server/writer: properly handle result encoding errors #7114
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.
If the encoding of a result of some sort -- any payload passed to
writer.JSON()
orwriter.JSONOK()
-- failed, we'd emit a log line likeand nobody likes these. Also, the encoding error would be the response payload, but the status code had still been 200.
Now, errors encoding the payload properly lead to 500 statuses, without extra logs.
Also headers should be set using Set(), not Add(), to avoid response headers like