Summary: | Safari does not cache-validate certain resources | ||
---|---|---|---|
Product: | WebKit | Reporter: | Sridhar Gurivireddy <just1gb> |
Component: | WebKit Misc. | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | ap, bfulgham |
Priority: | P2 | Keywords: | InRadar |
Version: | 528+ (Nightly build) | ||
Hardware: | PC | ||
OS: | Windows XP | ||
URL: | http://finance.yahoo.com |
Description
Sridhar Gurivireddy
2008-01-16 09:27:43 PST
The title says "hitting back" - I do not see this in steps to reproduce. Could you please clarify which is correct? It happens both when navigating back and launching a new instance of safari. I don't know what's happening here and whether this is a bug, but this is probably decided upon by Apple frameworks beneath WebKit. $ curl -I http://l.yimg.com/us.js.yimg.com/lib/bc/bc_2.0.4.js HTTP/1.1 200 OK Date: Thu, 17 Jan 2008 22:27:17 GMT Cache-Control: max-age=315360000 Expires: Sun, 14 Jan 2018 22:27:17 GMT Last-Modified: Wed, 17 Jan 2007 23:44:19 GMT Accept-Ranges: bytes Content-Length: 2040 Content-Type: application/x-javascript Age: 31461 Connection: keep-alive Server: YTS/1.16.0 Why does IE revalidate? Is it a bug in IE? The response says: Cache-Control: max-age=315360000 That says it should not be revalidated until it's 10 years old! Closing old report. |