Skip to content
New issue

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

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

Already on GitHub? # to your account

Honor maximum websocket frame length #493

Closed
3rd-Eden opened this issue Aug 29, 2011 · 1 comment
Closed

Honor maximum websocket frame length #493

3rd-Eden opened this issue Aug 29, 2011 · 1 comment
Labels
bug Something isn't working

Comments

@3rd-Eden
Copy link
Contributor

I was pumping a shit load of information down the wire, and I received

WebSocket frame (at 18446744073709551615 bytes) is too long.

This occurred in Safari 5.1, so it's still using the old drafts. As a result of this, the message was dropped....

@quentinxs
Copy link

It also occurs in Safari on iOS 5.0.1

WebSocket frame (at 4294967295 bytes) is too long.

Searching the issue on Google came up with 2 main finds:
Documentation of the problem on iOS - http://dalelane.co.uk/blog/?p=1652
A possible explanation of why it occurs - http://stackoverflow.com/questions/6960500/websocket-versions-and-backwards-compatibility

This issue was closed.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants