yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #02541
[Bug 1153718] Re: status 401 Not Authorized is not valid
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => havana-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1153718
Title:
status 401 Not Authorized is not valid
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
Keystone responds to some requests with a response status string like
"HTTP/1.1 401 Not Authorized". The "reason-phrase" for the 401 status
code is "Unauthorized", not "Not Authorized", so the response is not
valid HTTP.
See http://tools.ietf.org/html/rfc2616#section-10.4.2 .
For an example,
$ curl -i http://localhost:5000/v3/projects ; echo
HTTP/1.1 401 Not Authorized
Vary: X-Auth-Token
Content-Type: application/json
Content-Length: 116
Date: Mon, 11 Mar 2013 18:35:57 GMT
{"error": {"message": "The request you have made requires
authentication.", "code": 401, "title": "Not Authorized"}}
The response should be:
$ curl -i http://localhost:5000/v3/projects ; echo
HTTP/1.1 401 Unauthorized
Vary: X-Auth-Token
Content-Type: application/json
Content-Length: 116
Date: Mon, 11 Mar 2013 18:35:57 GMT
{"error": {"message": "The request you have made requires
authentication.", "code": 401, "title": "Not Authorized"}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1153718/+subscriptions