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=43687>. 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=43687 ------- Additional Comments From [EMAIL PROTECTED] 2007-10-29 00:47 ------- (In reply to comment #5) > Ok, so I'm having a brain-dead moment (seem to be pretty common around > here :). This patch should do nothing at all, and it is a FireFox bug that > you are looking at (it shouldn't be sending 'if-modified-since' and 'if-none- > match' headers, since it was already told that the page is uncachable). IMHO it isn't firefox bug. RFC2616 (14.9.1 What is Cacheable) about "Cache-control: no-cache" says: If the no-cache directive does not specify a field-name, then a cache MUST NOT use the response to satisfy a subsequent request without successful revalidation with the origin server. This allows an origin server to prevent caching even by caches that have been configured to return stale responses to client requests. So because tomcat sends for static resources "ETag" and "Last-Modified" headers it allow to make REVALIDATION by firefox. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
