nova returns 204 for not authenticated user

[Aaron Lee]

Mr. Dietz suggested that this looks like this is coming from the NoAuthMiddleware.

$ curl -v http://10.127.4.226:8774/v1.1/flavors/detail.json
* About to connect() to 10.127.4.226 port 8774 (#0)
* Trying 10.127.4.226... connected
* Connected to 10.127.4.226 (10.127.4.226) port 8774 (#0)
> GET /v1.1/flavors/detail.json HTTP/1.1
> User-Agent: curl/7.21.4 (universal-apple-darwin11.0) libcurl/7.21.4 OpenSSL/0.9.8r zlib/1.2.5
> Host: 10.127.4.226:8774
> Accept: */*
>
< HTTP/1.1 204 No Content
< Content-Length: 0
< X-Auth-Token: admin:admin
< X-Server-Management-Url: http://10.127.4.226:8774/v1.1/flavors/detail.json/admin
< X-Storage-Url:
< X-Cdn-Management-Url:
< Content-Type: text/plain; charset=UTF-8
< Date: Fri, 30 Sep 2011 22:50:33 GMT
<
* Connection #0 to host 10.127.4.226 left intact
* Closing connection #0

[Brian Waldon (bcwaldon)]

I've noticed this, too. It always happens when I don't provide an X-Auth-Token or forget to put the tenant id in the url.

[Thierry Carrez (ttx)]

What's expected behavior ?

[Nirmal Ranganathan (rnirmal)]

I'd suggest for X-Auth-Token not being provided should just be a 401 and for the TENANT not being provided in the URL a 404. Just my thought.

[Sean Dague (sdague)]

This appears to be fixed in upstream