Fix WriteHeader + RenderJSON causing wrong Content-Type header#1980
Merged
Fix WriteHeader + RenderJSON causing wrong Content-Type header#1980
Conversation
Replace WriteHeader() + RenderJSON() pattern with EncodeJSON() which properly sets Content-Type header before writing status code. The previous pattern caused Content-Type to default to text/plain instead of application/json, breaking frontend JSON parsing. Fixes #1979
Pull Request Test Coverage Report for Build 20279407861Details
💛 - Coveralls |
This was referenced Dec 16, 2025
umputun
approved these changes
Dec 16, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
WriteHeader()called beforeRenderJSON()causes Content-Type header to be ignoredEncodeJSON()which properly sets headers before writing status codeFixes #1979