Openfire (ARCHIVED)

Flash cross domain handler (port 5229) should not spit crossdomain.xml immediately

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 3.6.1
  • Fix Version/s: 3.6.3
  • Component/s: Core
  • Acceptance Test - Add?:
    No
  • Description:
    Hide

    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
    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.

Activity

Ascending order - Click to sort in descending order
Daniel Henninger made changes - 11/25/08 02:13 AM
Field Original Value New Value
Status Open [ 1 ] Closed [ 6 ]
Resolution Fixed [ 1 ]
Hide
Permalink
Daniel Henninger added a comment - 11/26/08 05:47 PM

Based on this document:
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.

Show
Daniel Henninger added a comment - 11/26/08 05:47 PM Based on this document: 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.
Daniel Henninger made changes - 11/26/08 05:47 PM
Status Closed [ 6 ] Reopened [ 4 ]
Resolution Fixed [ 1 ]
Hide
Permalink
Daniel Henninger added a comment - 11/29/08 12:12 AM

While adobe's documentation says you should do it one way, the other works fine too. So we're going with it answering both style requests, and back to the extremely lightweight handler.

Show
Daniel Henninger added a comment - 11/29/08 12:12 AM While adobe's documentation says you should do it one way, the other works fine too. So we're going with it answering both style requests, and back to the extremely lightweight handler.
Daniel Henninger made changes - 11/29/08 12:12 AM
Status Reopened [ 4 ] Closed [ 6 ]
Resolution Fixed [ 1 ]

People

Dates

  • Created:
    11/25/08 01:59 AM
    Updated:
    11/29/08 12:12 AM
    Resolved:
    11/29/08 12:12 AM
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for igniterealtime.org. Try JIRA - bug tracking software for your team.