On 10/8/17, Paul B. Gallagher <[email protected]> wrote: > Lee wrote: > >> 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. > > Keep reading.
"The problem is tracked in bug 1347857. Check the bug for workarounds. The issue will be fixed in the next SeaMonkey release." and that's it for the item in the release notes. > The bug goes on to say that the failure to prompt > eventually leads to an error message. Presumably because failure to > prompt leads to failure to authenticate (you can't answer a question it > doesn't ask), so when the unauthorized user tries to execute commands, > they are rejected. I followed the directions to duplicate the bug & never saw a failure to prompt. Have you seen something different? If you haven't, try it yourself: - open seamonkey browser - click on window / mail & newsgroups - close the browser window - from the mail & newsgroups window click on window / browser - goto https://auth-demo.aerobatic.io/ - click on tools / web development / toggle tools - click on the network tab (so you can see the status code returned) - click on the standard auth button - get the userid/password popup - give it aerobatic/aerobatic as the userid / password - see the 401 error returned ^shrug^ but I'd bet even if the release notes had said something about a 401 error when trying to authenticate we'd have still had this conversation :) Regards, Lee _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
