spring-cloud / spring-cloud/spring-cloud-gateway
How to enable websocket compression (permessage-deflate) for proxied websocket ?
Open
Nobody has claimed this yet.
enhancement
help wanted
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
I have websocket behind cloud gateway. How to enable permessage-deflate compression on gateway? when I connect directly do websocket compression works, but gateway just ignores request header:
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
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
No source file or test is named. Start by locating the gateway's proxied WebSocket handshake handling and compare its extension negotiation with the direct connection described in the report. Done means permessage-deflate is handled as intended for proxied WebSockets, with coverage for the reported request header behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- api, backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100