-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
transport: Discard the buffer when empty after http connect handshake #7424
Merged
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
configure the proxy to wait for server hello
- Loading branch information
commit 3cf3bd6776830a74803adf358ff4f76488f04340
There are no files selected for viewing
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's now 3 places where we're setting this deadline.
Maybe instead when the conn is created in
proxyDial
we should just doc.SetDeadline(....defaultTestTimeout)
(noteDeadline
notRead
to also abort writes)?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
During testing, I noticed that the test can hang in
proxyDial
if the proxy server waits for aserver hello
when the server doesn't intend to send one. This was due to a logical error on my part which I fixed.To be safe, I added read deadlines in both the places where reads could hang.
Do you mean adding a deadline in the actual
proxyDial()
implementation by introducing a timeout that only the tests use?Or are you referring to adding a deadline on the conn returned by
proxyDial
in the test code?The latter would not prevent
proxyDial
from hanging when the proxy server is stuck reading theserver hello
. The former would work but it involves changing non-test code, which I was trying to avoid.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I didn't mean in
proxyDial
... I meant the connection it returns, we could immediately, always, do aSetDeadline(...)
, instead of doing it later and conditionally.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed
SetReadDeadline
toSetDeadline
. Moved the SetDeadline immediately after theproxyDial
call. TheSetDeadline
inproxyServer.run()
is still present to avoid proxyDial from hanging indefinitely in case of test failures.