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.

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

Should Content-Length be set on gzipped responses? #84

Open
tonyghita opened this issue Jun 12, 2019 · 1 comment
Open

Should Content-Length be set on gzipped responses? #84

tonyghita opened this issue Jun 12, 2019 · 1 comment

Comments

@tonyghita
Copy link

I see that the Content-Length header is read when a response passes through the middleware, and that it is later deleted before writing the gzipped response to prevent the EOF.

Should a Content-Length header be set after the size of the compressed content is known? What are the reasons for omitting Content-Length on gzipped responses?

@sourpotato
Copy link

I have the same question.

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

No branches or pull requests

2 participants