Closed
Bug 189170
Opened 22 years ago
Closed 22 years ago
Mozilla does not prompt the login alert box dealin a 401-2 server alert instead of a 401-1
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
People
(Reporter: le.iota, Assigned: darin.moz)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030114
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030114
when the server is asking for authentification, Mozilla does not acknowledge it
and it deals directly a 401-2 error
Reproducible: Always
Steps to Reproduce:
1. load http://www.viewline.net/
2.
3.
Actual Results:
the server replies 401-2 error and Mozilla doesn't promprt authentification box
Expected Results:
ack to the server the authentification request and prompt the authentification box.
-> i mark this as DUPEME. mark it as blocking bug 12578 bug 57529 Bug 134103
and bug 140645 sorry for the spam
Reporter | ||
Comment 1•22 years ago
|
||
-> i submit a new bug. mark it as DUPEME. mark it as blocking bug 12578 and bug
57529 Bug 134103 and of course bug 61681 sorry for the spam
Comment 3•22 years ago
|
||
HTTP/1.1 401 Acc.s refus...Server: Microsoft-IIS/5.0..Date: Wed, 15 Ja
n 2003 15:34:35 GMT..WWW-Authenticate: Negotiate..WWW-Authenticate: NT
LM..Connection: close
and what Do you mean with DUPME ?
If you know that a bug is a dupe, DON'T REPORT IT.
You will loose your Account if you do that again !
And don't add bug to the depency list if they are unrelated. This generated
useless SPAM.
Thanks
*** This bug has been marked as a duplicate of 23679 ***
Comment 4•22 years ago
|
||
1. The problem with that site is that it uses NTLM authentication. This bug has been duped to a bug about implementing that.2. You write:> -> i mark this as DUPEMEWhy? *Before* filing a bug, watch out if it hasn't already been reported. There's no point in filing a DUPEME bug.> . mark it as blocking bug 12578That has *what* to do with NTLM authentication?> sorry for the spamYeah, indeed. This bug is useless.Verifying duplicate.
Status: RESOLVED → VERIFIED
Comment 5•22 years ago
|
||
I'm the culprit for the typo on "DUPME", I meant "DUPEME" and forgot to remove
it when I added comment 2.
Comment 6•22 years ago
|
||
Sorry for the lack of line breaks earlier. Blame it on Safari.Olivier, "DUPEME" doesn't make sense when a bug has just been filed.
Whiteboard: DUPEME
Comment 7•22 years ago
|
||
Soren ? It makes sense, it means someone is trying to find the proper dupe and
tell other triagers "don't lose your time on this bug report, someone is taking
care of it".
Once I found the dupe, I mentioned it and forgot to remove "DUPEME".
I knew it was a dupe from the original report (I'm not the reporter) as this is
very common.
If DUPEME is used in another way, please let me know.
Comment 8•22 years ago
|
||
I'd say "DUPEME" means "someone find a dupe, I know / am 99% sure there is one
but can't find it".
In this case, the original reporter added that status whiteboard keyword, which
makes it rather pointless (if you know a bug is a dupe when filing it, don't
file it in the first place; try and find the other bug and eventually ask for
help from others).
I thought *you* added the "DUPEME", so my previous comment is wrong anyway.
Comment 9•22 years ago
|
||
"dupme" means : I'm sure that this bug is a dupe but I can't find it or i don't
have time. Only triagers should add such a line.
The reporter should not add such a line because that means that his bug report
is invalid.
You need to log in
before you can comment on or make changes to this bug.
Description
•