Net Panel-Asserts request from cache problem

[simp...@126.com]

Hello.I'm using Firefox 4.0.1 and using firebug 1.7.3 to monitor js/css/img/etc download from my server.

However, I can't figure out whether the browser is download these assets from server or from browser cache.

First,all the request status code is 200 and there is time spent in the waterfall chart.So I think the assets is download from server.

But at the bottom of firebug, there is a text saving that there is 825.2KB from cache(In Chinese).

Can anyone help me figure out whether is from cache or from server?

Thx very much.

[Sebastian Zartner]

Hello.I'm using Firefox 4.0.1 and using firebug 1.7.3 to monitor js/css/img/etc download from my server.

This configuration is completely outdated. The current versions are Firefox 24.0 and Firebug 1.12.3. So you should really update your system.
 

First,all the request status code is 200 and there is time spent in the waterfall chart.So I think the assets is download from server.

But at the bottom of firebug, there is a text saving that there is 825.2KB from cache(In Chinese).

Requests shown in gray are read from cache. In your case this is half of all requests. Also note that there are two different kinds of caches in Firefox, the normal browser cache (with HTTP status code 304) and one called Back-Forward Cache (or BFCache).
You can see more details about this in the Net panel description in our wiki.

Sebastian

[simp...@126.com]

Thx a lot.

I used Firefox 24 and the BFCache or normal cache is easy to figure out.

But this system is built on that old version of Firefox and depend on some constraints(just like IE6 in China).I can't update that system.

However,if those grey request is from cache,the 160+ms grey column is also the time spent in execute js/css/dom, not just the gap?

在 2013年10月17日星期四UTC+8下午7时51分50秒，Sebastian Zartner写道：

[Sebastian Zartner]

But this system is built on that old version of Firefox and depend on some constraints(just like IE6 in China).I can't update that system.

Well, then try to push your bosses to update the systems. As I said FF 4.0.1 is outdated and not maintained anymore, so there are a lot of bugs and security holes in it. Same for IE 6, which even Microsoft wants to get rid of. Only China still stays with IE6.
Anyway, that's another story.
 

However,if those grey request is from cache,the 160+ms grey column is also the time spent in execute js/css/dom, not just the gap?

No, this time is spent fetching it from cache. You can hover the timeline of each request to get more detailed info on which part of the request the time is spent. Regarding the screenshot I'd say most time is spent on "Waiting".

Sebastian

[simp...@126.com]

No, this time is spent fetching it from cache. You can hover the timeline of each request to get more detailed info on which part of the request the time is spent. Regarding the screenshot I'd say most time is spent on "Waiting".

This old version of Firefox spent so much time fetching multi js file from cache.It's so terrible.

Thank you very much

[Sebastian Zartner]

Another reason to update to the current version of Firefox. :-)

Sebastian