ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2025-02-21 18:06:46 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Yay use the Range request header

Browse Source
This commit is contained in:
Jean-Paul Calderone 2021-09-07 14:17:38 -04:00
parent 9def6e79c9
commit 82f94ae5af
1 changed files with 7 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/proposed/http-storage-node-protocol.rst
View File

@ -539,24 +539,20 @@ For example::
[1, 5] [1, 5]
``GET /v1/immutable/:storage_index/:share_number?offset=:offset&length=:length ``GET /v1/immutable/:storage_index/:share_number
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Read a contiguous sequence of bytes from one share in one bucket. Read a contiguous sequence of bytes from one share in one bucket.
If the ``offset`` query parameter is given then it is interpreted as a base 10 representation of an integer giving the position at which to begin reading.
If it is not given then begin reading at the beginning of the share.
If the ``length`` query parameter is given then it is interpreted as a base 10 representation of an integer giving the maximum number of bytes to read and return.
If it is not given then bytes will be read until the end of the share is reached.
The response body is the raw share data (i.e., ``application/octet-stream``). The response body is the raw share data (i.e., ``application/octet-stream``).
The ``Range`` header may be used to request exactly one ``bytes`` range.
Interpretation and response behavior is as specified in RFC 7233 § 4.1.
Multiple ranges in a single request are *not* supported.
Discussion Discussion
`````````` ``````````
Offset and length of the requested data are specified here as query arguments. Multiple ``bytes`` ranges are not supported.
Instead, this information could be present in a ``Range`` header in the request. HTTP requires that the ``Content-Type`` of the response in that case be ``multipart/...``.
This is the more obvious choice and leverages an HTTP feature built for exactly this use-case.
However, HTTP requires that the ``Content-Type`` of the response to "range requests" be ``multipart/...``.
The ``multipart`` major type brings along string sentinel delimiting as a means to frame the different response parts. The ``multipart`` major type brings along string sentinel delimiting as a means to frame the different response parts.
There are many drawbacks to this framing technique: There are many drawbacks to this framing technique: