Issue 372136 in chromium: XMLHttpRequest fails for responses with HTTP status 407

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Cr-Internals-Network Pri-2 Via-Wizard Type-Bug OS-Linux

New issue 372136 by krewech...@gmail.com: XMLHttpRequest fails for
responses with HTTP status 407
http://code.google.com/p/chromium/issues/detail?id=372136

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like
Gecko) Ubuntu Chromium/34.0.1847.116 Chrome/34.0.1847.116 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Send any XHR to a server.
2. Have the server return a 407 response.

What is the expected behavior?
The response is treated like any other HTTP response.

What went wrong?
The developer console shows "net::ERR_UNEXPECTED_PROXY_AUTH" instead
of "407 (Proxy Authentication Required)" next to the failed request.

The XMLHttpRequest object is empty:
xhr.responseText is ""
xhr.status is 0
xhr.statusText is ""

In a test sweep over responses with 57 different response HTTP status
codes, only code 407 exhibited this behavior.

I could not reproduce anything similar in Firefox 29, Opera 20, IE 10,
Safari 7, or the Android browser.

Did this work before? N/A

Chrome version: 34.0.1847.116 Channel: n/a
OS Version:
Flash Version:

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Labels: Cr-Internals-Network-Auth Cr-Internals-Network-Proxy

Comment #1 on issue 372136 by mme...@chromium.org: XMLHttpRequest fails for

responses with HTTP status 407
http://code.google.com/p/chromium/issues/detail?id=372136

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #2 on issue 372136 by asa...@chromium.org: XMLHttpRequest fails for

responses with HTTP status 407
http://code.google.com/p/chromium/issues/detail?id=372136

Is there a proxy in use? If the request wasn't going through a proxy server
and a 407 is received, then there's no proxy server to authenticate with.
Hence the net::ERR_UNEXPECTED_PROXY_AUTH.

[chro...@googlecode.com]

Comment #4 on issue 372136 by ri...@chromium.org: XMLHttpRequest fails for

responses with HTTP status 407

https://code.google.com/p/chromium/issues/detail?id=372136

Unless it happens when there is actually a proxy server involved, I am
inclined to consider this "works as intended". I don't see a compelling use
case for passing the 407 code back to Javascript.

[chro...@googlecode.com]

Updates:
Labels: Needs-Feedback

Comment #5 on issue 372136 by yhi...@chromium.org: XMLHttpRequest fails

for responses with HTTP status 407
https://code.google.com/p/chromium/issues/detail?id=372136

https://fetch.spec.whatwg.org/#http-fetch says the UA must retry when
receiving 407, so there is no way to receive a 407 response as an XHR
client.