You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/12/04 15:10:30 UTC
DO NOT REPLY [Bug 25201] New: -
Provide Cache Purge operation
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
Summary: Provide Cache Purge operation
Product: Apache httpd-2.0
Version: 2.0.48
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: mod_cache
AssignedTo: bugs@httpd.apache.org
ReportedBy: fmeschbe@day.com
We place Apache httpd 2.0 in front of our CMS product as a caching reverse proxy
to enhance performance. While the cache properly works managing its cached
resources there is currently no functionality for the CMS product to inform the
proxy about changed content.
I propose to enhance the mod_cache module to support a new configuration
directive "CachePurgeMethod" with default "PURGE". When a request for such a
method comes in the mod_cache handles it by trying to remove the indicated cache
entry.
If the cache entry exists, the .data and .header file is removed and the request
is terminated with a OK/200 status. If no cache entry exists for the request
URL, the request is terminated with a NOT_FOUND/404 status.
This behaviour (method to purge a cache entry and the status codes for
(un)successfully removal) is sketched after the PURGE method support of the
squid cache. See http://www.squid-cache.org/Doc/FAQ/FAQ-7.html#ss7.5 for short
information.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org