Bisected to 5113ad0, only affects http without proxytunnel. I didn't use the gist script for reasons noted below, instead I manually monitored socat output to see when the CONNECT GET lines would show (if they did bisect good, if they didn't bisect bad). socat openssl-listen:4433,reuseaddr,fork,cert=yourcerthere.pem,verify=0 -
The reason I didn't use the gist script is because that was a very narrow example written to help us reproduce an issue with a proxytunnel to google's server. if you look in the script you'll see that. Technically you could repurpose it by changing the line in the script to net.Dial("tcp", "www.google.com:80") and then add curl option --proxytunnel since curl by default won't tunnel http connections, but the bug is not reproducible then.
@bagder yes I mean't HTTPS proxy (title updated, sorry!).
In this very specific case, the gist script represents the problem quite well. I'm actually hitting the issue with a different HTTP proxy implementation, so it's not specific to the gist script. More specifically, it seems to be:
GET instead of CONNECT (i.e. no --proxytunnel option)
I did this
I expected the following
What actually happened
...hangs at this point
macOS Sierra 10.12.6
This is the same behaviour as: #1156
I am using the same gist to run a basic HTTPS proxy.
The text was updated successfully, but these errors were encountered: