Skip to content

HTTP/2 decompression support missing #537

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ve6yeq opened this issue Dec 29, 2021 · 2 comments · Fixed by #610
Closed

HTTP/2 decompression support missing #537

ve6yeq opened this issue Dec 29, 2021 · 2 comments · Fixed by #610

Comments

@ve6yeq
Copy link

ve6yeq commented Dec 29, 2021

AsyncHTTPClient commit hash: 19e83a3

Context:
It is possible to enable transparent decompression of compressed responses using the Configuration.decompression property. This works fine for HTTP/1.1 connections with the response body being "transparently" decompressed but does not appear to be implemented for HTTP/2 connections where the response body is still compressed.

Any idea on where this transparent decompression should be connected into with HTTP/2?

@Lukasa
Copy link
Collaborator

Lukasa commented Jan 4, 2022

I think this is for @fabianfett and @dnadoba: we may need to bring NIOHTTPResponseDecompressor into our HTTP/2 pipelines.

@rnantes
Copy link

rnantes commented May 12, 2022

This caused me issues. I ended up having to use config.httpVersion = .http1Only Or headers.add(name: "accept-Encoding", value: "identity")

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants