241579 - Exclude cache directory from Windows roaming profile

Status: RESOLVED DUPLICATE of bug 74085

(Core Graveyard :: Profile: BackEnd, defect)

Description

[Chris Thomas (CTho) [formerly [e-mail] [e-mail]]]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040420
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040420

When using roaming profiles, having the browser's cache in the Application Data
can significantly increase the size of the user's profile.  An alternative might
be to store the cache in the Local Settings directory somewhere, but based on
discussions in #mozilla that probably isn't a very good idea.

How to not upload certain directories when using roaming profiles:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;188692

Possibly relevant:
http://support.microsoft.com/default.aspx?scid=kb;en-us;185255

Reproducible: Always
Steps to Reproduce:

Comment 1

[Nicholas Allen]

*** This bug has been marked as a duplicate of 74085 ***

Comment 2

[[e-mail]]

This bug is *not* about moving the cache folder.

Comment 3

[Benjamin Smedberg]

This bug is windows-specific and is about using the windows registry to prevent
windows from uploading the cache data to a roaming profile.

Comment 4

[Nicholas Allen]

Ok, then it should probably be WONTFIXed then.  Using the registry to exclude
directories from roaming is broken.  CSIDL_LOCAL_APPDATA is supposed to be used
for non-roaming data.

Comment 5

[Nicholas Allen]

From an email exchange with Chris- "Why is it broken?"

The registry setting that's being talked about in the bug was basically a quick
fix for IE on NT4.  It suffers from problems like this:

http://support.microsoft.com/default.aspx?scid=kb;en-us;290736

and it doesn't always work when the client machine is running an older version
of Windows.  Instead of fixing all the problems, a different workaround was made
for IE and LOCAL_APPDATA was created with Shell version 5.

I was being inflammatory (and apologize for that) by calling it outright broken
but it's probably not the right way to go.

Comment 6

[David :Bienvenu]

this is for windows profile roaming, not just mozilla profile roaming, right?

Comment 7

[benc]

Yes. And I don't understand why it was reopened.

Comment 8

[Henrik Gemal]

this has nothing to do with Mozilla Roaming.

*** This bug has been marked as a duplicate of 74085 ***