[wp-trac] [WordPress Trac] #22258: nocache_headers fail to prevent aggressive caching in Chrome

[WordPress Trac]

#22258: nocache_headers fail to prevent aggressive caching in Chrome
------------------------------+--------------------
 Reporter:  andy              |       Owner:
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  3.5
Component:  General           |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |
------------------------------+--------------------

Comment (by nacin):

 RFC2616 doesn't say much about this, but some reading:
 http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-13#page-10.
 If the Date and Last-Modified headers are within 60 seconds (and they
 would be here, barring a server misconfiguration), it is considered a weak
 validator, because of potential timing inconsistencies; they are also
 considered weak for being only accurate to the second.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/22258#comment:7>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software