Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

object: specify 0:0 range requests as special #315

Merged
merged 1 commit into from
Dec 25, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion object/service.proto
Original file line number Diff line number Diff line change
Expand Up @@ -615,7 +615,9 @@ message SearchV2Response {
neo.fs.v2.session.ResponseVerificationHeader verify_header = 3;
}

// Object payload range. Ranges of zero length SHOULD be considered as invalid.
// Object payload range. Ranges of zero length SHOULD be considered as invalid
// except for the special 0:0 request which is interpreted as "get whole
// payload" and allows to receive payload only when its size is not known.
message Range {
// Offset of the range from the object payload start
uint64 offset = 1;
Expand Down
4 changes: 3 additions & 1 deletion proto-docs/object.md
Original file line number Diff line number Diff line change
Expand Up @@ -723,7 +723,9 @@ PUT Object response body
<a name="neo.fs.v2.object.Range"></a>

### Message Range
Object payload range. Ranges of zero length SHOULD be considered as invalid.
Object payload range. Ranges of zero length SHOULD be considered as invalid
except for the special 0:0 request which is interpreted as "get whole
payload" and allows to receive payload only when its size is not known.


| Field | Type | Label | Description |
Expand Down
Loading