Also, when Aurora drops the connection, it does not first send a close frame with the expected error code. It just instantly closes the underlying TCP socket. I would expect it to send one of the following error codes to the server before closing the socket: 1002 - Protocol Error 1004 - Message Too Large
Brian, You win a special award of some kind for best test case. If we had such a thing :) The issue here is a "shift the accumulation buffer" optimization that none of the other fragment test cases have managed to hit. Thanks! It can result in fragmented parts of the message being lost, which resulted in the failure.
Created attachment 546774 [details] [diff] [review] patch 1
Created attachment 546776 [details] [diff] [review] patch 1a forgot to put a comment in the obsoleted patch. code content is the same.
A special award? I'm glad I could be helpful!
Oh I should mention that I strongly suspect this bug also affects the current Firefox 6 beta. I didn't write exhaustive test code for it though because Fx6 implements draft-07 and my code has all been updated for draft-09. But I did fire up the draft-07 branch of my code to try something against Fx6 and experienced the same problem that originally caused me to look into this issue for Fx7.
6 years ago
The early bird cathes the worm :) Thanks! I'll continue testing on FF8.