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. _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
