Mason83 wrote:
On 28/07/2017 20:15, Bob Fleischer wrote:
I have Seamonkey V 2.48 running on 64-bit Windows 10 (v 1703). I just
upgraded from V 2.46.
A certain internal corporate web page I use no longer works, but only
when accessed from Seamonkey 2.48 on this system. On other browsers,
and from an absolutely clean v2.48 installation on a "virgin" Windows 10
(v 1703), everything works as before.
See the thread
"Problems with -sites requiring authentication"
Date: Wed, 5 Jul 2017 23:32:31 +0200
I think you've run into this bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1347857
https://bugzilla.mozilla.org/show_bug.cgi?id=1350152
The work-around, as you've found out, is restarting SM.
It seems it is something in the mail part that breaks
HTTP auth.
Regards.
That could be it, although I personally see no connection to mail.
As a test, I repeated the scenario I reported with my home system, which has
an entirely separate profile and always has.
I opened the same web site with 2.46, authenticated, and got in.
I then upgraded to 2.48, and got the same weird error message when I tried
to connect.
I then restarted 2.48 in safe mode, accessed the web site (with remembered
authentication in this case, no attempt to clear anything), and got in.
Then I restarted 2.48 normally, and access to this web site worked OK.
Bob
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
