bug when websocket receive more than 2^15 bytes on chrome: Received a frame that sets compressed bit while another decompression is ongoing

Question

I tried to passed a JSON via websocket to a html GUI. When size is upper than 32768 bytes, chrome raises this exception:

WebSocket connection to 'ws://localhost:8089/events/' failed: Received a frame that sets compressed bit while another decompression is ongoing

on the line where WebSocket is instantiated :

this._websocket = new WebSocket(url);

However it work fine on firefox. I used jetty 9.1.3 on server side and I tried with chrome 33 and 34 beta.

I forget to precise that if I send length message superior than 32768 bytes, on chrome's network debugging tools, it show 32768 bytes length instead of real message length.

Any ideas ?

Bug filed at bugs.eclipse.org/430418

Joakim Erdfelt
– Joakim Erdfelt

2014-03-14 18:09:47 +00:00
Commented Mar 14, 2014 at 18:09 — Joakim Erdfelt
– Joakim Erdfelt, Commented Mar 14, 2014 at 18:09

Anshul Goyal · Accepted Answer · 2014-03-28 11:19:53Z

2

When using Jetty 9.1.2.v20140210 I don't have any problems with the connection, but with the later 9.1.3.v20140225 version it fails and I get the error using Opera or Chrome. Firefox works fine on all versions.

I submitted a bug report to Jetty about this: https://bugs.eclipse.org/bugs/show_bug.cgi?id=431459

edited Mar 28, 2014 at 11:19

Anshul Goyal

78k42 gold badges162 silver badges196 bronze badges

answered Mar 28, 2014 at 11:03

Bercon

212 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Noam Ben Ari Over a year ago

Thanks, I bumped into the same problem and the older version works for me too.

raulsaeztapia Over a year ago

It is the same to us. We are specified 9.1.2.v20140210 on pom.xml and all work again.

VLAZ · Accepted Answer · 2025-07-08 20:05:54Z

This might be a bug in Jetty.

permessage-deflate requires the compression bit be set on the first frame of a fragmented message - and only on that.

It might be that Jetty fragments outgoing message to 32k fragments, and sets the compression bit on all frames. If so, that's a bug.

I have just tested current Chrome 33 using Autobahn|Testsuite: everything works as expected .. including messages with 128k.

You can test Jetty using above testsuite. It'll catch the bug if there is one.

Of course you're right, I tried with jetty 9.1.2 and it's work fine with both chrome and firefox. I have not tried to determine if as you said, there is 1 compression bit per fragment. Thanks for your answer
Chrome 33 and 34 pass deflate-frame extension too, it could also be a bug in that extension.

Collectives™ on Stack Overflow

bug when websocket receive more than 2^15 bytes on chrome: Received a frame that sets compressed bit while another decompression is ongoing

2 Answers 2

2 Comments

2 Comments

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

2 Comments

Related