Re: [squid-users] Problem: Squid3 accelerator does not cache

On Wed, 28 Jul 2004, Petri Välisuo wrote:

> I am trying to use squid-3.0-PRE3 as a http-accelerator, using http_port
> configuration:
> http_port 10.10.1.39:80 vhost defaultsite=10.10.3.46
>
> It seems that all accesses are denied, unless I use also the
> always_direct allow ALL
>
> configuration option or configure origin server as cache peer:
> cache_peer 10.10.3.46 parent 80 0 originserver

Correct. This is intentional and documented in the release notes.

> Now the squid passes traffic through, but _it_does_not_cache_anything!??

It should cache..

> 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?

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).

Regards
Henrik
Received on Fri Jul 30 2004 - 17:38:04 MDT