[Webkit-unassigned] [Bug 11640] New: XMLHttpRequest produces undefined:undefined HTTP authentication

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Nov 17 20:42:15 PST 2006


           Summary: XMLHttpRequest produces undefined:undefined HTTP
           Product: WebKit
           Version: 420+ (nightly)
          Platform: Macintosh
               URL: http://www.fulgore.net/prototype.js
        OS/Version: Mac OS X 10.4
            Status: UNCONFIRMED
          Severity: Major
          Priority: P2
         Component: WebCore JavaScript
        AssignedTo: webkit-unassigned at opendarwin.org
        ReportedBy: gary at fulgore.net

Prototype line 775 seems to be culprit.

If you are authenticated to a basic realm and then use XMLHttpRequest through
Prototype - it results in a request to http://undefined:undefined@hostname
which in turn prevents you from being able to complete the request.

Some chat transcript from bdash below:

20:13 < bdash> the prototype code calls
transport.open(this.options.method.toUpperCase(), this.url,
               this.options.asynchronous, this.options.username,
20:14 < bdash> this.options is an object consisting of some default fields,
merged with the configuration you pass to Ajax.Request
20:14 < bdash> there is no username or password key, so this.options.username
and this.options.password are both undefined
20:15 < bdash> our behaviour obviously differs from Firefox in the case of
undefined, though the work-in-progress XMLHttpRequest specification says that
no username and password should be indicated by 'null'

Extent of browser testing as follows:

IE Windows - Request completes ok
FF Windows - Request completes ok
FF OSX - Request completes ok
SF/WK OSX - Request fails

Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list