David E. Ross wrote:
On 8/16/13 9:59 PM, Paul B. Gallagher wrote:
David E. Ross wrote:
I believe cookies are written to cookies.sqlite when SeaMonkey
terminates. This happens well after I have visited the Web sites
that sent the cookies. Thus, the sites act as if they have indeed
set persistent cookies when, actually, they have set only session
cookies.
This theory is easily tested.
1) With SeaMonkey closed, copy cookies.sqlite to a safe place from which
you can restore it after the test.
2) Make the original cookies.sqlite in your SeaMonkey profile (not the
archive copy) writable.
3) Launch SeaMonkey and browse to one or more sites that you expect to
set cookies. Confirm with Cookie Manager that they have done so. Do not
terminate SeaMonkey.
4) In Windows Explorer, look at the date/time stamp of the active
cookies.sqlite file in your SeaMonkey profile and see if it has changed.
If it has, you're wrong.
5) Terminate SeaMonkey and check the date/time stamp of the active
cookies.sqlite file in your SeaMonkey profile and see if it has changed.
If it has now, but not before, you're right.
6) Restore your archived, read-only copy of cookies.sqlite to your
SeaMonkey profile. Make sure it's read-only.
Hmm. The time stamp did change at step #4 and again at step #5.
However, Web sites that want to set persistant cookies do not object
when cookies.sqlite is set read-only. They apparently do not recognize
the failure to write their cookies onto disc.
Interesting that your results are different from mine.
In my case, the files cookies.sqlite-shm and cookies.sqlite-wal did
update while SeaMonkey was open, but cookies.sqlite itself did not until
I terminated the program.
--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
