Re: [squid-users] Squid and Cocoon Problem

> tor 2007-06-28 klockan 12:57 +0200 skrev jsianes@andaluciajunta.es:
>> Hello. I have an Squid proxy cache configured as frontend of a Coocoon
>> server.
>> The problem is I always get a TCP_MISS. Here is an example of two clicks (2
>> seconds between them) over the same link:
>>
>> 1183027652.407 320 10.240.216.71 TCP_MISS/200 16870 GET
>> http://intranet.juntadeandalucia.es/cocoon/aj-ic--.html? -
> [...]
>> [HTTP/1.1 200 OK\r\nX-Cocoon-Version: 2.1.7\r\nVary: Cookie\r\nVary:
>> User-Agent\r\nExpires: Thu, 28 Jun 2007 10:57:32 GMT\r\nCache-Control:
>> max-age=600, public\r\nContent-Type: text/html\r\nDate: Thu, 28 Jun 2007
>> 10:47:32 GMT\r\nServer: Apache-Coyote/1.1\r\nConnection: close\r\n\r]
>
>> As you can see, the second click get a TCP_MISS when the expiration date is
>> obvious not expired yet (max-age=600, 10 min). Why Squid is not making a
>> HIT?
>> Any comment will be very appreciated. I'm using Squid 2.6 version.
>
>
> Comments:
>
> 1. Are you really sure the URL is the same? What's after the ? (set
> "strip_query_terms off" to have it logged..)

Yes, the query terms are exactly the same.

> 2. With those Vary headers (Cookie, User-Agent) it's not much point of
> caching as every session is unique and is not allowed to share content..

The vary header includes all sessions IDs used by application, so it's not a
problem at all.

I just have found the problem: by default, Squid doesn't cache any QUERY
string due to an ACL definition. Cocoon always use query strings so, by ACL,
is never cached. The solution is as simple as comment that no_cache ACL
referenced to QUERY and all works perfectly. Thanks for all.

Javier Sianes
Received on Fri Jun 29 2007 - 00:26:12 MDT