E.g. 1) was the server not contacted at all due to cached file having expires-header with a future date. 2) was the server contacted, but the cached-version was up to date (304 not modified) 3) was it downloaded from the server. Plus: display the uncompressed size if the server used a compressed content-encoding. Plus: display the server http response code and the message.
(In reply to comment #0) > Plus: display the server http response code and the message. I believe this is currently available if you click on each request bar.
(In reply to comment #1) > > Plus: display the server http response code and the message. > > I believe this is currently available if you click on each request bar. It is only the headers but not the status line, i.e. the first line in: HTTP/1.0 200 OK Date: Thu, 21 Jun 2007 17:13:16 GMT Server: VitalityServer/2.0 Content-type: text/html; charset=ISO-8859-1 Content-length: 601
I think this may be tricky to do as the underlying HTTP stack that WebKit uses (Foundation on Mac, CoreFoundation on Windows) simply hands us back the cached response rather than the "real" response from the server when the request is fulfilled from the cache.
<rdar://problem/5712799>
Created attachment 24501 [details] Proposed patch to visually distinguish cached loads
Comment on attachment 24501 [details] Proposed patch to visually distinguish cached loads r=me
Created attachment 24502 [details] Screenshot of cached loads
Landed part of this in r37709.
Comment on attachment 24501 [details] Proposed patch to visually distinguish cached loads Clearing the review flag since I plan to do more work for this bug.
What else would need to be done to get this bug closed? We now show the HTTP status code and the message as well.
Not sure… hmm.