Bug #4704
Document file ranges and make them friendly
| Status: | New | Start date: | 12/03/2013 | ||
|---|---|---|---|---|---|
| Priority: | Medium | Due date: | 12/04/2013 | ||
| Assignee: | Stavros Sachtouris | % Done: | 50% |
||
| Category: | kamaki | Spent time: | 1.00 hour | ||
| Target version: | v0.13 | Estimated time: | 1.00 hour |
Description
When requesting multiple ranges of bytes from a file using --range, kamaki
prints whatever the server responds, as usual. The format of the response,
although standard ( see http://www.ietf.org/rfc/rfc2616.txt section 19.2),
it might be confusing for the users, for two reasons:
A. Insufficient help / documentation
B. User will have to reconcile data parts with external scripts
To resolve A, document the multi-part range functionality wherever it is supported in kamaki commands.
To resolve B, remove boundaries and body headers from the response, except if otherwise required by the user (by using the --output-format=json or -j/--json arguments)
Associated revisions
Elaborate range argument usage
Refs: #4704
History
#1 Updated by Stavros Sachtouris almost 10 years ago
- Due date set to 12/04/2013
- Estimated time set to 1.00
#2 Updated by Stavros Sachtouris almost 10 years ago
- Subject changed from Kamaki prints unneeded data when requesting multiple byte ranges from a file to Document file ranges and make them friendly
#3 Updated by Stavros Sachtouris almost 10 years ago
- Target version changed from v0.12 to v0.13
- % Done changed from 0 to 50