On Wed, Jan 14, 2009 at 7:41 AM, Karim Zaki <karim.z...@itworx.com> wrote: > All, > > I need to have mod_cache process requests after mod_rewrite is done with > them. The reason I need this is that CacheEnable only accepts a path and will > cache everything under that path, while I need to cache based on more > granular criteria...so I need mod_rewrite to look at the request and modify > it, and then mod_cache to see the modified URI and act accordingly. mod_cache > should not cache any request that's been modified by mod_rewrite, since it > would no longer fall under the cacheable path. However, what happens is that > mod_rewrite modifies the URI, but mod_cache still sees the original URI. > > I googled and found two old threads from 2005 and 2007 discussing mod_cache > being a "quick" handler and citing this as the reason for this behavior. Is > there any way around it?
The next 2.2.x release will allow you to do E=no-cache:1 to prevent a response from being saved by mod_cache. http://httpd.apache.org/docs/2.3/env.html -- Eric Covener cove...@gmail.com --------------------------------------------------------------------- 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-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
