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
Fail immediately on proxy connect exception #2805
Conversation
83dfb04
to
1c0af1f
Compare
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.
Thanks for taking care of this. 😄
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.
Thanks a lot, @jrhee17 !
Codecov Report
@@ Coverage Diff @@
## master #2805 +/- ##
============================================
- Coverage 72.80% 72.72% -0.08%
- Complexity 11929 11934 +5
============================================
Files 1049 1049
Lines 46467 46554 +87
Branches 5810 5810
============================================
+ Hits 33828 33856 +28
- Misses 9665 9724 +59
Partials 2974 2974 Continue to review full report at Codecov.
|
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.
Thanks! @jrhee17 🙇♂️
Motivation: Related: line#2801 Proxy client can hang when a connection is established, but the connection is closed without a `ProxyConnectEvent`. 1) If a `ProxyConnectEvent` is never received, we don't mark the session as complete. 2) Since the session isn't completed, the first write is never invoked 3) Previously we had been relying on `ProxyHandler`s pending write failures to be notified of proxy failure (`HttpRequestSubscriber.operationComplete` used to close the response previously). Modification: Try to fail the `sessionPromise` on proxy connect exception
Motivation
Related: #2801
Proxy client can hang when a connection is established, but the connection is closed without a
ProxyConnectEvent
.ProxyConnectEvent
is never received, we don't mark the session as complete.ProxyHandler
s pending write failures to be notified of proxy failure (HttpRequestSubscriber.operationComplete
used to close the response previously).Modification
Try to fail the
sessionPromise
on proxy connect exception