Bug 24159 - Cache-control: public headers don't cache in the browser between sessions
Summary: Cache-control: public headers don't cache in the browser between sessions
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac OS X 10.5
: P3 Normal
Assignee: Nobody
URL: https://rallyperf.rallydev.com/slm/
Keywords: InRadar
: 24176 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-02-25 08:58 PST by Tarun Reddy
Modified: 2009-02-25 16:19 PST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tarun Reddy 2009-02-25 08:58:50 PST 
When a computer sends "Cache-control: public" for SSL site, the browser should cache content on disk for those requests. This is how Firefox 3.0+, Chrome and IE 6+ behave.

To reproduce, 
1.) Go to a website that show gives Cache-control: public for content on an SSL site. The example site https://rallyperf.rallydev.com/slm/ has this on the login page.
2.) Quit browser
3.) Open same page again. Firefox 3.0+, Chrome and IE 6+ all do not reload that static content. Safari 3.2+, Safari 4.0 beta, and WebKit all reload content. This makes the site significantly slower over low latency connections.

See following URLs for more info:
http://blog.httpwatch.com/2009/01/15/https-performance-tuning/   (Tip #4)
http://blog.pluron.com/2008/07/why-you-should.html
Comment 1 Mark Rowe (bdash) 2009-02-25 12:58:49 PST 
Disk caching is handled by the system CFNetwork framework, not by WebKit.
Comment 2 Mark Rowe (bdash) 2009-02-25 12:59:28 PST 
<rdar://problem/6622697>
Comment 3 Mark Rowe (bdash) 2009-02-25 12:59:55 PST 
Closing as INVALID is this is not a WebKit issue.
Comment 4 Tarun Reddy 2009-02-25 16:19:45 PST 
*** Bug 24176 has been marked as a duplicate of this bug. ***