3 ms·
It would be very convenient if it worked that way, but it doesn't. $ https_proxy=http://localhost:8888 curl -vo /dev/null https://example.org * Tryin
by paulddraper 10y ago
It would be very convenient if it worked that way, but it doesn't.
$ https_proxy=http://localhost:8888 curl -vo /dev/null https://example.org
* Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 8888 (#0)
* Establish HTTP proxy tunnel to example.org:443
> CONNECT example.org:443 HTTP/1.1
> Host: example.org:443
> User-Agent: curl/7.35.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.0 200 Connection established
< Proxy-agent: tinyproxy/1.8.3
* Proxy replied OK to CONNECT request
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs
...
* Server certificate:
* subject: C=US; ST=California; L=Los Angeles; O=Internet Corporation for Assigned Names and Numbers; OU=Technology; CN=www.example.org
* start date: 2015-11-03 00:00:00 GMT
* expire date: 2018-11-28 12:00:00 GMT
* subjectAltName: example.org matched
* issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
* SSL certificate verify ok.
...
The protocol defined in https_proxy is irrelevant. CONNECT will be used, with a TLS tunnel.
- majewsky 10y agoThat's odd. I use mitmproxy at work to check how my apps call REST APIs on HTTPS endpoints, and I definitely don't have mitmproxy's interception CA installed.