Crossdomain woes

(I may have jumped the gun on https, I re-read your post and notice nothing about https outgoing connections, But this solution will still stand a chance of working.)

the problem with that is that HTTPS is not port 80, also it does not send a cleartext host therefore all it has in as ip address.

Two possible answers to this.

1: Add port 443 (https) to the existing policy file to allow the client to access that port as well as port 80

2: If that does not work, setup a crossdomain policy service on port 843 that includes your access.

here is a link to unity's Sandbox documentation.

http://docs.unity3d.com/Documentation/Manual/SecuritySandbox.html

Thanks for the answer but as I think you added later the GET is actually done using http not https, can see it in the sniffer. Do you think WWW is in some way changing its behaviour because the page it's on was served usign https ?

The code works within the Editor, reads the crossdomain no probs but when deployed via the LMS it complains the policy file is invalid. Don't suppose there is a "verbose" setting on WWW somewhere to get more info re what it's complaining about ?