-
Notifications
You must be signed in to change notification settings - Fork 4.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
add support for https proxy #87638
add support for https proxy #87638
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue Detailsfixes #31113 .
|
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.
LGTM. Thanks.
failures may be relevant. Investigating.. |
/azp run runtime-libraries-coreclr outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-libraries-coreclr outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
src/libraries/System.Net.Http/src/System/Net/Http/SocketsHttpHandler/HttpUtilities.cs
Show resolved
Hide resolved
Have you considered running mitmproxy locally? We could even configure it in our enterprise tests to have proper E2E automated testing. |
I can look into it. I originally wanted come public proxy on Internet. |
fixes #31113 .
I could not find functional public proxy for testing. Plain HTTP is no brainer, HTTPS over HTTPS is somewhat more complicated and I'll ask community for validation.