Re: router login - error 401, unauthorized

2017-10-09 Thread rjkrjk 



Lee wrote on 10/8/17 6:47 PM:

On 10/8/17, Frank-Rainer Grahl  wrote:

Likely point 3 in the known issues in the 2.48 release notes:

https://www.seamonkey-project.org/releases/seamonkey2.48/


My understanding is that the 'steps to reproduce' requires one to have
only the email client running, open the browser from the email client
and then try to login somewhere.

So the work-around is to open the browser, from there open email/news
reader/whatever **and leave the browser window open** - correct?


leave broswer open ONLY.that worked for me.
(as well as using firefox)













Fix will be in 2.49.1.

Maybe we should just drop the release notes and tell everyone to open a
lenghty thread in one of the support groups if he7she/it runs into a known
problem :)


I would have never guessed that "you may no longer be prompted for
authentication in certain scenarios" meant getting a 401 error when
trying to login somewhere.  In my mind, not being prompted for
authentication means not getting the userid/password popup.

Lee



FRG


Jonathan Wilson wrote:

I just quit and restarted SeaMonkey and like magic the login worked if I
went
straight there and didn't open anything else (mail, ChatZilla etc)

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



---
This email has been checked for viruses by AVG.
http://www.avg.com


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

Re: router login - error 401, unauthorized

2017-10-09 Thread Mason83 
On 08/10/2017 18:44, Frank-Rainer Grahl wrote:

> Likely point 3 in the known issues in the 2.48 release notes:
> 
> https://www.seamonkey-project.org/releases/seamonkey2.48/
> 
> Fix will be in 2.49.1.
> 
> Maybe we should just drop the release notes and tell everyone to open a 
> lenghty thread in one of the support groups if he7she/it runs into a known 
> problem :)

FWIW, the problem still existed in 2.49.1 from 20170528045907
Which is expected since you FIXED the bug in August...

What does the .1 mean? When will it increase to .2?

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