On Tuesday 12 March 2002 14:59 pm, Shridhar Daithankar wrote: > A dumb thought. Is http proxy same as https proxy? If you are using proxy > is it configured for https?
Well, squid proxy does both. But the principle of operation is different. With HTTP Proxy, the client connects to the proxy server instead of the web server, and issues a GET http://www.whatever.com/path/hello.html HTTP/1.0 request. The proxy server manages the actual connection to the web server, and serves the page to the client, optionally caching the page. With HTTPS Proxy, the client connects to the proxy server, and issues a CONNECT ip.address.of.actualserver:portno HTTP/1.0 request. The proxy server connects to the server, and then steps out of the way - the client is the one who actually requests web pages and manages the certificates etc. of the server. There is no caching involved. With the CONNECT method, the port needn't be 443 (https). It can be anything - for example, here is a sample session with my squid proxy: binand@binand[~]:(6) telnet proxy 3128 Trying 10.0.2.3... Connected to gw1. Escape character is '^]'. CONNECT 10.0.2.2:25 HTTP/1.0 HTTP/1.0 200 Connection established 220 mailserver.cysphere.com ESMTP EHLO there 250-mailserver.cysphere.com Ok. [snip] You should download transconnect from http://transconnect.sourceforge.net. It uses this CONNECT method to tunnel non proxy-aware applications via a squid proxy. Of course, this opens up all ports that admins might want to firewall out. So, generally CONNECT is acl'ed to be limited to the https port. (I opened it up to generate the example above :-) Binand _______________________________________________ linux-india-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/linux-india-help
