Use compression/decompression codecs for HTTP/2 request/response content?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 35.1k
- Forks
- 16.3k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 143
Description
It is easy to build a netty HTTP/1 server that does support gzip/deflate compressed POST/PUT requests. Just add HttpContentDecompressor to the pipeline before
Is there an efficient way to do that in a netty HTTP/2 server without using InboundHttp2ToHttpAdapter? e.g. having a HttpPostRequestDecoder support decompression?
Also HttpContentDecompressor does seem to create an EmbeddedChannel/EmbeddedEventLoop for every connection, which has quite a memory footprint.
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 HttpContentDecompressor, HttpPostRequestDecoder, and the HTTP/2 server pipeline around InboundHttp2ToHttpAdapter. Compare how compressed HTTP/1 request content is handled with the HTTP/2 path, including the reported EmbeddedChannel and EmbeddedEventLoop cost. Done would require an agreed, efficient design and confirmed codec support for HTTP/2 request and response content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100