HTTP Authentication not supported

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Access a access protected URL (BASIC or DIGEST)
2. The standard authentication dialog that the browser pops up for receiving 
the username and password is never shown, instead we get 401 Unauthorized.
3.

What is the expected output? What do you see instead?
When accessing the access protected URL, the standard authentication dialog 
should popup to enter the username and password.

What version of the product are you using? On what operating system?
Advanced REST client Version 1.0.20 and Chrome Version 13.0.782.55 beta-m. I am 
running on Windows 7.

Please provide any additional information below.
This was working till some time back. This seems to be a problem with the 
newest Chrome beta release

Original issue reported on code.google.com by sures...@gmail.com on 13 Jul 2011 at 10:00

[GoogleCodeExporter]

According XMLHttpRequest level 2 spec:
"If authentication fails, Authorization is not in the list of author request 
headers, request username is null, and request password is null, user agents 
should prompt the end user for their username and password."
This is exactly the case. Chrome Rest Client do not set any credentials for 
user.
That is mean browser implementation of XMLHttpRequest l.2 is broken. 
But You always should use Authorization header to reflect real communication eg:
Authorization: Basic dGVzdGVyOnRlc3Rlcg==

You have helper program to fill Authorization header. Enter "Authorization" to 
header name field and click to header value field. You should see "construct" 
popup. You can authorization enter data there and construct proper header 
value. 

Original comment by jarro...@gmail.com on 13 Jul 2011 at 3:17

• Changed state: WontFix

[GoogleCodeExporter]

Hi,

I agree, it looks like the browser's XMLHttpRequest is broken in the latest
build. I will check this and file a bug in Chrome.

Original comment by sures...@gmail.com on 14 Jul 2011 at 3:39

[GoogleCodeExporter]

that helps 

Original comment by rmandep...@gmail.com on 18 Oct 2011 at 12:50

[GoogleCodeExporter]

Seems like a really advanced rest client... doesn't even support 
authentication. You might want to change the title of the app or fix this 
issue. 

Original comment by themattr...@gmail.com on 10 Apr 2012 at 11:17

[GoogleCodeExporter]

themattreid, that's unhelpful. The issue's been explained and the fault doesn't 
lie with this app. Auth support is great - aside from being a perfectly usable 
solution for this problem, that construction helper even includes a nice OAuth 
header constructor. Those kinds of touches are what makes this extension worthy 
of the "Advanced" in the name.

Original comment by m...@nerone.org on 16 Apr 2012 at 8:50