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.

Sign up for GitHub

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

Jump to bottom

flashsocket fallback to xhr-multipart or xhr-polling broken? #99

Closed
BubbaGump opened this issue Nov 13, 2010 · 2 comments
Closed

flashsocket fallback to xhr-multipart or xhr-polling broken? #99

BubbaGump opened this issue Nov 13, 2010 · 2 comments

Comments

@BubbaGump
Copy link

Hi again,

I seem to be having issues with the transports falling back after flashsocket fails.

13 Nov 18:35:14 - socket.io ready - accepting connections
13 Nov 18:35:26 - Initializing client with transport "flashsocket"
13 Nov 18:35:26 - Client 2864829630125314 connected
13 Nov 18:35:26 - Client 2864829630125314 disconnected
13 Nov 18:35:26 - Initializing client with transport "xhr-multipart"
13 Nov 18:35:26 - Client 9020702340640128 connected
13 Nov 18:36:20 - Client 9020702340640128 disconnected

xhr-multipart seems to "connect" fine, but never sends the "connect" back to the client..

Can anyone else confirm this? This is a hard one to reproduce as it relies on flashsocket failing when it normally works.

I am using the latest git install.

Thanks.
@cjoudrey
Copy link

Hey,

I'm actually having a similar problem.

The xhr-multipart doesn't seem to be working properly under Firefox 3.6.12.

27 Nov 14:34:50 - Initializing client with transport "xhr-multipart"
27 Nov 14:34:50 - Client 02334164548665285 connected
27 Nov 14:34:50 - connect
27 Nov 14:34:55 - disconnect
27 Nov 14:34:55 - Client 02334164548665285 disconnected
27 Nov 14:35:00 - Initializing client with transport "xhr-multipart"
27 Nov 14:35:00 - Client 8614127929322422 connected
27 Nov 14:35:00 - connect
...

The server prints connect, but the client never receives the connect event.

The connection is then closed and re-opened.

Thanks.

@rauchg
Copy link
Contributor

rauchg commented Jan 10, 2011

Can't reproduce

@snyk-bot snyk-bot mentioned this issue Oct 30, 2022
Open
@Bhanditz Bhanditz mentioned this issue Oct 30, 2022
Open
@ajesse11x ajesse11x mentioned this issue Oct 30, 2022
Open
@takeratta takeratta mentioned this issue Oct 30, 2022
Open
@john-bauer john-bauer mentioned this issue Oct 30, 2022
Open
@iamstarkdev iamstarkdev mentioned this issue Oct 30, 2022
Open
@abinabrahamanchery abinabrahamanchery mentioned this issue Oct 30, 2022
Open
@ebarahona ebarahona mentioned this issue Oct 31, 2022
Open
@one3chens one3chens mentioned this issue Oct 31, 2022
Open
This was referenced Oct 31, 2022
Open
Open
Open
@cagataycali cagataycali mentioned this issue Oct 31, 2022
Open
@ibraheem5022 ibraheem5022 mentioned this issue Nov 3, 2022
Open
darrachequesne pushed a commit that referenced this issue Jul 4, 2024
@P4sca1
fix: move @types/component-emitter to dependencies (#99)
4efa005 
Otherwise consumers of socket.io-parser (and socket.io) need to have it
listed in their devDependencies.
darrachequesne added a commit that referenced this issue Jul 8, 2024
@darrachequesne
[refactor] Remove any reference to the global variable (#103)
d848f0f 
Related #99
darrachequesne pushed a commit that referenced this issue Jul 8, 2024
@amitport @darrachequesne
[chore] Update to blob@0.0.5 (avoid reference to 'global') (#107)
1969404 
Source: https://github.com/amitport/blob/releases/tag/v0.0.5

Closes #99 
Related socketio/socket.io-client#1166
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rauchg @cjoudrey @BubbaGump