[Webkit-unassigned] [Bug 114738] New: 304s broken for main resources

[bugzilla-daemon at webkit.org]

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

           Summary: 304s broken for main resources
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
               URL: http://www.sirensclef.com/webkit/304/example.php
        OS/Version: Unspecified
            Status: UNCONFIRMED
          Severity: Major
          Priority: P2
         Component: Page Loading
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: alex at sirensclef.com


A great deal of work was done recently by Nate Chapin on the caching of main resources in memory cache. Ideally this would lead to Safari finally supporting 304 responses on main resource loads, but that's still not the case. I believe this is a bug in the current implementation.

Here is an example PHP script that sends a few headers to demonstrate the issue: http://www.sirensclef.com/webkit/304/example.php
304s are supported in Chrome and FF on that page.

Interestingly, I found this page in bugzilla which partially works: http://renevier.net/misc/webkit_109225.php
I get a 200 the first time, and each subsequent refresh. However, if I manually press enter from WebKit nightly's URL field, it gives a 304 and then continues to give a 304 on each refresh.

Lastly, here is a plain HTML page that gets 200 in Safari, but 304 in Chrome/FF: http://www.sirensclef.com/webkit/304/index.html

Can this please be fixed now? After the recent work that was done, I would think this is a great opportunity to finally deliver some basic functionality that Safari users & developers have been waiting years for.

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