Lordran
Lordran
Yes,I left the problem, and this feature is neccesary. Exposing the parser should be a good solution. :)
@elazarl Hi,can you continue to merge this? This is a good feature for setting different proxy for CONNET method :)
@elazarl I have tested it with go 1.17.9(go version go1.17.9 linux/amd64), it works fine. Please review or think about this PR again? This is a key feature for case when...
@elazarl Ther eare three tests failed when build in my fork. But the build status is "success".
@elazarl These tests have the same result in current master. So I think this PR is OK.
@elazarl Meanwhile,I build with go 1.17,and get the same result ("success"),afterall, this PR dosen't use any new breaking grammar :)
@mikegleasonjr > If anyone comes here, I have an example to use a custom roundtripper for each request: > > ``` > rt := goproxy.RoundTripperFunc(func(req *http.Request, ctx *goproxy.ProxyCtx) (*http.Response, error)...
@uzxmx The code seems that cannot connect to multiple targets, you have to specify a target in **NewConnectDialToProxyWithHandler** :(
@mtatarau90 how to handle the concurrency problem?
This should be the way you want: https://github.com/elazarl/goproxy/tree/master/examples/cascadeproxy > client --> middle proxy --> end proxy --> internet