Henrik Nordstrom wrote:
> As you get a TCP_MISS/200 on the CONNECT request it's very unlikely to
> be a Squid problem. Squid has accepted the request, successfully
> connected to the requested server and connected the client and server
> together. Then your logs indiate one of them almost immediately
> disconnects... (doesn't tell which one unfortunately), or perhaps there
> was a networking issue which make the established connection fail.
Your config confirms that.
CONNECT and HTTPS ports are permitted to the three external client IP's
and to localhost.
>
>>>>>> This is what shows up in the access log:
>>>>>> 1213013343.566 CLIENT.EXTERNAL.IP TCP_MISS/200 39 CONNECT
>>>>> www.google.com:443 - DIRECT/72.14.205.104 -
>>>>>> 1213013984.055 CLIENT.EXTERNAL.IP TCP_MISS/200 39 CONNECT
>>>>> www.yahoo.com:443 - DIRECT/209.191.93.52 -
>
Amos
-- Please use Squid 2.7.STABLE3 or 3.0.STABLE7Received on Thu Jul 10 2008 - 04:10:38 MDT
This archive was generated by hypermail 2.2.0 : Thu Jul 10 2008 - 12:00:03 MDT