Re: might some change in 2.48 break some web servers?
Frank-Rainer Grahl wrote: This bug usually hits you only if you don't start the browser first or close the last browser Windows when Mail is still open. Always in TB because it has no browser. It should not happen if you start the browser normally first. Check the error console if you see some error messages pointing to authentication or add-ons. The mozilla devs really take their time to review this one despite me and jorgk giving positive feedback. We might have to put it in a branch for 2.49.1: https://bugzilla.mozilla.org/show_bug.cgi?id=1350152 Well beggars can't be choosers and Firefox is not affected so this takes the usual backseat... FRG Bob Fleischer wrote: 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 I can confirm that, if I open the browser first, I do not have this problem. Bob ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: might some change in 2.48 break some web servers?
This bug usually hits you only if you don't start the browser first or close the last browser Windows when Mail is still open. Always in TB because it has no browser. It should not happen if you start the browser normally first. Check the error console if you see some error messages pointing to authentication or add-ons. The mozilla devs really take their time to review this one despite me and jorgk giving positive feedback. We might have to put it in a branch for 2.49.1: https://bugzilla.mozilla.org/show_bug.cgi?id=1350152 Well beggars can't be choosers and Firefox is not affected so this takes the usual backseat... FRG Bob Fleischer wrote: 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 support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: might some change in 2.48 break some web servers?
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 support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: might some change in 2.48 break some web servers?
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
Re: might some change in 2.48 break some web servers?
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
Re: might some change in 2.48 break some web servers?
Bob Fleischer wrote: Lee wrote: On 7/28/17, 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. Which means it's not a problem with v2.48 in general, but a problem with your particular install on that machine. Have you tried running Seamonkey in safe mode? with a new profile? with no addons? Regards, Lee The error page I get seems to come from the server and seems to blame the server: You are not authorized to view this page You do not have permission to view this directory or page using the credentials you supplied. Please try the following: Click the Refresh button to try again with different credentials. If you believe you should be able to view this directory or page, please contact the Web site administrator by using the e-mail address or phone number listed on the partners.duxburysystems.com home page. HTTP 401.2 - Unauthorized: Logon failed due to server configuration Internet Information Services Technical Information (for support personnel) Background: This is usually caused by a server-side script not sending the proper WWW-Authenticate header field. Using Active Server Pages scripting this is done by using the AddHeader method of the Response object to request that the client use a certain authentication method to access the resource. More information: Microsoft Support Note that I am not prompted for a login. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey Well, of course it's a problem with my particular install (or profile) on that machine, but it was a profile that worked correctly in 2.46 (I use that server every day). It could mean that a valid but non-default setting in 2.46 either migrated incorrectly to 2.48 or is implemented incorrectly (or at least differently) in 2.48. How do I go about diagnosing that? (In case it makes a difference, this web server is a very old version--Windows 2000. This web site require authentication but is non-secure--straight http.) Bob 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. Bob ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: might some change in 2.48 break some web servers?
Lee wrote: On 7/28/17, 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. Which means it's not a problem with v2.48 in general, but a problem with your particular install on that machine. Have you tried running Seamonkey in safe mode? with a new profile? with no addons? Regards, Lee The error page I get seems to come from the server and seems to blame the server: You are not authorized to view this page You do not have permission to view this directory or page using the credentials you supplied. Please try the following: Click the Refresh button to try again with different credentials. If you believe you should be able to view this directory or page, please contact the Web site administrator by using the e-mail address or phone number listed on the partners.duxburysystems.com home page. HTTP 401.2 - Unauthorized: Logon failed due to server configuration Internet Information Services Technical Information (for support personnel) Background: This is usually caused by a server-side script not sending the proper WWW-Authenticate header field. Using Active Server Pages scripting this is done by using the AddHeader method of the Response object to request that the client use a certain authentication method to access the resource. More information: Microsoft Support Note that I am not prompted for a login. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey Well, of course it's a problem with my particular install (or profile) on that machine, but it was a profile that worked correctly in 2.46 (I use that server every day). It could mean that a valid but non-default setting in 2.46 either migrated incorrectly to 2.48 or is implemented incorrectly (or at least differently) in 2.48. How do I go about diagnosing that? (In case it makes a difference, this web server is a very old version--Windows 2000. This web site require authentication but is non-secure--straight http.) Bob ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: might some change in 2.48 break some web servers?
On 7/28/17, 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. Which means it's not a problem with v2.48 in general, but a problem with your particular install on that machine. Have you tried running Seamonkey in safe mode? with a new profile? with no addons? Regards, Lee > The error page I get seems to come from the server and seems to blame > the server: > >> >> You are not authorized to view this page >> You do not have permission to view this directory or page using the >> credentials you supplied. >> >> Please try the following: >> >> Click the Refresh button to try again with different credentials. >> If you believe you should be able to view this directory or page, >> please contact the Web site administrator by using the e-mail address or >> phone number listed on the partners.duxburysystems.com home page. >> >> HTTP 401.2 - Unauthorized: Logon failed due to server configuration >> Internet Information Services >> >> Technical Information (for support personnel) >> >> Background: >> This is usually caused by a server-side script not sending the proper >> WWW-Authenticate header field. Using Active Server Pages scripting this is >> done by using the AddHeader method of the Response object to request that >> the client use a certain authentication method to access the resource. >> >> More information: >> Microsoft Support >> > > Note that I am not prompted for a login. > > ___ > support-seamonkey mailing list > support-seamonkey@lists.mozilla.org > https://lists.mozilla.org/listinfo/support-seamonkey > ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
might some change in 2.48 break some web servers?
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. The error page I get seems to come from the server and seems to blame the server: You are not authorized to view this page You do not have permission to view this directory or page using the credentials you supplied. Please try the following: Click the Refresh button to try again with different credentials. If you believe you should be able to view this directory or page, please contact the Web site administrator by using the e-mail address or phone number listed on the partners.duxburysystems.com home page. HTTP 401.2 - Unauthorized: Logon failed due to server configuration Internet Information Services Technical Information (for support personnel) Background: This is usually caused by a server-side script not sending the proper WWW-Authenticate header field. Using Active Server Pages scripting this is done by using the AddHeader method of the Response object to request that the client use a certain authentication method to access the resource. More information: Microsoft Support Note that I am not prompted for a login. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
