From eb274afdb411e3de74ca36b5aad0b41a79089e77 Mon Sep 17 00:00:00 2001 From: Lance Bragstad Date: Tue, 27 Jun 2017 21:04:06 +0000 Subject: [PATCH] Document and add release note for HEAD APIs 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 --- api-ref/source/v3/index.rst | 3 +++ releasenotes/notes/bug-1696574-15a728396350a95a.yaml | 8 ++++++++ 2 files changed, 11 insertions(+) create mode 100644 releasenotes/notes/bug-1696574-15a728396350a95a.yaml diff --git a/api-ref/source/v3/index.rst b/api-ref/source/v3/index.rst index e5631cc81b..b95b04c450 100644 --- a/api-ref/source/v3/index.rst +++ b/api-ref/source/v3/index.rst @@ -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) `_ diff --git a/releasenotes/notes/bug-1696574-15a728396350a95a.yaml b/releasenotes/notes/bug-1696574-15a728396350a95a.yaml new file mode 100644 index 0000000000..ea54bf4032 --- /dev/null +++ b/releasenotes/notes/bug-1696574-15a728396350a95a.yaml @@ -0,0 +1,8 @@ +--- +fixes: + - | + [`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.