spring-cloud / spring-cloud/spring-cloud-gateway
Websocket connection throws 413 entity too large exception
Open
Nobody has claimed this yet.
feedback-provided
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
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 files or tests are named. Start by reproducing the Spring Cloud Gateway proxy setup with HTTP and WebSocket requests, then inspect WebSocket forwarding and x_forwarded_for/x_forwarded_proto handling. Done means the WebSocket request avoids the 413 exception and the forwarded headers are not duplicated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, 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
- 25/100