From 9f8a4e29699eded5ace26c948abce73a713084b6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fran=C3=A7ois=20Kooman?= Date: Wed, 25 Nov 2015 13:00:10 +0100 Subject: [PATCH] do not mention response bodies for errors, no point to have those for the storage API --- draft-dejong-remotestorage-06.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-dejong-remotestorage-06.txt b/draft-dejong-remotestorage-06.txt index e60437e..64be202 100644 --- a/draft-dejong-remotestorage-06.txt +++ b/draft-dejong-remotestorage-06.txt @@ -286,8 +286,8 @@ Internet-Draft remoteStorage November 2015 If not exactly one Content-Type header was received as part of a PUT request, the Content-Type header value contains non-ASCII characters, or it is unreasonably long, the server MAY refuse to - process the request, and instead respond with a descriptive error - message in the body, and a http response code from the 4xx range. + process the request, and instead respond with a HTTP response code + from the 4xx range. The response MUST contain a strong ETag header, with the document's new version (for instance a hash of its contents) as its value.