-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Do not try to pipe Gzip responses with no body #2176
Conversation
@@ -921,7 +921,7 @@ Request.prototype.onRequestResponse = function (response) { | |||
}) | |||
|
|||
var responseContent | |||
if (self.gzip) { | |||
if (self.gzip && self.method !== 'HEAD') { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will fix the particular issue with HEAD requests, but will still cause issues if the response is empty for say a GET. A better way of handling would be to catch the Error from zlib.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Figuring out if the response is empty beforehand would be great, will think about it. I would rather not use try/catch
if there is some other way to detect the condition.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately there is no reliable way to determine upfront if the response body is empty. And in fact the error is thrown because the gzip content is invalid which may happen even if you have a body.
So the least we can do is forward the error events so that the user can handle them accordingly. Which means that you will receive an error when the request method is GET, the gzip option is set to true, and there is no response body.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Anyway still this PR fixes the mentioned issue in the description which is the most common use case.
@czardoz you can open up another issue and point to this one, so we can have a discussion there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done: #2177
Thanks, @simov! |
LGTM! 🍰 |
Version 2.72 is out! ✨ |
Fixes #2045
Fixes #2177