Search squid archive

Re: Configuring cache_peer to use ssl

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Quoting Amos Jeffries <squid3@xxxxxxxxxxxxx>:

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

And finally, does the patch for the bug change things?
http://www.squid-cache.org/bugs/show_bug.cgi?id=2332

after applying patch on STABLE5, on the parent proxy side i see such messages

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)

or:

2008/05/15 11:25:54| clientNegotiateSSL: Error negotiating SSL connection on FD 16: error:1407609B:SSL routines:SSL23_GET_CLIENT_HELLO:https proxy request (1/-1)

BUT - only in case i am trying to connect to https:// sites. for the normal ones everything works.

Both ends are identical - slack 12.1, squid3.0STABLE5 with patch, running now with log level 1

Janis



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.




[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux