All resources with 304 status code have receiving time set to 15000. This can be easily reproduced by loading some site (e.g. cnn.com) and pressing f5 to reload. This was caused by http://trac.webkit.org/changeset/102961 (https://bugs.webkit.org/show_bug.cgi?id=58354). Switching from currentTime() to monotonicallyIncreasingTime() in SubresourceLoader (see link below) fixes it, but I am not sure it won't break things on other platforms. http://codesearch.google.com/codesearch#OAMlx_jo-ck/src/third_party/WebKit/Source/WebCore/loader/SubresourceLoader.cpp&exact_package=chromium&q=subresourceloader&type=cs&l=164 simonjam@, could you please have a look on that?
Yep, that's the right fix. I'll upload a patch shortly.
Created attachment 122328 [details] Patch
Nate, it looks like you fixed revalidation shortly before I switched everything to monotonic time, and I missed your change. This should fix it to use monotonic time like the rest of resource loading. Would you mind reviewing it?
Comment on attachment 122328 [details] Patch Clearing flags on attachment: 122328 Committed r104887: <http://trac.webkit.org/changeset/104887>
All reviewed patches have been landed. Closing bug.
FYI: I filed http://code.google.com/p/chromium/issues/detail?id=110154 to merge it to Chromium M17.