playframework / playframework/play1
Play 1.7 WS problem (header too large)
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 671
- Avg merge
- 12d 15h
- Merged PRs (30d)
- 1
Description
Are you looking for help?
Requests made through WS do not support response headers longer than 8152 bytes. Some web servers return such long headers.
Netty allows to configure this, but it does not seem to be possible to configure through Play!
Play Version (1.5.x / etc)
1.7.1
Operating System (Ubuntu 15.10 / MacOS 10.10 / Windows 10)
MacOS and Ubuntu.
JDK (Oracle 1.8.0_72, OpenJDK 1.8.x, Azul Zing)
JDK 17.0.1
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 tracing Play 1.7.1's WebSocket request handling and how it configures Netty, focusing on the response-header size limit described in the issue. Check whether the limit is exposed through Play configuration; done means WebSocket requests can handle headers longer than 8152 bytes when configured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100