Re: SM 2.24 browser multi-tab session restore failure

2014-03-08 Thread User

Paul B. Gallagher wrote, On 2014.03.07 22:12:

User wrote:


Summary - SM 2.24 browser does not always save a full snapshot of a
browser tab and this results in some web sites having to be re-logged
in again after session restore.

...

I have checked my CLEAR PRIVATE DATA settings in PREFERENCES, I
previously had it set to auto clear private data but the only data I
selected to clear was browser cache contents, which did not affect
the older version SM 2.21 in always being able to fully restore all
browser tabs without having to log in. But in SM 2.24, even though I
have the CLEAR PRIVATE DATA disabled, this problem is not resolved
and I believe the problem has to do with how SM 2.24 saves browser
tab contents that is causing certain tabs with log in data to be lost
in the session save.


One possibility -- which only you can check -- is that the cookies in question
expired in the interim. Not all cookies are designed to last until 2039. So if
you restored after their expiration date, the expired cookies would be rejected
by the server and it would ask you to login again.

Also worth looking at your cookie defaults and site-specific permissions -- if
you're only accepting session cookies, they should not survive a program
termination (by definition), even if you don't have SM set to clear cookies on
termination.

There may be other possibilities I haven't thought of. Keep reading.


Your points are valid. However, the session restore usually happens within less 
than 15 SECONDS of shutting down the SM application. The most I usually leave it 
is maybe 10 to 15 minutes at best. So expiry isn't the cause. I also haven't 
changed any cookie permission settings since upgrading from SM 2.21 to 2.23. It 
just suddenly stopped working for some sites that needed the log in information 
to be retained, whatever that might be. I've selected the option to accept all 
cookies and accept them all normally. I think I'll try to clear all cookies for 
specific sites that are having problems and then see how it fairs.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: SM 2.24 browser multi-tab session restore failure

2014-03-07 Thread Paul B. Gallagher

User wrote:


Summary - SM 2.24 browser does not always save a full snapshot of a
browser tab and this results in some web sites having to be re-logged
in again after session restore.

...

I have checked my CLEAR PRIVATE DATA settings in PREFERENCES, I
previously had it set to auto clear private data but the only data I
selected to clear was browser cache contents, which did not affect
the older version SM 2.21 in always being able to fully restore all
browser tabs without having to log in. But in SM 2.24, even though I
have the CLEAR PRIVATE DATA disabled, this problem is not resolved
and I believe the problem has to do with how SM 2.24 saves browser
tab contents that is causing certain tabs with log in data to be lost
in the session save.


One possibility -- which only you can check -- is that the cookies in 
question expired in the interim. Not all cookies are designed to last 
until 2039. So if you restored after their expiration date, the expired 
cookies would be rejected by the server and it would ask you to login again.


Also worth looking at your cookie defaults and site-specific permissions 
-- if you're only accepting session cookies, they should not survive a 
program termination (by definition), even if you don't have SM set to 
clear cookies on termination.


There may be other possibilities I haven't thought of. Keep reading.

--
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