httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From john doe <>
Subject [users@httpd] Re: apache2: mod_cache: the order of CacheEnable and CacheDisable
Date Thu, 16 Jun 2005 00:42:52 GMT
Since nobody has replied so, I looked into its supposed source code:

The logic seems to be like this:
1. If a url matches ANY of the CacheDisable entries, don't cache it
and END of program.
2. Else if a url matches ANY of the CacheEnable entries, cache it and
End of program.
3. Else don't cache it and End of Program.

Based on the code, I conclude:
1. Order of CacheEnable and CacheDisable doesn't matter - they can be
mixed in any order.
2. CacheDisable takes higher priority over CacheEnable, a conservative
and prudent approach (which I happen to agree in lieu of a more
sophisticated water-down rule system as in Squid).

Any comments?

On 6/13/05, john doe <> wrote:
> By reading the apach2 doc, it's not clear what would happen if a
> mixture of CacheEnable and CacheDisable is present in the conf file.
> Consider the following two examples:
> Example1:
>      CacheEnable /
>      CacheDisable /cgi
> Example2:
>      CacheDisable /cgi
>      CacheEnable /
> In either case,  is /cgi cached?
> -jd

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message