> On Wed, 28 Jul 2004, Petri V�lisuo wrote: I was using squid 3.0-PRE3 as http-accelerator. I had problems with it, because it didn't cache, but complained that all requests were TCP_CLIENT_REFRESH_MISSES like I explain below.
> > 1091015921.988 2 10.100.4.2 TCP_CLIENT_REFRESH_MISS/200 3268 GET > > http://laulurastas2.intra.wasalab.com/ - FIRST_UP_PARENT/10.10.3.46 > > text/html [Host: laulurastas2.intra.wasalab.com\r\nAccept: text/html, > > text/plain, text/sgml, */*;q=0.01\r\nAccept-Encoding: gzip, compress, > > bzip2\r\nAccept-Language: en\r\nUser-Agent: Lynx/2.8.6dev.4 libwww-FM/2.14 > > SSL-MM/1.4.1 GNUTLS/0.8.12\r\n] [HTTP/1.1 200 OK\r\nDate: Wed, 28 Jul 2004 > > 11:58:41 GMT\r\nServer: Apache/1.3.23 (Unix) (Red-Hat/Linux) > > PHP/4.1.2\r\nLast-Modified: Tue, 09 Apr 2002 18:56:58 GMT\r\nETag: > > "16ddb-b4a-3cb3397a"\r\nAccept-Ranges: bytes\r\nContent-Length: > > 2890\r\nConnection: close\r\nContent-Type: text/html\r\n\r] > > > > Could somebody please explain me what could be matter or suggest further > > tests and configuration options. Or do I really need to go one step back > > and use squid2.5? On Sat, 31 Jul 2004, Henrik Nordstrom wrote: > The above looks wrong. I think you should file a bug report. > TCP_CLIENT_REFRESH_* should only be logged if the client forced a refresh, > which yours did not. > > Also make sure you are using a current nightly snapshot release of > Suqid-3.. the PRE3 release is way old and a lot have changed since then > (for good and bad). This was the reason! I updated the squid to 3.0-PRE3-20040801 and now it works great. Even though I think that the Squid 2.5 works faster in my configuration. I am using SquidGuard and a lot of rules to deny web attack urls known by snort. It may be the squidGuard which slows down the service. Thanks for help. -petri -- Petri V�lisuo <[EMAIL PROTECTED]> +358 44 767 7774 PGP: http://www.wasalab.com/~petri/gpg_public_key.txt ICQ: 176287479
