mirror of
https://github.com/tahoe-lafs/tahoe-lafs.git
synced 2024-12-20 05:28:04 +00:00
webapi.rst: document Range: header on GET requests
closes ticket#2460
This commit is contained in:
parent
6252a72965
commit
c3608f61d9
@ -348,7 +348,10 @@ Reading a File
|
|||||||
``GET /uri/$DIRCAP/[SUBDIRS../]FILENAME``
|
``GET /uri/$DIRCAP/[SUBDIRS../]FILENAME``
|
||||||
|
|
||||||
This will retrieve the contents of the given file. The HTTP response body
|
This will retrieve the contents of the given file. The HTTP response body
|
||||||
will contain the sequence of bytes that make up the file.
|
will contain the sequence of bytes that make up the file. The "Range:"
|
||||||
|
header can be used to restrict which portions of the file are returned (see
|
||||||
|
RFC 2616 section 14.35.1 "Byte Ranges"), however Tahoe only supports a
|
||||||
|
single "bytes" range and never provides a `multipart/byteranges` response.
|
||||||
|
|
||||||
To view files in a web browser, you may want more control over the
|
To view files in a web browser, you may want more control over the
|
||||||
Content-Type and Content-Disposition headers. Please see the next section
|
Content-Type and Content-Disposition headers. Please see the next section
|
||||||
|
Loading…
Reference in New Issue
Block a user