On Tue, 09 Mar 2010 21:42:42 +0100, Jan Houtsma <list_at_houtsma.net> wrote:
> Op 9-3-2010 21:37, Henrik Nordström schreef:
>> tis 2010-03-09 klockan 19:49 +0100 skrev Jan Houtsma:
>>
>>
>>> Yes. The wget was from the squid server itself where using the proxy
it
>>> fails, and using direct internet connection it works.
>>>
>> What does access.log say when it fails? Do the reported server address
>> match what you expect it to be for the requested host?
>>
>
> 1268167273.909 250 192.168.1.16 TCP_MISS/503 4234 GET
> http://www.google.com/ - DIRECT/www.google.com text/html
>
>>
>>> So when squid is forwarding the http-GET request it fails. But when
wget
>>> itself sends the http-GET request it works.
>>>
>> Perhaps time to fire up wireshark to look at the traffic..
>>
>> The error message received is very low level.. squid could not even
open
>> the TCP connection to the server.
>>
>> Regards
>> Henrik
>>
>
> Yea, will do that
That log trace you showed had Squid attempting and failing to connect to
IPv6-google.
I would suspect a v6 routing failure here. Squid-3.1 has known bugs with
failover to IPv4 if IPv6 fails on a mixed-IP domain.
Does the wget direct test you made from the Squid box use google IPv6
addresses for its succeeding connection?
Amos
Received on Wed Mar 10 2010 - 00:45:00 MST
This archive was generated by hypermail 2.2.0 : Wed Mar 10 2010 - 12:00:03 MST