Writing status text breaks JSON decoding #13
Merged
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.
OutputJSON
as of 3cfb7ff has the following chunk of code:Writing out
rs.StatusText
to thehttp.ResponseWriter w
causes the body of the response to contain non-JSON data, and breaks client parsing. I don't understand the purpose of that code.You can see this if you set
config.ErrorStatusCode
orresponse.ErrorStatusCode
to anything other thanhttp.StatusOK
. Here's the difference in curl:With the default
ErrorStatusCode
:With a changed
ErrorStatusCode
:Should that code block simply be removed? I'm happy to write up a patch for it, but I wanted to check with you first in case there's something I am not understanding.