Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data incorrectly framed by UA. Dropping connection #103

Closed
brendon opened this issue Nov 23, 2010 · 1 comment
Closed

Data incorrectly framed by UA. Dropping connection #103

brendon opened this issue Nov 23, 2010 · 1 comment

Comments

@brendon
Copy link

brendon commented Nov 23, 2010

Hi there,

I'm currently using socket.io as part of Juggernaut 2.

I've been having this problem with Firefox 3 and its flashsocket fallback. I've placed the websocket file in the root of the site. The first time you try to connect you get this in the logs (production).

22 Nov 23:26:37 - Initializing client with transport "flashsocket"
22 Nov 23:26:37 - Client 24364942777901888 connected
22 Nov 23:26:38 - Data incorrectly framed by UA. Dropping connection
22 Nov 23:26:38 - Client 24364942777901888 disconnected
22 Nov 23:26:39 - Initializing client with transport "xhr-polling"
22 Nov 23:26:39 - Client 2361341412179172 connected
22 Nov 23:26:39 - Initializing client with transport "xhr-multipart"
22 Nov 23:26:39 - Client 6185610580723733 connected

If you refresh the page it works fine:

22 Nov 23:54:33 - Initializing client with transport "flashsocket"
22 Nov 23:54:33 - Client 14171182038262486 connected

I noticed someone else posted this problem here too but in reply to a thread about Firefox 4 which seems to be a different matter.

Any help would be greatly appreciated :)

Cheers,

Brendon

@rauchg
Copy link
Contributor

rauchg commented Mar 6, 2011

Need better reproduction steps

darrachequesne pushed a commit that referenced this issue Jul 4, 2024
… to also have the .once removed as it's wrapped in a function. Anyways this alone is enough to close bug #103 . Because we now have a once listener we can easily fix #38
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants