search

gimite / web-socket-js

HTML5 Web Socket implementation powered by Flash
BSD 3-Clause "New" or "Revised" License
2.73k stars 489 forks source link

flash socket v13 string message decoding not work correctly on IE9 #108

Closed dengyingyu closed 12 years ago

dengyingyu commented 12 years ago

I used web-socket-js for backend man client on web. First, I use Chrome V13 for testing, it support only v76. But when I test it with IE9(use flash socket v13) , short message ( like '#0!' ) is ok, but longger message is not work, it cause flash socket closed imm. When I switch to Chrome V16( use websocket v13 ), it work correctly. Then I think if there are some bugs in Flash Socket v13 about string messages decoding.

dengyingyu commented 12 years ago

I use latest version of web-socket-js and my flash player version is 11.1.102.55 and my IE9 version is 9.0.8.8112.16421 and my OS is Win7Ultra.

I wrote a server myself, follow the rfc documents. I use header like [fin:1 rsv[]:0 opcode:1][payload_len:27 mask:0] followed by data[utf8 string[27]]. I can see them on Chrome V16 with native websocket, but not on IE9 with flash socket.

gimite commented 12 years ago

Can you try "Troubleshooting" section in https://github.com/gimite/web-socket-js#readme ?

If it doesn't help, can you send information pointed in "Troubleshooting" section, especially error message in step 2? Also can you clarify whether it closes when you send message from server or client, and whether it happens for any message with same length e.g. repeating "a" 27 times?

dengyingyu commented 12 years ago

sorry, it's my fault. damn js in IE not support string[], that cause my server treat unescaped string message as a wrong format message and closed the socket.