Buffconn should buffer upto maxHeaderBytes to avoid ErrBufferFull #7017
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.
Description
Buffconn should buffer up to maxHeaderBytes to avoid ErrBufferFull
Motivation and Context
It can happen with erroneous clients which do not send
Host:
header until 4k worth of header bytes has been read. This can lead
to Peek() method of bufio to fail with ErrBufferFull.
To avoid this we should make sure that Peek buffer is as large as
our maxHeaderBytes count.
Regression
No
How Has This Been Tested?
https://play.golang.org/p/COImHdhMj-J here is an example code to reproduce a version of this issue.
Types of changes
Checklist:
mint
PR # here: )