Identity API v3 showing wrong normal response codes for HEAD calls

[Timothy Symanczyk]

http://developer.openstack.org/api-ref-identity-v3.html

All of the HEAD calls listed in the Identity API v3 give 200 as their normal response codes. However in practice keystone seems to return 204 No Content as a normal response code for HEAD calls, which is more correct.

[Brant Knudson (blk-u)]

According to the HTTP RFC, the HEAD response status code should be the same as if a GET response was done, and this is forcecd when you run keystone in apache httpd because it converts HEAD requests to get requests.

[Brant Knudson (blk-u)]

Reference to the RFC: http://tools.ietf.org/html/rfc7231#section-4.3.2

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/214812

[Timothy Symanczyk (timothy-symanczyk)]

Brant, please confirm - you are saying that this bug is invalid and that the documentation SHOULD say 200?

Please note then in file api-ref/src/wadls/identity-api/src/v3/wadl/identity-admin-v3.wadl, line 767...

     <!--There is no response. As noted above, an HTTP 204 indicates success-->

... I'm not trying to change anyone's mind either way. But simply noting that right now there is at least an inconsistancy.

[Timothy Symanczyk (timothy-symanczyk)]

I've already noted this in the comments for the change, but just so it's here as well :

In my own testing with curl and devstack, the APIs in real life show 204.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/214812
Committed: https://git.openstack.org/cgit/openstack/api-site/commit/?id=4be3df1c1258cfadfdba64cba658a3e1cfc339c1
Submitter: Jenkins
Branch: master

commit 4be3df1c1258cfadfdba64cba658a3e1cfc339c1
Author: Timothy Symanczyk <email address hidden>
Date: Fri Aug 14 23:27:29 2015 -0700

    Fix incorrect responses codes in Identity API v3

    For these six HEAD calls, the correct normal response code is
    204 No Content.

    Change-Id: I2b23eed10088831df6168bdbf09c4ad39b7adb4f
    Closes-Bug: #1486739