Seems I'm back at square 1. The idea of using max-age=0 did not work, which, on second thought, makes sense. CacheIgnoreCacheControl should ignore the "cache-control" header regardless of its value. The virtual host solution did not work either. It created new cache entries for the vhost.
-----Original Message----- From: André Warnier [mailto:[EMAIL PROTECTED] Sent: Monday, December 01, 2008 6:20 PM To: users@httpd.apache.org Subject: Re: [EMAIL PROTECTED] Clearing cache selectively on Apache + mod_cache Eric Covener wrote: > On Mon, Dec 1, 2008 at 11:09 AM, André Warnier <[EMAIL PROTECTED]> wrote: >> Which leads me to believe that, as such, the scheme proposed with the >> separate VirtualHost will not work as simply as expected. > > Yep, it looks like you'd need to jump through hoops to have a vhost > that was able to nuke these requests (using the same hostname on a > separate interface). Just intellectual curiosity : other than going through the source code of mod_cache, is there a description somewhere of the algorithm used by mod_cache to calculate this hashcode ? --------------------------------------------------------------------- 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] --------------------------------------------------------------------- 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]
