DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=30399>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30399 mod_cache caching Set-Cookie headers Summary: mod_cache caching Set-Cookie headers Product: Apache httpd-2.0 Version: 2.0.50 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: mod_cache AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] Hi, I have a question regarding mod_cache's behaviour about caching response headers. I noticed that mod_cache also stores cookies (or better the Set-Cookie header) with all the other End-to-end headers (see 13.5.1 RFC 2616). As I can see from the RFC this is required to be RFC 2616 compliant. In my special case this is a problem because I try to use mod_cache to cache Tomcat generated jsps for performance reasons. Currently I help myself by adding apr_table_unset(headers_out, "Set-Cookie"); to ap_cache_cacheable_hdrs_out. As this approach breaks RFC 2616 compliance I am sure that this approach will never be part of the official Apache code. To prevent patching of future Apache versions I would like ask to if there is any chance that an additional configuration directive will be added to mod_cache that allows to define headers that should not be cached. Of course setting this directive in your configuration would break RFC 2616 compliance of mod_cache, so the default value for this directive should be empty or none. Regards Rüdiger Plüm --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
