Bug 137115 - Web Inspector: Should show why a resource is not cached
Summary: Web Inspector: Should show why a resource is not cached
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2014-09-25 02:45 PDT by Martin Häcker
Modified: 2016-12-13 15:32 PST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Häcker 2014-09-25 02:45:05 PDT
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.
Comment 1 Radar WebKit Bug Importer 2014-09-25 02:45:32 PDT
<rdar://problem/18452620>