|
If you were logged in you would be able to see more operations.
|
|
|
| Support Plan Customer Issue: |
No
|
| Resolution Date: |
11/29/08 12:12 AM
|
| Acceptance Test - Add?: |
No
|
|
The flash cross domain handler that runs on port 5229 immediately spits a cross domain file at whoever connects to the port. That is improper as Flash is expecting to perform an HTTP dance to retrieve that file. In other words, flash expects to connect, send a GET /crossdomain.xml, get the file, and disconnect. Instead, often flash based clients will connect, go to send the GET, and either notice they've been disconnected already and freak out, or do the GET, not hear anything back (because it was already sent before they got their GET out), and time out. A simple fix for this will be to run a minimal HTTP servlet on that port.
|
|
Description
|
The flash cross domain handler that runs on port 5229 immediately spits a cross domain file at whoever connects to the port. That is improper as Flash is expecting to perform an HTTP dance to retrieve that file. In other words, flash expects to connect, send a GET /crossdomain.xml, get the file, and disconnect. Instead, often flash based clients will connect, go to send the GET, and either notice they've been disconnected already and freak out, or do the GET, not hear anything back (because it was already sent before they got their GET out), and time out. A simple fix for this will be to run a minimal HTTP servlet on that port. |
Show » |
|
So we're going with it answering both style requests, and back to the extremely lightweight handler. 
Bug
Closed
Major
Flash cross domain handler (port 5229) should not spit crossdomain.xml immediately
http://www.adobe.com/devnet/flashplayer/articles/socket_policy_files.html
We should not be doing HTTP for this. That said, HTTP works, and Flash clients accept it just fine. That said, might as well follow the guidelines as precisely as possible.