Uh oh!
There was an error while loading. Please reload this page.
WIP: SOCKS proxy support - #51
Conversation
| origin: Origin, | ||
| proxy_origin: Origin, | ||
| socks_version: str, | ||
| user_id: bytes = b"httpcore", |
There was a problem hiding this comment.
This is required by SOCKS4.
SOCKS5 will require username/password and likely defining acceptable authentication methods. Which makes me think we might want separate AsyncSOCKS4Connection and AsyncSOCKS5Connection.
Uh oh!
There was an error while loading. Please reload this page.
yeraydiazdiaz
commented
Apr 1, 2020
I realize there's a fair bit of cleanup noise as well, sorry about that. Hopefully the important bits are clear. |
Uh oh!
There was an error while loading. Please reload this page.
yeraydiazdiaz
commented
Apr 30, 2020
Yep, this branch predates the recent changes regarding proxies. Will update it soon. |
yeraydiazdiaz
commented
May 16, 2020
I think I'll hold off on this until we've decided if proxy modes are something we want at all. |
lovelydinosaur
commented
Jan 18, 2022
SOCKS5 is now supported in 0.14.5 - https://www.encode.io/httpcore/proxies/#socks-proxy-support (Not sure what we'd want to do about socks4, socks4a) |

Adds SOCKS4 proxy support via socksio 🎉
You can test this either locally using Dante via Docker as we do in socksio or simply running an
ssh -vND <PORT> <OTHER_MACHINE>, then running the following script, assuming the proxy is running inlocalhost:1080:Before I carry on with SOCKS4A and SOCKS5 (or possibly I should open a different PR?) I'd like some feedback.