[Webkit-unassigned] [Bug 137115] New: Web Inspector: Should show why a resource is not cached

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Sep 25 02:45:05 PDT 2014


           Summary: Web Inspector: Should show why a resource is not
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Web Inspector
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: spamfaenger at gmx.de
                CC: timothy at apple.com, joepeck at webkit.org,
                    webkit-bug-importer at group.apple.com,
                    graouts at webkit.org

See also #137113 for the reverse information why a resource is cached.

Currently it is very hard to debug why the browser does not cache specific resources using the webkit inspector.

Ideally when I look at a resource I want to see if a resource is not going to be cached and why that is the case.

Not sure where the best place for this info would be, but probably in the file inspector is a good starting place.

Currently we get info like this:

Anfrage & Antwort
Methode    GET
im Cache    Nein
Status    OK
Code    200
Codiert    41.48 KB
Decodiert    41.48 KB
√úbertragen    41.72 KB
Komprimiert    Nein

What I want is something that tells me

in Cache: NO (will not be cached because it has  a query parameter)
in Cache: No (will not be cached because specifies the Cache-Control: no-cache header)

Bonus points if it points to the RFC that specifies this behavior.

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