reverseproxy: Remove redundant flushing #4299
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.
From reading through the code, I think this code path is now obsoleted by the changes made in #4266.
Basically,
h.flushInterval()
will set the flush interval to-1
if we're in a bi-directional stream, and the recent PR ensured thath.copyResponse()
properly flushes headers immediately when the flush interval is non-zero. So now there should be no need to call Flush before callingh.copyResponse()
.Since this was your code from #3556 and #3561 @masknu, would you mind confirming that your usecase still works correctly with this change, just as a sanity check? Thanks!