Closed
Bug 210882
Opened 22 years ago
Closed 22 years ago
SQUID Proxy with NTLM authentication does not work
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: maxim, Assigned: darin.moz)
Details
(Whiteboard: [ntlm])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla 1.4 b, rc1, rc2, rc3
We have corporate proxy SQUID 2.5.2 and it works with Basic authentication just
fine with 1.3 and 1.4 (b,rc1,rc2,rc3) Then our administrator has added NTLM
authentication for SQUID. 1.3 continues to work (as I write using it:) with
plain authentication but 1.4 fails to go through the proxy, always User/Password
dialog with empty fields appears. The only way to exit is to select Cancel action.
Note, NTLM with Mozilla 1.4b+ works with IIS sites in intranet.
On the other hand, IE goes through the proxy without this problem.
Reproducible: Always
Steps to Reproduce:
1. Goto any site.
2. User/password dialog box appear with blank user and password
3. Enter valid user and password
Actual Results:
1. User/password dialog box appear with blank user and password again
Expected Results:
Surf the internet or use basic authorization
I've heard that NTLM for SQUID authentication is actually LM authentication
Comment 1•22 years ago
|
||
doesn't block mozilla-development (that's what the blocker-flag is for)
Severity: blocker → critical
Comment 2•22 years ago
|
||
doesn't crash either.
Do you enter your username/password with the domain first (DOMAIN\user) ?
Can you attach a HTTP log ? See instructions here:
http://mozilla.org/projects/netlib/http/http-debugging.html
Severity: critical → major
Whiteboard: [ntlm]
Reporter | ||
Comment 3•22 years ago
|
||
With specifying domain in the user it works! Thank you very much!
I wonder why the short user name (without DOMAIN) appears to be enough within
intranet IIS server though.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
VERIFIED/WFM:
IIS server configs that I have seen allow the server to assume a domain for
users that provide only their username.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•