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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Feb 3 10:04:45 PST 2011


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





--- Comment #42 from Alexander Romanovich <alex at sirensclef.com>  2011-02-03 10:04:44 PST ---
(In reply to comment #40)
> > I'm not sure how what has been suggested exposes anything about HTTP caching to the end user. For myself, I have only requested that *developers* be able to request a resource with revalidation. As it stands, you allow anyone (end users, developers) to revalidate resources in the main document by refreshing. Why can a developer not revalidate a resource via a JS-originated request?
> 
> While I question the wisdom of such designs, there is a valid bug we have about this, see bug 51286.

It would be *great* to solve bug 51286 because it gives us a reliable way (hopefully cross-browser?) to revalidate any resource we want on the fly. But what's still missing is the ability to detect that the main resource was refreshed. We'd want to know that also, so that we can then choose to re-cache additional resources via XHR.

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



More information about the webkit-unassigned mailing list