Bug 26681

Summary:

Problem updating applicationCache when server returns 304

Product:

WebKit

Reporter:

Kevin D. Wolf <kevinw>

Component:

WebCore Misc.

Assignee:

Alexey Proskuryakov <ap>

Status:

RESOLVED FIXED

Severity:

Normal

CC:

ap, laszlo.gombos

Priority:

Keywords:

InRadar

Version:

528+ (Nightly build)

Hardware:

OS:

Windows Server 2003

URL:

http://new.efficientcoder.net/2009/06/webkitsafari-application-cache-work.html

Attachments:

Description	Flags
proposed fix	darin: review+
improve the fix	sam: review+

Kevin D. Wolf

Reported 2009-06-24 08:36:47 PDT

1) Configure an application to use a manifest and window.applicationCache 2) Download initial cache, everythings works fine. Server returns an ETag or Last-Modified date within the header. Also has headers to disable cacheing. 3) Cache is updated, but the one or more of the resources aren't 4) WebKit requests a resource sending up If-Modified-Since and If-None-Match header headers. 5) Server returns a 304 Not Modified. 6) WebKit makes another request (goes back to step 4) this process will go on in an infinite loop. You can see a more detailed overview at: http://new.efficientcoder.net/2009/06/webkitsafari-application-cache-work.html

Attachments
proposed fix (3.75 KB, patch) 2009-06-25 07:24 PDT, Alexey Proskuryakov	darin: review+	Details Formatted Diff Diff
improve the fix (2.57 KB, patch) 2009-06-26 06:23 PDT, Alexey Proskuryakov	sam: review+	Details Formatted Diff Diff
View All Add attachment proposed patch, testcase, etc.