Re: [squid-users] Why no graphics?

One thing that may be of importance here is that images.google.com
uses a DNS ttl of only 300 seconds... but this does not seem to be
your problem as Squid indicates the requests was processed rather
quickly.. (260-490 msec).

Perhaps you have networking problems like a mismatch between full/half
duplex in the negotiaion between your Squid server and the switch or
similar problems?

It could also be a mismatch in persistent connection management
between your browser and Squid. Some browsers are a bit buggy... try
if disabling the use of persistent connections help, and report back
here if it does..

  client_persistent_connections off

and/or

  server_persistent_connections off

Regards
Henrik

On Wednesday 10 July 2002 05.06, Carolyn Longfoot wrote:
> Hey,
>
> I'm behind a packet filtering firewall (IPFW on FreeBSD 4.5) that
> *all* traffic goes through, so it should not affect Squid in
> particular.
>
> I should be more specific in that the images (for example from
> http://images.google.com/images?q=july+4th&svnum=10&hl=en&lr=&ie=UT
>F-8&oe=UTF-8&start=20&sa=N) do eventually show up but it's slow as
> an ant carrying a piano.
>
> Access.log shows a whole bunch of TCP misses, like so:
> 1026269112.638 466 10.0.0.11 TCP_MISS/200 5570 GET
> http://images.google.com/images? - DIRECT/216.239.51.126 image/jpeg
> 1026269233.617 224 10.0.0.11 TCP_MISS/200 5262 GET
> http://images.google.com/images? - DIRECT/216.239.33.126 image/jpeg
> 1026269233.658 263 10.0.0.11 TCP_MISS/200 3495 GET
> http://images.google.com/images? - DIRECT/216.239.33.126 image/jpeg
> 1026269233.829 434 10.0.0.11 TCP_MISS/200 3516 GET
> http://images.google.com/images? - DIRECT/216.239.51.126 image/jpeg
> 1026269233.887 491 10.0.0.11 TCP_MISS/200 5614 GET
> http://images.google.com/images? - DIRECT/216.239.51.126 image/jpeg
>
> Cache.log does not seem to show anything unusual either:
>
Received on Wed Jul 10 2002 - 04:31:28 MDT