graftcp VS dorkscout

Thanks, that's super useful.

> If you try to use go's package manager, example: `go get golang.org/x/oauth2`

I just tested, and `go get golang.org/x/oauth2` seems to work fine for me, I can see all the requests being happily intercepted immediately: https://imgur.com/a/Cb1y9Q2

Can you see the 500 in HTTP Toolkit, and any more info there (in the body or as an error at the top) related to that? Or can you see a "certificate rejected" message? If nothing turns up there at all then yes, something must be overriding the proxy configuration.

Maybe you have some other Go package manager configuration that conflicts with this? I'd be very interested to know about that if so, I'm sure there's others with the same thing. It's always very hard to know if my configuration is representative of normal devs for any given language/tool.

Probably best to debug this outside of a HN thread though :-). You can file a proper issue about this at https://github.com/httptoolkit/httptoolkit/issues/new, I'd love to know what's going on there and get this fixed.

> I ended up using https://github.com/hmgle/graftcp which somehow manages to force tcp traffic through a socks5 proxy.

Really interesting, thanks! I'll look into that.

unfortunately golang doesn't work with proxychains :( but you can still use other tools such as graftcp or specify a proxy with the -x or --proxy flag that uses multiple proxy's like multitor or just use the tor proxy which is the simplest way.