Sec-WebSocket-Extensions header is not passed to proxied server

[amizurov]

Expected behavior: proxied server should receive the Sec-WebSocket-Extensions header.

Current behavior:
Configure gateway route for handling websocket connection. Client send request ->

       GET /ws HTTP/1.1
       Host: localhost:7788
       Upgrade: websocket
       Connection: Upgrade
       Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ==
       Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
       Sec-WebSocket-Version: 13

Proxied server not received Sec-WebSocket-Extensions header. This is header was filtered in WebsocketRoutingFilter.class.

Spring Cloud Gateway Version: 2.1.2.RELEASE

[ryanjbaxter]

This was done on purpose.

#143
cc: @spencergibb

[amizurov]

Hi, @ryanjbaxter and thanks for responding. I agree that WebSocket is a hop‑by‑hop protocol (Connection and Upgrade headers), but when a gateway received Upgrade request from a client it need to sent its own Upgrade request to a proxied server including the appropriate headers one of them is Sec-WebSocket-Extensions header. It is used in the WebSocket opening handshake to agree on a set of protocol-level extensions to use for the duration of the connection.

[amizurov]

@ryanjbaxter @spencergibb guys any update about issue ?

[divyaJainPhilips]

@amizurov did you find a solution to this problem. Facing the same issue while establishing websocket connection

[amizurov]

@amizurov did you find a solution to this problem. Facing the same issue while establishing websocket connection

Yes, we patched gateway and will prepare pull request a soon as possible.

[divyaJainPhilips]

@amizurov any idea on the timeline when u will be able to create a pull request