In fact, the CacheOn directive simply sets a variable in the mod_cache data structure which is never checked.
Is there any reason to keep this directive or can I go ahead and remove CacheOn and the code that sets and merges it (for no good reason)? Graham Leggett wrote: > Ask Bjoern Hansen wrote: > >> "CacheOn on" sounds pretty silly. Wouldn't it be better if it was >> "CacheOn yes" or just "Cache on"? :-) > > > Or another question: What does CacheOn do that CacheEnable doesn't > already do? > > Regards, > Graham -- Paul J. Reder ----------------------------------------------------------- "The strength of the Constitution lies entirely in the determination of each citizen to defend it. Only if every single citizen feels duty bound to do his share in this defense are the constitutional rights secure." -- Albert Einstein
