Search squid archive

"Expires" Question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

if we request an cached object that is expired trough squid in
accelerator mode and record squids request to the webserver we see this:

GET http://acceltest/library/img/online.gif HTTP/1.0
If-Modified-Since: Tue, 28 Mar 2006 07:29:00.GMT
Host: acceltest
User-Agent: lwp-request/2.01
Via: 1.1 acceltest (squid/3.0.PRE5)
X-Forwarded-For: 192.168.1.2
Cache-Control: max-age=259200

the object on the webserver is unmodified so the webserver replies:

HTTP/1.1.304 Not Modified
Server: Microsoft-IIS/5.0
Date: Fri, 17.Nov.2006  14:24:18 GMT
X-Powered-By: ASP.NET
Cache-Control: max-age=60
Expires: Fri, 1 7.Nov.2006 14:25:18 GMT
ETag: "086ed473952c61:154b"
Content-Length: 0

Despite the new "Expires" squid receives, it still replies to the client
request with the old Expires and max-age values for the object. 

Is this correct behavior? For the browser this looks like the object is
stale and it will reload it from the cache for every subsequent request?

Thanks & regards 

Thomas 




[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux