Skip to content
This repository has been archived by the owner on Dec 16, 2023. It is now read-only.

Unzipped responses should have Content-Length removed #142

Closed
s25g5d4 opened this issue Dec 14, 2017 · 2 comments · Fixed by #143
Closed

Unzipped responses should have Content-Length removed #142

s25g5d4 opened this issue Dec 14, 2017 · 2 comments · Fixed by #143

Comments

@s25g5d4
Copy link
Contributor

s25g5d4 commented Dec 14, 2017

Some server do add Content-Length in response header. For zipped responses, the content-length is the compressed, compact size of data of course. But because in PR #72 zipped responses will get decompressed, if content-length is presented in original response header, it should be updated, or, removed. I'm willing to send a PR to fix it. It is just an one-line fix, I would really appreciate it if you could take a look.

@s25g5d4
Copy link
Contributor Author

s25g5d4 commented Dec 14, 2017

Forgot to say that why I made this ticket is because, I have some SVGs that will be sent gzipped by server. But because the content-length recorded in fixtures are smaller than the actual data size, browser will truncate responses and fail to parse those SVGs.

@marcusschiesser
Copy link

@assaf - any plans to release this commit soon?

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

Successfully merging a pull request may close this issue.

2 participants