1162163 - Choosing to clear the cache on exit shouldn't disable it altogether

Status: UNCONFIRMED

(Core :: Networking: Cache, defect, P3)

Description

[Marc Meltzer]

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; Trident/7.0; .NET CLR 2.0.50727; SLCC2; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3; rv:11.0) like Gecko

Steps to reproduce:

Default value for "privacy.clearOnShutdown.cache" is true.  Change "privacy.sanitize.sanitizeOnShutdown" from default (false) to true.

Setting both of these preferences to true disables caching.


Actual results:

I would like to revisit Bug 709262 (https://bugzilla.mozilla.org/show_bug.cgi?id=709262).

I see the issue is the cache is disabled when the preferences "privacy.clearOnShutdown.cache" and "privacy.sanitize.sanitizeOnShutdown" are both set to true.  Reading all of the comments, the logic in the "fix" is very flawed.  Why would you disable the cache just to satisfy the need to exit the browser quickly?

I know the thread started with a much earlier version of Firefox, but it apparently still affects current versions (31.5.3).

If I go into Options-Privacy and select to use custom settings for the history, and then check the "Clear history" box, I can then set what I want to clear.  What preferences do each of those checkboxes map to?

There has to be a better way to implement clearing private data.  You aren't even clearing it, you're not allowing it to be cached at all.


Expected results:

The cache should be enabled, and just the relevant data should be flushed from the cache when exiting the browser.

Comment 1

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 2

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 3

[steve james]

Awesome work thanks for sharing this with us also check https://copyenglish.com/