-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
fix(har timing): record connect
timing for proxied connections
#32855
Conversation
connect
timing for proxied connections
This comment has been minimized.
This comment has been minimized.
Co-authored-by: Max Schmitt <max@schmitt.mx> Signed-off-by: Simon Knott <info@simonknott.de>
This comment has been minimized.
This comment has been minimized.
Test results for "tests 1"1 flaky36416 passed, 757 skipped Merge workflow run. |
Do we have to upgrade the deps? I am always wary of introducing regressions. |
For SOCKS proxy we don't, but for HTTP proxy yes. The If we don't want to update, another alternative would be leave things as is for the HTTP proxy and set |
Could you give this another look @dgozman? |
…ns" (#32855) (#33003) This reapplies what we reverted in #32989. Max and me debugged this, and found that the test failures come from SOCKS proxy now preferring IPv6 over IPv4. We've updated the tests and made sure that this doesn't mask any breaking change. I'm enabling CQ1 to make sure we don't oversee any other CI failures.
Fixes a bug discovered in #32647. When using http proxy, the
connect
event isn't emitted so we don't populatetcpConnectionAt
. The updated version ofhttps-proxy-agent
emits aproxyConnect
as a replacement, so this PR updates and listens to that event.For socks proxies, the
on("socket")
event is emitted once the SOCKS connection is established, which is the equivalent of having a TCP connection available.