diff options
author | Zhao Chao <zhaochao1984@gmail.com> | 2018-03-02 17:03:44 +0800 |
---|---|---|
committer | Zhao Chao <zhaochao1984@gmail.com> | 2018-03-02 20:57:23 +0800 |
commit | d597bb4714e666c924e8a48ad30ebad71a3b45ed (patch) | |
tree | 6e1a2c509132bcb2deea0bbe8a18eaeb804b8ea9 /api-ref | |
parent | f71719a0f374746a96ad4681458185f953f08add (diff) | |
download | trove-d597bb4714e666c924e8a48ad30ebad71a3b45ed.tar.gz |
Return 204 instead of 200 for root-disable API
As no content will be returned to the client if a root-disable request
succeeds, a HTTP 204 (Not Content) response is more appropriate.
Redis root-disable scenario test fails because it's return HTTP 204, but
all API related tests are expecting a HTTP 200. Although changing Redis
root-disable API is a much simpler way to resolve the problem, migrating
from HTTP 200 to HTTP 204 should be a better solution. Related tests and
documents are also updated accordingly.
APIImpact
Change-Id: If732a578009fd35436e810fb7ceceefd1ada3778
Signed-off-by: Zhao Chao <zhaochao1984@gmail.com>
Diffstat (limited to 'api-ref')
-rw-r--r-- | api-ref/source/samples/db-disable-root-user-response-json-http.txt | 2 | ||||
-rw-r--r-- | api-ref/source/user-management.inc | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/api-ref/source/samples/db-disable-root-user-response-json-http.txt b/api-ref/source/samples/db-disable-root-user-response-json-http.txt index 031611ac..17632f6a 100644 --- a/api-ref/source/samples/db-disable-root-user-response-json-http.txt +++ b/api-ref/source/samples/db-disable-root-user-response-json-http.txt @@ -1,4 +1,4 @@ -HTTP/1.1 200 OK +HTTP/1.1 204 No Content Content-Type: application/json Content-Length: 0 Date: Mon, 18 Mar 2013 19:09:17 GMT diff --git a/api-ref/source/user-management.inc b/api-ref/source/user-management.inc index 595c442e..d17be907 100644 --- a/api-ref/source/user-management.inc +++ b/api-ref/source/user-management.inc @@ -92,7 +92,7 @@ Disable root user Disables the root user. -Normal response codes: 202 +Normal response codes: 204 Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), badMethod(405), overLimit(413), unprocessableEntity(422), |