I think there is a terminology confusion here.
Squid (any version) can act fine as a https proxy/tunnel using the
CONNECT method.
The CONNECT method is abused by some applications to proxy other TCP
traffic than SSL. This is not what the CONNECT method is meant to be
used for, but it can. Generally it is recommended to consider installing
a SOCKS proxy in such case to have more controlled proxying of general
TCP connections (see Dante if you need a SOCKS proxy server).
Squid 2.5 can also accept proxy connections over SSL to have the
communication between your browser and the proxy encrypted, but there is
no browsers supporting SSL encrypted proxies.
For https proxying over SSL this would result in that the traffic is
encrypted twice. Once for the proxy connection browser<->proxy, and once
for the browser<->webserver end-to-end connection via the proxy.
Regards
Henrik Nordström
fre 2013-01-18 klockan 01.56 skrev Fathi Ben Nasr:
>
> Hello,
>
> Someone wrote that squid can act as an https proxy (i.e. connections
> between squid and web client are secured) but there was no client
> implementing it.
> Now using aim 4.7.2480, in its config panel I can choose a proxy talking
> https and enter my proxy ip port username and password.
> It works if I use squid as a http proxy but not as an https proxy.
> Is there some server cert I should install on squid subdirs or is aim
> buggy or talks only to netscape https proxies ?
>
> TIA.
> Fathi Ben Nasr
>
> (See attached file: smime.p7s)
Received on Thu Nov 07 2002 - 07:52:20 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:11:12 MST