httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 25201] - Provide Cache Purge operation
Date Sun, 14 Dec 2003 10:05:25 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25201>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25201

Provide Cache Purge operation





------- Additional Comments From fmeschbe@day.com  2003-12-14 10:05 -------
if <limit> itself can do what i want it to do :

 - define the name of the method mod_cache accepts to purge a cache entry
 - define restrictions on the use of this same method
 - being limited to mod_cache - that is having no influence on other modules or
   overall configuration and not being influenced from other modules or
   overall configuration

then limit is ok, don't you think ?

but ! if limit cannot do this or if limit may be overruled from outside the
mod_cache configuration, <limit> is not ok.

as - to my knowledge - there is no special container directive for mod_cache
other than <directory>, etc., i think there must be a special named directive,
which exactly does what i want it do (see list above).

maybe i just miss some point, in which case i gladely agree to whatever you propose.

btw: the intended idea of having a directive defining the name of the method to
use is, that mod_cache will handle the request and not give any other module a
chance to see the request in case mod_cache can handle it. and to my knowledge
there is no standard method named 'PURGE' [i only know that squid uses this
method exactly for this purpose]

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message