You are exactly right. However, the real question is: why does the request contain that max-age directive? Returning a s-max-age should not prevent the cache from revalidating the response with the origin server. To get the best performance you want to 1. avoid having the browser revalidating the response each time it requires it 2. avoid having the cache revalidating the response with the origin server for each request I also note that the Date header is older than the Last-Modified. -ascs -----Message d'origine----- De : Marko Asplund [mailto:marko.asplund@xxxxxxxxxx] Envoyé : dimanche 9 décembre 2007 22:18 À : users@xxxxxxxxxxxxxxxx Objet : Re: Reverse proxy cache control problems After reading a bit more on what RFC 2616 says about Cache-control I figured out it was apparently the Cache-Control: max-age=0 header the browser was sending that made mod_cache not use the cached copy even though the server was returning Cache-Control: max-age=3600 After switching the line to Cache-Control = s-maxage=3600 caching seems to be working as planned. Another option would've been to use the following configuration directive: CacheIgnoreCacheControl On marko --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|