Handle an HTTP Response with a Content-type but no body. #530
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In c46663d a change was made to clean up the
encode_with_ruby_encoding
method.Previously, the
force_encoding
method was always called and then there was arescue
that would just return thebody
. If a request had anil
body, therescue
made sure that anil
value (the originalbody
) would be returned.After c46663d, if a response had a
nil
body, an error would be thrown when parsing the response.This PR includes a spec that reproduces the error and a fix that adds a
nil
check to make sure we do not callforce_encoding
onnil
. If thebody
isnil
, we will returnnil
. This matches the previous behavior.