Re: [squid-users] http_accel question

AJ Lemke wrote:
>
> Do these look like the headers are getting through? I see the
> Cache-Control: public, max-age=30 in them.
>
> 208.248.72.14 - - [04/Oct/2001:16:40:41 -0500] "GET
> http://cache.cartrucktrader.com/Listings/ListingsDealer.cfm? HTTP/1.0" 200
> 22531 TCP_MISS:DIRECT [

Request Headers:

 Referer: http://cache.cartrucktrader.com/Listings/
 Connection: Keep-Alive
 User-Agent: Mozilla/4.77 [en] (Windows NT 5.0; U)
 Host: cache.cartrucktrader.com
 Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, image/png,
*/*
 Accept-Encoding: gzip
 Accept-Language: en
 Accept-Charset: iso-8859-1,*,utf-8
 Cookie: CFID=3783; CFTOKEN=14098151

Reply Headers:

 HTTP/1.1 200 OK
 Server: Microsoft-IIS/5.0
 Date: Thu, 04 Oct 2001 21:40:53 GMT
 Content-type: text/html
 Page-Completion-Status: Normal
 Cache-Control: public, max-age=30
 Page-Completion-Status: Normal

So sure, the header is there now.

> 208.248.72.14 - - [04/Oct/2001:16:40:47 -0500] "GET
> http://cache.cartrucktrader.com/Listings/ListingsDealer.cfm? HTTP/1.0" 200
> 22538 TCP_HIT:NONE
> 208.248.72.14 - - [04/Oct/2001:16:40:52 -0500] "GET
> http://cache.cartrucktrader.com/Listings/ListingsDealer.cfm? HTTP/1.0" 200
> 22539 TCP_HIT:NONE
> 208.248.72.14 - - [04/Oct/2001:16:40:56 -0500] "GET
> http://cache.cartrucktrader.com/Listings/ListingsDealer.cfm? HTTP/1.0" 200
> 22539 TCP_HIT:NONE
> 208.248.72.14 - - [04/Oct/2001:16:41:00 -0500] "GET
> http://cache.cartrucktrader.com/Listings/ListingsDealer.cfm? HTTP/1.0" 200
> 22539 TCP_HIT:NONE
> 208.248.72.14 - - [04/Oct/2001:16:41:03 -0500] "GET
> http://cache.cartrucktrader.com/Listings/ListingsDealer.cfm? HTTP/1.0" 200
> 22539 TCP_HIT:NONE
> 208.248.72.14 - - [04/Oct/2001:16:41:07 -0500] "GET
> http://cache.cartrucktrader.com/Listings/ListingsDealer.cfm? HTTP/1.0" 200
> 22539 TCP_HIT:NONE
> 208.248.72.14 - - [04/Oct/2001:16:41:22 -0500] "GET
> http://cache.cartrucktrader.com/Listings/ListingsDealer.cfm? HTTP/1.0" 200
> 22539 TCP_HIT:NONE
>
> That should allow caching for only 30 seconds, that is what we are testing
> with.
>
> We are close. Again Thanks for you help

You are more than close. As seen above the object is now cached.

But I'd recommend you to use Expires rather than Cache-Control.

I think I have found why you are having such problems getting things
cached. Squid has a fence time of 60 seconds for objects which cannot be
revalidated. If such an object is fresh for less then 60 seconds then
Squid in most cases do not consider it worth caching. To change this,
see refresh.c:refreshIsCachable

Regards
Henrik Nordström
Squid Hacker
Received on Fri Oct 05 2001 - 01:06:35 MDT