fross
02-15-2007, 01:06 PM
Hi all,
this may not be the usual crossdomain.xml problem you're familiar with, so please read on :)
I have a swf (written in as3) that connects to two servers in different ways - server A it connects to with a URLLoader and gets some static information from. server B it opens an XMLSocket to and gets some streaming data.
When the SWF is served from my local machine (ie a file:// location), both work fine.
When the SWF is served from server A, it connects back to server A with the URLLoader happily, however, the XMLSocket to server B fails. Not explicitly, there is no error, however the XMLSocket never gets an Event.CONNECT happening.
I do have a crossdomain.xml file on a webserver, port 80, on server B. here it is:
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy
SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<allow-access-from domain="*" />
</cross-domain-policy>
(it's firewalled, so I can do that ;) )
Some things I noticed that are interesting though:
- the crossdomain.xml file on server B is not getting accessed by the flash file. No hits to it are recorded in the webserver's access logs. I've verified I can see the file from a web browser.
- server B is actually getting something from the flash client! I traced it with ethereal, and see a couple of ACKs going back and forth, but I'm not an expert in this sort of thing. After a couple of those messages though, it just stops.
- I set allowScriptAccess to always, in case that affects anything :)
I've not released something to a live environment like this before; I've read the docs but suspect I'm missing something basic here, so any pointers would be very welcome.
Thanks!
this may not be the usual crossdomain.xml problem you're familiar with, so please read on :)
I have a swf (written in as3) that connects to two servers in different ways - server A it connects to with a URLLoader and gets some static information from. server B it opens an XMLSocket to and gets some streaming data.
When the SWF is served from my local machine (ie a file:// location), both work fine.
When the SWF is served from server A, it connects back to server A with the URLLoader happily, however, the XMLSocket to server B fails. Not explicitly, there is no error, however the XMLSocket never gets an Event.CONNECT happening.
I do have a crossdomain.xml file on a webserver, port 80, on server B. here it is:
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy
SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<allow-access-from domain="*" />
</cross-domain-policy>
(it's firewalled, so I can do that ;) )
Some things I noticed that are interesting though:
- the crossdomain.xml file on server B is not getting accessed by the flash file. No hits to it are recorded in the webserver's access logs. I've verified I can see the file from a web browser.
- server B is actually getting something from the flash client! I traced it with ethereal, and see a couple of ACKs going back and forth, but I'm not an expert in this sort of thing. After a couple of those messages though, it just stops.
- I set allowScriptAccess to always, in case that affects anything :)
I've not released something to a live environment like this before; I've read the docs but suspect I'm missing something basic here, so any pointers would be very welcome.
Thanks!