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

Flash Socket over SSL seems to incorrectly handle large amounts of data #1045

Closed
meltzerj opened this issue Oct 6, 2012 · 9 comments
Closed

Comments

@meltzerj
Copy link

meltzerj commented Oct 6, 2012

All information can be found here: http://stackoverflow.com/questions/12756522/flash-sockets-over-ssl-in-ie9-seem-to-have-a-data-limit

This issue actually seems to not be isolated to Internet Explorer.

Im honestly not even sure if this is a socket.io bug as opposed to a node bug. I'm curious as to whether anyone else who has tried cross domain flash socket transport over SSL has experienced this with large amounts of data.

UPDATE:

Looking a bit more closely at the logs, it seems that at some point the data being sent to the server is being broken up into separate sections (definitely not the correct term) of data. This is probably why the code in default.js looking for a null byte as the first frame throws an error, because when the packets are broken up, the second section is not it's own but rather the second part of a continuation of data. It doesn't seem that socket.io anticipates this, although it's possible that the bug lies somewhere else and that socket.io is doing things correctly...

I asked this question on the node google group and they're unsure whether it's a node or socket.io bug: https://groups.google.com/forum/?fromgroups=#!topic/nodejs/dwmeBILTrD0

UDPATE 2:

After a bit more research, it looks as if Websockets send the "sec-websocket-version" key of "13", while flash sockets do not send this key and therefore use a different parser from that of Websockets. Flash uses the default.js file, while websockets use the hybi-16.js file. Is this correct?

@meltzerj
Copy link
Author

meltzerj commented Oct 7, 2012

Has anyone gotten a test case with cross-domain flash socket transport over SSL working with a relatively large amount of data (about > 80 Kb)? This seems like it could be a serious issue...

@rauchg
Copy link
Contributor

rauchg commented Oct 11, 2012

@meltzerj would you mind isolating a test case so I can look at creating a workaround?

@3rd-Eden
Copy link
Contributor

I'm really tired of no one responding to my socket.io Github issues. Why is support so bad here?

@meltzerj also read http://blog.nodejitsu.com/getting-refunds-on-open-source-projects

@rauchg
Copy link
Contributor

rauchg commented Oct 11, 2012

@3rd-Eden he deleted his comment btw.

@3rd-Eden
Copy link
Contributor

@guille i noticed, still good related reading, we are only human.

@rauchg
Copy link
Contributor

rauchg commented Oct 11, 2012

Cool, I thought you were replying to the email.

@meltzerj
Copy link
Author

@3rd-Eden @guille Yeah, I suddenly realized I was wrong to impulsively post that which is why I deleted it right away.

@rauchg
Copy link
Contributor

rauchg commented Oct 11, 2012

👍

@meltzerj
Copy link
Author

meltzerj commented Nov 2, 2012

@guille You may want to check this out: http://stackoverflow.com/questions/12756522/flash-sockets-over-ssl-in-ie9-seem-to-have-a-data-limit/13180267#13180267

Could be a bug fix for flashsockets over ssl.

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

3 participants