[Webkit-unassigned] [Bug 77538] 302 redirect for <script> src with cached location caches the redirect

[bugzilla-daemon at webkit.org]

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





--- Comment #2 from Nate Chapin <japhet at chromium.org>  2012-07-02 15:54:58 PST ---
(In reply to comment #1)
> This is likely caused by the MemoryCache not understand cache headers properly for redirects.

That's right. CachedResource::m_response will only hold the last ResourceResponse in the redirect chain. Even better, CachedResource::m_request will only hold the ResourceRequest at the start of the redirect chain, so if in the future we request the destination script directly, the cache will miss.

First crazy idea to pop into my head:
Maybe on successful completion of a resource load that redirected, we should prime the cache with a new entry that has the final ResourceRequest and ResourceResponse (and therefore the final url), and if there were any cache control headers, aggressively evict the original CachedResource.

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