[Webkit-unassigned] [Bug 30862] Dynamically inserted subresources aren't revalidated even when the containing document is reloaded

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=30862





--- Comment #30 from Darin Fisher (:fishd, Google) <fishd at chromium.org>  2011-02-02 17:03:56 PST ---
(In reply to comment #29)
> Please try the attached test case with steps to reproduce from comment 0. It has different behavior in Safari and in Firefox, for reasons that are not completely understood. This is what this bug is about.

Hmm, I did not realize we differ from Firefox in regards to this bug.  I wonder if Firefox is buggy then...

Anyways, I still stand by comment #15.  At the very least, I think there should be some kind of time based heuristic for when we stop applying the cache validation policy of the document to subresources.

We used to have a bug where the cache policy of the document would be sticky for XMLHttpRequest.  Facebook engineers noticed this as a huge disparity between WebKit-based browsers and other browsers when it comes to the frequency of If-Modified-Since requests because users do hit reload sometimes.  The fix was to make WebKit reset the cache policy of the document on load.  That was a good fix IMO.

I could maybe be persuaded to treat shift+reload differently, but even that seems fishy.  I hate to have to complicate the code for it.  But suppose we did.  What would the new heuristic be?  Certainly you would not want to neuter the cache forever?  Again, remember that facebook pages do not navigate the document.  They just play games with history.pushState / fragment navigations, and then they dynamically load the page with XHR.  Other pages are like that too!

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.