From 84b264baa8d81ceafa1ed6beb840c6fb80b91cc3 Mon Sep 17 00:00:00 2001 From: Kazuhiro MIYAHARA Date: Thu, 1 Sep 2016 14:59:56 +0900 Subject: [PATCH] Fix api reference of object GET request with Range parameter In RFC 7233, response body size of range requests with parameter 'bytes=N-M' is (M - N + 1). And response of object GET request with range parameter in current Swift implementation is according to the RFC. However, in current api reference explains that response body size of object GET request with 'Range: bytes=10-15' is five ( != 15 - 10 + 1). This patch fixes the api reference explanation. Change-Id: I8371864f8e5adb42c1e56b7ea26c556ea1252728 --- api-ref/source/parameters.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/api-ref/source/parameters.yaml b/api-ref/source/parameters.yaml index a687e1cbbe..28e7a93e4c 100644 --- a/api-ref/source/parameters.yaml +++ b/api-ref/source/parameters.yaml @@ -234,9 +234,9 @@ Range: - **Suffix byte range specification**. Use LENGTH bytes to specify the length of the data range. The following forms of the header specify the following ranges of data: - ``Range: bytes=-5``. The - last five bytes. - ``Range: bytes=10-15``. The five bytes of data + last five bytes. - ``Range: bytes=10-15``. The six bytes of data after a 10-byte offset. - ``Range: bytes=10-15,-5``. A multi- - part response that contains the last five bytes and the five + part response that contains the last five bytes and the six bytes of data after a 10-byte offset. The ``Content-Type`` response header contains ``multipart/byteranges``. - ``Range: bytes=4-6``. Bytes 4 to 6 inclusive. - ``Range: bytes=2-2``. Byte