Closed
Bug 316438
Opened 19 years ago
Closed 19 years ago
does not prompt for username/password when trying to access password protected content
Categories
(Toolkit Graveyard :: XULRunner, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: ryan, Unassigned)
Details
Attachments
(1 file)
1.44 KB,
application/zip
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 I have an iframe with it's src pointing to a URL that is password protected. XulRunner does not prompt for a user/pass like firefox, it just renders a 402.1 forbidden from my server, as if you had requested and it had failed to authenticate. If I put the username and password inside the url (http://username:password@URL), it loads up the content correctly. Reproducible: Always Steps to Reproduce: 1. See attached reproduction. Actual Results: 402.1 forbidden page from IIS. Expected Results: Prompt for username and password. I tried this with Xulrunner 1.8.20050.5168, 1.8.20050.15673, and 1.9.20051.11408 with the same results.
Reporter | ||
Comment 1•19 years ago
|
||
This is a very small sample app to demonstrate the problem.
Comment 2•19 years ago
|
||
chrome-type docshells do not prompt for auth by default (bug 267367, bug 260836). you need to make the frame a content docshell or explicitly enable auth. I think you can do the former by setting an attribute type="content" or type="content-primary" on the iframe, although I'm not 100% sure that it works on non-browsers.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Assignee | ||
Updated•8 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•