openstack/swift
Code Issues Proposed changes

Fix api reference of object GET request with Range parameter

Browse Source 
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
This commit is contained in:
Kazuhiro MIYAHARA 2016-09-01 14:59:56 +09:00
parent dd30b9ef98
commit 84b264baa8
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
api-ref/source/parameters.yaml
View File

@ -234,9 +234,9 @@ Range:
- **Suffix byte range specification**. Use LENGTH bytes to specify - **Suffix byte range specification**. Use LENGTH bytes to specify
the length of the data range. The following forms of the header the length of the data range. The following forms of the header
specify the following ranges of data: - ``Range: bytes=-5``. The 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- 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`` bytes of data after a 10-byte offset. The ``Content-Type``
response header contains ``multipart/byteranges``. - ``Range: response header contains ``multipart/byteranges``. - ``Range:
bytes=4-6``. Bytes 4 to 6 inclusive. - ``Range: bytes=2-2``. Byte bytes=4-6``. Bytes 4 to 6 inclusive. - ``Range: bytes=2-2``. Byte