Closed
Bug 269470
Opened 20 years ago
Closed 20 years ago
Browser cache is stored in the roaming part of the user profile
Categories
(Core Graveyard :: File Handling, defect)
Tracking
(Not tracked)
People
(Reporter: ivan.jones, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Firefox by default stores its cache in the ROAMING rather than the non-roaming
part of a user profile under WinXP. i.e. "%UserProfile%\Application
Data\Mozilla\Firefox\Profiles\thtj17nl.default\Cache" rather than ""%
UserProfile%\Local Settings\Application
Data\Mozilla\Firefox\Profiles\thtj17nl.default\Cache"
There are two issues with this incorrect configuration:
1) If a Group Policy is in place to limit the profile size, then the user is
unable to log off as the profile grows beyond the administratively configured
size (maximum 30Meg)
2) Transient data such as cache data should NOT roam with an NT profile - see
the Microsoft Logo Guidlines on msdn.microsoft.com for more information.
Reproducible: Always
Steps to Reproduce:
1. Set up a roaming user profile (so that user-owned files get copied to a
server share at logout)
2. Set a profile size limit using Group Policy (the maximum size is 30Meg)
3. Browse the web until the Windows XP profile quota warning kicks in
(ProQuota.exe)
4. Try to log off
Actual Results:
Unable to log off because the roaming profile is too big
Expected Results:
It should have stored its cache in a user-owned folder that does NOT roam with
the user profile. Specifically, anywhere under %UserProfile%\Local Settings\
does not get saved back to a network share when the user logs out.
This issue effectively precludes the use of Firefox in any managed corporate
environment.
Comment 1•20 years ago
|
||
*** This bug has been marked as a duplicate of 74085 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•