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=42425>. 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=42425 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO ------- Additional Comments From [EMAIL PROTECTED] 2007-05-15 13:08 ------- I do not get your problem here. Caching is only denied if there is an Expires header and if the time mentioned in the Expires header is earlier then the request time. If this comparison becomes true only due to the different granularity of the times measured (which can happen) this means that the difference between the time in the Expires header and the request time is less than a second. So there is a very short period of time (less than a second) during which this entity (if it is cached) would be regarded as fresh and thus deliverable to the client from the cache without further revalidation. So what is the point in having cached objects that are that short lived? -- 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]
