There's no caching information available in the monitor




Developer Tools: Netmonitor
4 years ago
7 months ago


(Reporter: vporof, Unassigned, Mentored)


(Blocks: 1 bug, {dev-doc-needed})

Firefox Tracking Flags

(Not tracked)



(1 attachment)



4 years ago
Cached requests (304) should be marked out differently in the requests menu, and more detailed caching information should be shown somewhere in the details pane. For example, firebug shows something like this:

Data Size       20035
Device          disk
Expires         Sat Apr 05 2014 19:44:49 GMT+0300 (EEST)
Fetch Count     4
Last Fetched    Sun Apr 07 2013 12:45:31 GMT+0300 (EEST)
Last Modified   Sun Apr 07 2013 12:45:31 GMT+0300 (EEST)

Comment 1

4 years ago
Moving into Developer Tools: Netmonitor component. Filter on NETMONITORAMA.
Component: Developer Tools → Developer Tools: Netmonitor
Summary: [netmonitor] There's no caching information available in the monitor → There's no caching information available in the monitor


4 years ago
Priority: -- → P3
FWIW, Firebug showed this informatino within the 'Cache' tab of an expanded request.

Blocks: 991806
Keywords: dev-doc-needed
Created attachment 8831086 [details]

Firebug's Net panel (cache tab) screenshot.

Here is how Firebug fetches cache data from the platform:

Keywords: good-first-bug
Some instructions for the implementation:

1) There should be a new panel "Cache" implemented alongside other panels like, Headers, Params, etc.

2) Here is implementation of existing panels. Implementation of the new Cache panel will be very similar

3) The new Cache panel should also utilize `PropertiesView` just like other panels. It should simplify the work.

4) The Cache panel doesn't probably need filter input box so, the `enableInput` property (for the PropertiesView component) should be set to false.

5) The cache data should be fetched from the platform using CacheStorageService (introduced in Firefox 32). See Firebug's implementation as an example:

6) Fetching the data should happen on the backend. See e.g. how response content is fetched: Back compatibility should be preserved so, client should be able to work with backend that doesn't support this new feature (ie fetching cache data)

Here is how the Client fetches the response content


Btw. Since the backend implementation is involved in this bug, I am removing good-first-bug flag. The patch doesn't have to be so simple.

Keywords: good-first-bug
You need to log in before you can comment on or make changes to this bug.