Fix Flush breaks response if called while buffering #60
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.
This fixes the bug I noted in #58 (comment). In doing so, it reverts 0f67f3f, which was #58, and commits a different fix for that issue.
Where #58 juggled calling
WriteHeader
withinFlush
, this pull request simply makesFlush
a no-op while the response is buffering, i.e. until it reaches the minimum size.In reverting 0f67f3f, it has the side-effect of reducing the size of the per-request
GzipResponseWriter
struct from 104 bytes to 96 bytes.