-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Allow use of CONNECT tunneling for unencrypted requests #37690
Comments
Tagging subscribers to this area: @dotnet/ncl |
Beyond HTTP proxies, we have an outstanding issue for SOCKS proxy support in #17740, and for HTTPS proxy support in #31113. Additionally, we'll have a lot more flexibility around this (so you can easily plug in whatever transport you'd like) with #1793. |
@scalablecory HttpClient is proxying HTTP request, the only problem is that it is not creating tunnel for it. If you proxy to HTTPS or web socket, the first message to the proxy is CONNECT. I am happy to see direct SOCKS support being worked on though. |
I am excited about the work at #1793 . I hope the flexibility provided will be enough for my use case. |
Gotcha. Typically the form "GET http://foo.com" is used for unencrypted requests (this allows for more efficient connection pooling) and "CONNECT foo.com" is used for encrypted requests. The ask, then, would be to make this selectable. #1793 would allow a CONNECT tunnel to be used, though we might want to add an option to |
Awesome, I am looking forward! Will keep using my home grown proxy for now. |
I need to create a secure tunnel with HTTP uri, but the HttpConnection only create a tunnel if this the destination is secure, or websocket IsNonSecureWebSocketScheme.
The reason I need it, is that I want to use a Socksv5 HTTP proxy (
HTTPTunnelPort
on Tor) to access onion website through the HttpClient. Onion website starts by http, but are indeed secure and the HTTP Proxy of Tor only support tunneling.Our current workaround hack is to code our own HTTP Socks proxy implementation in C#, which does not handle lot's of edge cases in HTTP.
The text was updated successfully, but these errors were encountered: