This way you may end up connecting to your proxy on the same port/ip one time with plain http and the other time with https. This is unfortunate as both aren't correlated. Wrong thing) (: this is the reason for your last error) Again, the reason one should add the scheme is that you most will likely use the same proxy for both http and https.Īs requests will guess the proxy scheme based on the request scheme. (My squid for example doesn't care and does the right, erm. Proxied https requests are therefore sent in plaintext in the form of GET HTTP/1.1 This is not how https should be proxied and why you get the error at your proxy. (This is how all those http proxy tunnels work) Urllib3 doesn't support CONNECT at the moment (will be supported very soon!). The proxies then decodes the body and forwards the raw data, receives the response, reencodes it and sends the raw, encoded response back to the requester. Http requests made using CONNECT are sent to the proxy where the body of the request is the encoded raw data of the tcp connection. This is where the http 'CONNECT' verb is used. (This is what the scheme in the proxy url is for) The proxy can handle plain http requests just fine.Įncrypted connections are just some random tcp stream to the proxy. The connection between requests and the proxy is mostly http. _ squid-users mailing list I'll recap the issue with the scheme:-) Most people use one proxy for both http and https. Error 'ipcacheParse: No Address records in.
0 Comments
Leave a Reply. |