[Webkit-unassigned] [Bug 134681] New: [Curl] Cache entry invalidated too early.

[bugzilla-daemon at webkit.org]

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

           Summary: [Curl] Cache entry invalidated too early.
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: peavo at outlook.com


When a cache entry has expired, it is invalidated when a request for the corresponding url is started.
This is too early, since the resource is possibly not modified (even though it has expired), and the server might respond with a 304 (not modified) response.
When we then receive a 304 response, the cache entry is deleted, and we have no cached response/data to provide.
This can be solved by not invalidating the entry when a request for that url is started, but instead invalidate when a 200 OK response is received,
which means the resource has been modified (this is already implemented).

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