[Webkit-unassigned] [Bug 70209] New: Hard Refresh Bug. Before a new document loader is created for reload, the cache policy of initial request should set to ReloadIgnoringCacheData.
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sun Oct 16 18:47:31 PDT 2011
https://bugs.webkit.org/show_bug.cgi?id=70209
Summary: Hard Refresh Bug. Before a new document loader is
created for reload, the cache policy of initial
request should set to ReloadIgnoringCacheData.
Product: WebKit
Version: 528+ (Nightly build)
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Page Loading
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: ssungmai.kim at samsung.com
Hard refresh (No cache data use) is not working at first try, but working correctly after second try.
This is because the cache policy is copied from the previous document loader's policy, which is UseProtocalCachePolicy.
Even though the cache policy is set to ReloadIgnoringCacheData after document loader creation by setCachePolicy() on FrameLoader::reload(), the cache policy of m_originalRequest is still UseProtocolCachePolicy.
The cache policy of Subresource's request is set to 'documentLoader()->originalRequest().cachePolicy()' on FrameLoader::addExtraFieldsToRequest() function.
So it would be UseProtocolCachePolicy at first try, then the HTTPHeaderFields of "Cache-Control : no-cache" and "Pragma : no-cache" could not be added to
the Subresource's request. The Cache policy of Subresource's request must be ReloadIgnoringCacheData to be set with no-cache header fields.
This bug is caused by wrong position where the cache policy is set to ReloadIgnoringCacheData, we fixed it.
--
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