spring-cloud / spring-cloud/spring-cloud-gateway
Sec-WebSocket-Extensions header is not passed to proxied server
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading WebsocketRoutingFilter.class and trace how WebSocket request headers are filtered for proxied connections. Reproduce the gateway route with the supplied request, then verify that the proxied server receives Sec-WebSocket-Extensions while existing WebSocket handling remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100