How does this work for you: it depends on what you want. If you want certain URLs to be revalidated with every request, you should follow Joshua's advice and make sure that those resources are served with Cache-Control: must-revalidate. If the source server is an Apache and the resources are static files, you can probably use mod_headers (Header set or Header append) to achieve this. The downside of this strategy is that it makes caching the resource on the reverse proxy more or less pointless.
If you can accept a certain delay between the time where the source is updated and the update becomes effective for the client, playing with CacheDefaultExpires may get you there. The RP cache will be revalidated every time the cache entry becomes stale, and you can determine the interval using CacheDefaultExpires. That will reduce the number of requests that need to be forwarded all the way to the source. BR -ascs ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, January 12, 2006 3:27 PM To: users@httpd.apache.org Subject: RE: [EMAIL PROTECTED] Apache reverse and caching proxy Hello Axel-Stéphane, If I can follow what you are trying to tell me, I should add the "expiresactive on" directive on the source server instead of the caching server? Axel-Stéphane SMORGRAV <[EMAIL PROTECTED]> 12/01/2006 15:12 Please respond to users@httpd.apache.org --------------------------------------------------------------------- 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: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
