Set correct Content-Type
header in query response
#4828
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.
Because the internal query request handlers did not set the response
content type explicitly to
application/json
, and the external requesthandler takes the response content type from the internal response to
set it for the resulting HTTP response, that response was also
incorrectly returning
Content-Type: text/plain
.Setting the content type in the internal response correctly results in
the expected
Content-Type
headerapplication/json; charset=UTF-8
.Fixes #4791
Signed-off-by: Christian Haudum christian.haudum@gmail.com