Bob Fleischer wrote:
Well, in case anyone else sees this issue. The problem seems to be
fixed, although I don't know why:
I restarted in "add-ons disabled" mode, connected to the problem
server, authenticated, and the page displayed properly.
I exited SeaMonkey, started SeaMonkey normally, and I was able to
access that server normally.
All I can figure is that the stored cookie or authentication for the
server was damaged in some way, but this persisted even after I
removed all records of that server in the data manager.
If your theory is that a cookie got corrupted, the easy fix would have
been to clear cookies and reattempt.
I don't usually get these types of errors because I clear private data
(including cache and cookies) frequently, and automatically on program
termination. An added benefit (or at least I tell myself that) is that
it's harder for big brother to build a complete, accurate dossier.
--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
