Fix concurrent write bug in reader.Render #3568
Open
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 a caller passed in a map retained within the caller's context as extraHeaders to gin.Context.DataFromReader() then a race to write the "Content-Lenght" header would occur.
// globalHeader is passed to gin.Context.DataFromReader
var globalHeaders = map[string]string{
"cache-control": "public, max-age=3600",
}
func (c *gin.Context) {
//...
}
master