Skip to content
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.

Sign up for GitHub

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

Jump to bottom

When server's Content-Encoding: GZip, response won't decompress #661

Closed
jesseky opened this issue Aug 9, 2019 · 0 comments
Closed

When server's Content-Encoding: GZip, response won't decompress #661

jesseky opened this issue Aug 9, 2019 · 0 comments
Assignees
@Richienb
Labels
pending pr

Comments

@jesseky
Copy link

jesseky commented Aug 9, 2019

headers.get('Content-Encoding') didn't automatically convert to lower case.

So, may be we can manually convert capitalization:

file src/index.js, line 197:
const codings = headers.get('Content-Encoding').toLowerCase();
@Richienb Richienb mentioned this issue Sep 10, 2019
Merged
@Richienb Richienb self-assigned this Sep 10, 2019
@xxczaki xxczaki mentioned this issue Sep 10, 2019
Closed
35 tasks
mnot added a commit to http-tests/cache-tests that referenced this issue Feb 1, 2022
@mnot
lowercase generated content
1c1ff25 
as a workaround for node-fetch/node-fetch#661

Fetch doesn't specify force-lowercase, but node-fetch does it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Richienb Richienb

Labels
pending pr
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jimmywarting @bitinn @jesseky @Richienb