On Wed, Apr 30, 2008 at 8:37 AM, Marko Asplund <marko.asplund@xxxxxxxxxx> wrote: > As far as I've understood the below setup would not correctly cache > request content when using request parameters (requires Expires header). > What would be the best way to fix this? See the CacheIgnoreQueryString directive. > > How will the Cache-Control and Expires (ExpiresByType) work together? The Expires* directives also set max-age on Cache-Control. Using those directives, you are influencing how down-stream caches will behave, not the local cache. The local cache would need to see those directives coming from the upstream (if I remember correctly). You'll want to use the CacheDefaultExpire directive to control the local cache. Unfortunately, I don't think it is possible to set different expiration times within the same host, since this directive can't be placed in <Directory>/<Location> sections. > > Is it possible to have the cache asynchronously update cached content so > that the last request would be served with expired content but behind > the scenes the cache would update the content once expired content is > requested? This feature has been discussed by the developers, but is not currently implemented to the best of my knowledge. Joshua. --------------------------------------------------------------------- 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
|