excess fragments

[jbardu]

Some clients generate the Frame.pm excess fragment error, I suspect because the unpacking is not working for them.

Here is a sniff, unfortunately just ascii

GET / HTTP/1.1
Upgrade: websocket
Connection: Upgrade
Host: ws.XXXXXX.com
Origin: https://XXX.YYYYYYY.com
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: OGvcQo1P4uQycWSRJKKtnw==
Sec-WebSocket-Version: 13
Sec-WebSocket-Extensions: x-webkit-deflate-frame
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.95 Safari/537.36
Cookie: XXXXXX
PSqg
PSqg
HTTP/1.1 101 WebSocket Protocol Handshake
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: rGj5x55J/XMWjTFMJulEi1UaySQ=
PUC PUC
PSqg
PUU PSqg PUZ
PSqg
PU
PSqg

On the server side, processing the received $frame, I get the error that more than 128 fragments are detected. At that point I have to force close the connection.

It does not seem to be a proxy server issue, I don't see any extra headers that would indicate a proxy server is corrupting the transmission?

The browser here is Chrome 28.0.1500.95 apparently under OSX.

[vti]

Try passing max_fragments_amount to the new constructor.