When using a WebPlayer build, and opening a socket on port 80, the web player checks for a crossdomain policy server on port 843.
This prevents alternative web implementations (UniWeb on the Asset Store) from working the same way as the WWW class, which does a HTTP request on port 80 for /crossdomain.xml (not port 843).
Is there any way to get around this, or could I call this a Unity bug? 
Call this a security measure 
Its no bug, its by design that it searches for the policy server cause crossdomain checking would die if it had to do it on each request / packet 
What you want to do is use the PrefetchPolicy function which can fetch it from the webserver, before you try to do any web request with UniWeb / TCP Sockets
Right, but if I do a prefetch call and point it at port 80 on the target web server, will it do a HTTP request? (My tests indicate it does not.) Because of this, I think it’s impossible to replicate WWW in a web player build.
I’ve not tried it in some time but are you sure that:
- You pointed it to port 80
- That you expanded your crossdomain to be a valid socket policy? without the to ports its invalid and would likely fail too I guess (or generally does it comply to http://unity3d.com/support/documentation/Manual/Security%20Sandbox.html )
Yeah, it’s definitely port 80. I watch the HTTP server and it doesn’t receive a GET request.
hmm that then would qualify as bug if it does not even try to talk to it on port 80 (and then fail). Unsure on what protocol the fetch is sent though if its TCP or not (just in case the firewall is involved)