Summary: | XMLHttpRequest needs to be extended before it can provide an alternative interface to the browser's dialog for HTTP auth | ||
---|---|---|---|
Product: | WebKit | Reporter: | Adam Ratcliffe <adam> |
Component: | XML | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW --- | ||
Severity: | Enhancement | CC: | ap, bfulgham, bugs-webkit, gavin.sharp, ian |
Priority: | P2 | ||
Version: | 420+ | ||
Hardware: | Mac | ||
OS: | OS X 10.4 | ||
Bug Depends on: | |||
Bug Blocks: | 10489 |
Description
Adam Ratcliffe
2006-04-10 01:47:25 PDT
Additionally, I think that our current implementation is inconsistent and/or broken (only shows the dialog for async requests, but doesn't seem to actually use the typed in credentials). (In reply to comment #1) > Additionally, I think that our current implementation is inconsistent and/or > broken (only shows the dialog for async requests, This is bug 8342. > but doesn't seem to actually use the typed in credentials). Looks like an NSURLConnection bug, rdar://4581439. It is probably possible to work around it in WebKit (by removing credentials from the URL passed to Foundation and handling them manually) , but I'm not sure if it's worth it. (In reply to Alexey Proskuryakov from comment #2) > (In reply to comment #1) > > Additionally, I think that our current implementation is inconsistent and/or > > broken (only shows the dialog for async requests, > > This is bug 8342. > > > but doesn't seem to actually use the typed in credentials). > > Looks like an NSURLConnection bug, rdar://4581439. It is probably possible > to work around it in WebKit (by removing credentials from the URL passed to > Foundation and handling them manually) , but I'm not sure if it's worth it. The NSURLConnection bug was fixed in OS X 10.5.3 (and newer) |