Quoting Rob Asher [EMAIL PROTECTED]:
blocking egress traffic for everything except known services(our own
proxies) so anonymous proxies and vpn's won't be able to
connectUNLESS they can get to them through the proxies somehow.
Things like PHProxy and all the anonymizing sites make
Quoting Henrik Nordstrom [EMAIL PROTECTED]:
A workaround is to forward CONNECT requests over http as usual instead
of wrapping them in yet another ssl layer. Another workaround if you
really MUST wrap the CONNECT requests in SSL between the proxy servers
is to offload the SSL wrapper from Squid
Quoting Amos Jeffries [EMAIL PROTECTED]:
in access.log
192.168.0.1 TCP_MISS/000 0 CONNECT sourceforge.net:443 -
FIRST_UP_PARENT/__ip__ -
What does cache.log have to say about those failed requests?
What version is the parent cache? Same details from them if possible.
it says nothing
Quoting Henrik Nordstrom [EMAIL PROTECTED]:
On tor, 2008-05-15 at 11:27 +0300, Jancs wrote:
2008/05/15 11:20:04| clientNegotiateSSL: Error negotiating SSL
connection on FD 17: error:1407609B:SSL
routines:SSL23_GET_CLIENT_HELLO:https proxy request (1/-1)
This means a proxy client contacted
Quoting Amos Jeffries [EMAIL PROTECTED]:
Janis wrote:
I succeded in setting up chain of proxies using ssl for
inter-communication, but - i lost possibility to tunnel https
requests - instead of it i get empty page without any messages.
Where should I look to correct this?
Could be
