Description
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?