HTTP Downloads and Caching
Cameron Braid
using it since 0.4 and it is an invaluable tool.
In the console and net view, when a URL is downloaded with status '304
not modified' there is no indication that this is the case. This
makes it hard to determine if the url is cached. The status could
show up the same way a 404 error is reported - change the color of the
url and have the status in brackets. This could probably apply to all
urls that don't result in status=200.
It also appears that firebug isn't reporting on the browser cache the
same way as other extensions.. Now, this may not be a bug with
firebug, but the two other extensions that I have been using seem
consistent.
I have looked at the headers from the "Live HTTP Headers" extension
and the "Tamper Data" extension, and they both report that the urls in
question havn't been downloaded.
For example, I do a shift-refresh, and see my 92k javascript resource
in both "Tamper Data" and "Live HTTP Headers" as being downloaded. It
also also shows up in firebug, this is good. Then I do a normal url
get (Alt-D Enter) and "Tamper Data" shows it as staus=pending, which
means the browser hasn't even requested the url from the server.
"Live HTTP Headers" doesn't show anything at all for it, indicating
the same. Firebug shows it as in the Net tab as being downloaded and
taking 2 seconds.
Cheers,
Cameron
robertivanc
that this is what is happening.
It's quite deceiving as it looks that firefox keeps requesting these
files where in fact it just loads them from the cache.
Robert
Adam
fired, but not the on-examine-response hook.
This happens because examination of the cache, and previous response
headers happens after the first hook is called. This is also why you
can't tamper with the cache control headers.
LiveHTTPHeaders doesn't show the requests at all, because that
extension (which tamperdata was partially based on) only monitors the
on-examine-response hook.
Adam