245003 - SSL pages won't cache in memory of browser.cache.disk_cache_ssl is false

Status: RESOLVED EXPIRED

(Core :: Networking: HTTP, defect)

Description

[Scott Johnson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040526 Firefox/0.8.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040526 Firefox/0.8.0+

I found this today while building a credit card submission form for a client. 
At first, I thought it was my problem because I wasn't sending out proper
headers to allow for caching.  I added in Last-Modified, Cache-Control, and
Expires, but Firefox still wouldn't cache the page.  I kept seeing 200s in my
logfile when I was expecting some 304s.  I checked the page info dialog, and it
showed that the page was not cached and that the expiration date was not set. 
When I changed browser.cache.disk_cache_ssl to true, the page was cached, and
the appropriate expiration date appeared.  Shouldn't SSL pages be cached in
memory even when disk_cache_ssl is false?  It appears that when the flag is set
to false, the page is completely discarded and no If-Modified-Since header is
ever sent.

Reproducible: Always
Steps to Reproduce:
1. set browser.cache.disk_cache_ssl to false
2. visit SSL site
3. reload

Actual Results:  
no If-Modified-Since header is sent on second request.

Expected Results:  
page should have been cached in memory and browser should send If-Modified-Since
on page reloads.

Using Firefox trunk nightly.

Comment 1

[Boris Zbarsky [:bzbarsky]]

We do cache such pages in memory (at least for reload/back/forward purposes)...
Looking at the code, it should in fact be sending If-Modified-Since headers for
such content...

Is there a test page where this problem can be reproduced?

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.