[Webkit-unassigned] [Bug 114517] New: Webkit reuses cache with different headers

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Apr 12 10:43:28 PDT 2013


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

           Summary: Webkit reuses cache with different headers
           Product: WebKit
           Version: 525.x (Safari 3.2)
          Platform: PC
               URL: http://br.kekanto.com/search?&c=269853&m=c&lat=-23.548
                    547000&lng=-46.638272000&q=pizza&near=S%C3%A3o+Paulo
        OS/Version: Windows 7
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: History
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: krynble at gmail.com


In order to reproduce this bug you should follow the following steps:

1) browse the following url: http://br.kekanto.com/search?&c=269853&m=c&lat=-23.548547000&lng=-46.638272000&q=pizza&near=S%C3%A3o+Paulo
It shows a list of places selling pizza in Sao Paulo.

2) Click either the star rating filter or price range (star and dolar signs respectively; NOTE: these are anchor tags <a>).
The pages reloads using AJAX and the new results are shown. I use pushState to create a new URL entry.

3) Navigate away from the page (like clicking a place name)

4) Press the back button

The expected result should be the same listing as before, but the actual result is a JSON.

Problem is: The URL pushed in the pushState is the same as Web Service used to populate the page. The browser considers it has a copy of the page and serves it, but that is a JSON. The same URL, if requested with the X-Requested-With: XMLHTTPRequest brings a JSON instead.

NOTE:
If you click a checkbox in the page it triggers the EXACT same reload function, but this does not cause the problem. Only happens only when browsing using anchor tags that change the underlying form and trigger a submit via AJAX.

-- 
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