Bug 137115
| Summary: | Web Inspector: Should show why a resource is not cached | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Martin Häcker <spamfaenger> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | graouts, inspector-bugzilla-changes, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Martin Häcker
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/18452620>