Closed
Bug 52770
Opened 24 years ago
Closed 24 years ago
Unable to access secure IIS web site
Categories
(Core :: Networking: HTTP, defect, P3)
Tracking
()
People
(Reporter: conorlennon, Assigned: gagan)
Details
This is similar to Bug 44041. In Bug 44041 the http header was HTTP/1.1 401 Access Denied WWW-Authenticate: NTLM WWW-Authenticate: Basic realm="131.202.33.81" Content-Length: 644 Content-Type: text/html The resolution to this bug was to handle multplie 'WWW-Authenticate' fields by using the first one that could be used. This has been fixed, and I can access the sites listed in this bug. However, we have some internal secure IIS web sites here, and I still can't access them. (tried in build 2000091408) The http header from them is HTTP/1.1 401 Access Denied WWW-Authenticate: NTLM Content-Length: 835 Content-Type: text/html Note: only one 'WWW-Authenticate' field. Mozilla Build 2000091408 does nothing when I try to access one of these sites. I would expect that I would get prompted for a user name and password. Is NTLM a valid value for this field? Netscape 4 recognises this value, and prompts me for a user name and password.
Reporter | ||
Comment 1•24 years ago
|
||
Changing component to Networking, as I was incorrect in assigning this as DOM 0.
Component: DOM Level 0 → Networking
NTLM not supported as yet. *** This bug has been marked as a duplicate of 23679 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Updated•24 years ago
|
Status: RESOLVED → VERIFIED
Comment 4•24 years ago
|
||
Verified dupe.
You need to log in
before you can comment on or make changes to this bug.
Description
•