openstack/keystone
Code Issues Proposed changes

Document and add release note for HEAD APIs

Browse Source 
Now that all GET APIs have a corresponding HEAD API, we can add a
formal statement about support and a release note.

Change-Id: Ia5569311f91d87b40d064595ce2c8d69461fbab7
Closes-Bug: 1696574
This commit is contained in:
Lance Bragstad 2017-06-27 21:04:06 +00:00
parent bece59e671
commit eb274afdb4
2 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
api-ref/source/v3/index.rst
View File

@ -18,6 +18,9 @@ policy rules based on a role-based access control (RBAC) approach.
The Identity service configuration file sets the name and location of a JSON
policy file that stores these rules.
Note that the V3 API implements HEAD for all GET requests. Each HEAD request
contains the same headers and HTTP status code as the corresponding GET API.
For information about Identity API protection, see
`Identity API protection with role-based access control (RBAC)
<https://docs.openstack.org/admin-guide/identity_service_api_protection.html>`_

8
releasenotes/notes/bug-1696574-15a728396350a95a.yaml Normal file
View File

@ -0,0 +1,8 @@
---
fixes:
- |
[`bug 1696574 <https://bugs.launchpad.net/keystone/+bug/1696574>`_]
All GET APIs within keystone now have support for HEAD, if not already
implemented. All new HEAD APIs have the same response codes and headers as
their GET counterparts. This aids in client-side processing, especially
caching.