story mechanism may display
the content last seen by the user even if it has expired.
Regards,
Oliver Schoett
says only that caches should, not that they must obey this directive.
Regards,
Oliver Schoett
plit, this can become confusing, as the
state of this bug and its dependencies may be different in 2.x and in
3.x, and the Bugzilla dependency list does not reflect that. For
example, bug 7 (which can hurt performance badly) is supposedly fixed in
2.7, but not yet in 3.x.
Regards,
Oliver Schoett
Oliver Schoett wrote:
Cache-Control: private
Expires: Mon, 01 Jan 2007 00:00:00 GMT
Sorry, but this is still not optimal. The Expires: date in the past
will also defeat caching by HTTP 1.1 caches. RFC 2616 allows for HTTP
1.1 directives to override the Expires: date of HTTP 1.0 as
must be so restrictive that no unwanted caching by HTTP 1.0
caches can occur. This may hurt performance, but that is better than
wrong results.
Regards,
Oliver Schoett
helps
performance, because
* stale resources in the cache are replaced by fresh ones,
* uncompressed resources in the cache are replaced by compressed
ones if the browser supports it.
So you can refresh the cache as a user by issuing forced reload requests.
Regards,
Oliver Schoett
s of Bug 7
(http://www.squid-cache.org/bugs/show_bug.cgi?id=7)? This bug makes
Squid deliver resources with expiration times in the past, thus causing
the clients to revalidate the resources every time they are used.
Regards,
Oliver Schoett
work.samba.java).
Regards,
Oliver Schoett
they are distinguished by their
jsessionid. If the jsessionid is passed in a cookie instead, all users
fetch the same URL
http://x.y/app/showUserProfile
and might end up seeing each other's profiles when squid caches this URL.
Regards,
Oliver Schoett
quid every time. This greatly lengthens page loading times, as the
latencies of all the verification requests sum up to long delays, even
if the 304 responses are short.
Regards,
Oliver Schoett
10 matches
Mail list logo
