Lee wrote:
On 10/8/17, Paul B. Gallagher <pau...@pbgdashtranslations.com>
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.
Sure. So read the bug:
<https://bugzilla.mozilla.org/show_bug.cgi?id=1347857>
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?
I'm not having trouble.
But here are some quotes from the bug:
"Summary: blank login not displaying error → Browser: Basic
Authentication will not open auth. dialog (eventually error message
instead) under particular Email Window related conditions
...
Workaround to get over the error just close the mail window and reopen it.
...
The required fixes are now in the TB mozilla-esr52 release branch which
we will use for building 2.49.1."
^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 :)
Could be. If you sample enough people, some of them will understand a
given message differently and some won't understand it at all. That's life.
--
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
