webapi.rst should document that Range requests are supported #2460

Closed
opened 2015-07-07 17:53:44 +00:00 by daira · 3 comments
daira commented 2015-07-07 17:53:44 +00:00
Owner

and that '416 Requested Range not satisfiable' is implemented.

and that '416 Requested Range not satisfiable' is implemented.
tahoe-lafs added the
documentation
normal
defect
1.10.0
labels 2015-07-07 17:53:44 +00:00
tahoe-lafs added this to the undecided milestone 2015-07-07 17:53:44 +00:00
tahoe-lafs added
1.10.1
and removed
1.10.0
labels 2015-07-07 17:54:04 +00:00
tahoe-lafs modified the milestone from undecided to 1.11.0 2015-07-07 17:54:04 +00:00
daira commented 2015-07-07 19:30:31 +00:00
Author
Owner

Also we should document whether or not multiple byteranges (returning a multipart/byteranges response) are supported.

Also we should document whether or not multiple byteranges (returning a `multipart/byteranges` response) are supported.
tahoe-lafs modified the milestone from 1.11.0 to 1.10.2 2015-07-17 21:54:07 +00:00

Fixed in [259ba07]. Multiple byteranges are not supported: all requests past the first are ignored.

Fixed in [259ba07]. Multiple byteranges are *not* supported: all requests past the first are ignored.
warner added the
fixed
label 2015-07-28 20:30:21 +00:00
daira commented 2015-07-28 21:58:08 +00:00
Author
Owner

Reviewed, +1.

Reviewed, +1.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#2460
No description provided.