Thanks for the response. That's not really going to be an issue in my case, since this cache is sitting at the back end of the application stack, and actually consists of small components that are later assembled into a complete page. The outside world never gets to access the cache directly. I could write an application to do all this of course, but it seems like most of the functionality is already there in a reverse proxy.
Sam. On 07/02/2008, Vincent Bray <[EMAIL PROTECTED]> wrote: > > On 06/02/2008, Sam Crawley <[EMAIL PROTECTED]> wrote: > > I'm looking to setup a reverse proxy with Apache 2.2 and mod_cache / > > mod_proxy. I need to be able to do the following things: > > > > 1. Force an item in the cache to expire now (i.e. the next time someone > > accesses it, it will get it from the origin) > > You're missing the fundamental point of http caching: that resources > can be cached by any agent on the wider web based on the constraints > (usually time based) of the original response. Any subsequent requests > can't affect that, for those proxies. I would guess that you'd be > better off getting your application to cache its responses to file. > > -- > noodl > > --------------------------------------------------------------------- > 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] > >
