196948 - Should not follow the sysmlink named Cache.Trash, just delete it

Status: RESOLVED WONTFIX

(Core :: Networking: Cache, defect)

Description

[Michiel van Leeuwen (email: mvl+moz@)]

1. Create a sysmlink ~/profile/<name>/<salt>/Cache.Trash to some dir (~/temp/a)
2. Create some files in that dir (~/temp/a/file)
3. Start mozilla
4. Visit a page
5. Look in the dir (~/temp/a)

File created there is gone. It should just have deleted the symlink.
Not always reproducable it seems.

Maybe this is related to bug 196525?

Comment 1

[gordon]

Why would a user create Cache.Trash as a symlink?  And if they did go to the
trouble to do that, why should we not let them?

I'm going to mark this WONTFIX, but I'm open to further discussion on the
matter.  I could be convince otherwise.

Comment 2

[Michiel van Leeuwen (email: mvl+moz@)]

When deleting directory's, mozilla should not follow symlinks. But it does.
Another observation is that putting a symlink in the Cache directory with the
name of a cache entry follows the symlink, and deletes everything in the dir it
points to. This, on itself,is a very strange situation ofcourse, but cache
entries should not be deleted recursivly, but just delete the file itself (or
symlink in this case).
My idea was that somehow, in strange way, a symlink has ended up in the Cache
dir of the reporter of bug 196525. But i tried hard to archieve that, and I
couldnt do it (on win2k)

So I don't think this is really serious. Maybe it is more file-handling then, it
deletes symlinks not like it should. The Cache.Trash dir is indeed not a problem.