Websocket under Chrome interrupt by RSV != 0

335 views
Skip to first unread message

mwolff86

unread,
Apr 19, 2017, 3:05:41 AM4/19/17
to vert.x

Hi,


we are using Vertx with websocket and frameHandler for handling Websocket. Normally it works well, but on some operating systems of our customers this error message is thrown:


ERROR ConnectionBase:187 [vert.x-worker-thread-6] - io.netty.handler.codec.CorruptedFrameException: RSV != 0 and no extension negotiated, RSV:4
ERROR LoggerVerticle:87 [vert.x-worker-thread-2] - WebsocketServerVerticle : an exception occur on the WebSocket
java.lang.Exception: RSV != 0 and no extension negotiated, RSV:4


As we know, they using Android devices with Chrome. Sometimes they can work as well too, but under unknow circumstances vertx thrown this errors and our customers couldn't do anything.


I couldn't tell you much about the operation system, all i know is there is an apache for forwarding all requests between device and vertx.

Does anyone has the same issue or can tell me how to solve this problem? All I found was to set "allowExtensions" to true but the HttpServerImpl setting this to false and i couldn't find a way to change this.


Thx for repsonse.

Tim Fox

unread,
Apr 19, 2017, 4:31:01 AM4/19/17
to vert.x
(Guessing) Looks like the client hasn't negotiated an extension, but is sending a frame specifying an extension, this would be a client error according to the rfc:


"MUST be 0 unless an extension is negotiated that defines meanings
      for non-zero values.  If a nonzero value is received and none of
      the negotiated extensions defines the meaning of such a nonzero
      value, the receiving endpoint MUST _Fail the WebSocket
      Connection_."

Vert.x doesn't currently support websocket extensions.

It might be an idea to try and isolate the requests that are causing this and use something like wireshark to look at the headers in the handshake to see if the client is trying to request some kind of extension.

mwolff86

unread,
Apr 20, 2017, 3:33:44 AM4/20/17
to vert.x
Hi Tim,

thx for pushing in right direction, we will anaylse the request hoping the find the problem.
Reply all
Reply to author
Forward
0 new messages