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

Using HTTP Range headers for pagination makes gzip compression of response bodies impossible even with nginx proxy? #2573

Closed
brandonros opened this issue Nov 24, 2022 · 3 comments
Closed

Using HTTP Range headers for pagination makes gzip compression of response bodies impossible even with nginx proxy? #2573

brandonros opened this issue Nov 24, 2022 · 3 comments

Comments

@brandonros
Copy link

Just want to confirm I'm not crazy. I've tried multiple nginx configs, Safari + Chrome.

fetch() from the browser will send Accept-Encoding: identity instead of Accept-Encoding: gzip, deflate, br by default because there's nothing that can be done apparently?
@wolfgangwalther
Copy link
Member

Please show us what you did, what you get and what you expect. Also let us know with which version you are working.

@brandonros
Copy link
Author

brandonros commented Nov 24, 2022 •
edited
Loading

Chrome refuses to request for gzip if you use Range + Range-Unit: items.

@steve-chavez
Copy link
Member

Hm, this seems related to #2204

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@steve-chavez @brandonros @wolfgangwalther