proposal: net/http: increase verbosity of unsuccessful proxy CONNECT request #40873
Comments
Duplicate of #38143 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Duplicate of #38143 |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
So in my environment http://antipa.hiblogger.net redirects to https://www.obozrevatel.com/blogs/
When I use direct connect without proxy, its working fine.
With Proxy it got intercepted with 302 (full response in Additional info) to my provider ban page http://blacklist.miralogic.ru and all I see in the error is "Found".
My code
What did you expect to see?
I suggest to change the error in
go/src/net/http/transport.go
Line 1684 in cdc77d3
and
go/src/net/http/transport.go
Line 1682 in cdc77d3
from
errors.New
with Status Text to something more verbose to better understand the nature of the problem (It's a proxy CONNECT error).Maybe there should be something like net.OpError like in
go/src/net/http/transport.go
Line 1545 in cdc77d3
What did you see instead?
Output:
Additional info
Response from CONNECT response (variable resp in dialConn function
go/src/net/http/transport.go
Line 1531 in cdc77d3
The text was updated successfully, but these errors were encountered: