Jerome Yanga wrote:
Resending as I had received a failure notice message.
I do not think that the refresh_pattern is even setup as they are all
commented out.
# grep refresh_pattern /etc/squid/squid.conf
# refresh_pattern regex min percent max
#refresh_pattern -i \.js$ 0 0% 1
#refresh_pattern -i \.css$ 0 10% 30
#refresh_pattern . 0 20% 4320
Attached is a zipped http header log captured using Live HTTP Headers.
Regards,
Jerome
Sample squid log entry from the zip file (without cookies) for reference:
------------------------
TCP_REFRESH_HIT:FIRST_UP_PARENT 10.11.12.13 10.10.10.10 - -
[06/Jun/2008:21:42:52 +0000] "GET
http://site_address.com/help/chr_ind_on.gif HTTP/1.1" 302 830
"http://site_address.com/help/whskin_tbars.htm"; "Mozilla/5.0 (Windows;
U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14"
------------------------
There were no associated HTTP headers for this object
(http://site_address.com/help/chr_ind_on.gif)*, but here is another
request that also resulted in a 302 (Moved Temporarily):
------------------------
GET /help/chr_back.gif HTTP/1.1
Host: site_address.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14)
Gecko/20080404 Firefox/2.0.0.14
Accept: image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://site_address.com/help/whskin_tbars.htm
Cookie: [removed]
HTTP/1.x 302 Moved Temporarily
Date: Thu, 05 Jun 2008 23:40:54 GMT
Location:
http://site_address.com/gateway/index.cfm?fa=login&returnURL=http%3A%2F%2Fsite_address%2Ecom%2Fhelp%2FFchr%5Fback%2Egif
Cache-Control: max-age=0
Expires: Thu, 05 Jun 2008 23:40:54 GMT
Content-Length: 422
Content-Type: text/html; charset=iso-8859-1
Connection: keep-alive
------------------------
The redirection just has a "Cache-Control: max-age=0", which allows the
cache to store the response, and just requires that it be revalidated
(which is done as evidenced by the TCP_REFRESH_HIT in the Squid log).
So, I'm still not seeing anything being cached against the server's
request. Try tailing the access log and grep for " 200 " and "HIT"**
(note the spaces on either end of the 200). That should show any
objects (as opposed to redirects or errors) that are served from cache.
Chris
* The other URL (http://site_address.com/help/whskin_tbars.htm) it the
referrer.
** tail -f /cache/logs/access.log | egrep "10.10.10.10.* 200 .*HIT"
