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.

Sign up for GitHub

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

Introduce OCI-Chunk-Max-Length header in the docs #486

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+8 −0
Open

Introduce OCI-Chunk-Max-Length header in the docs #486

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 8 additions & 0 deletions spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -325,6 +325,13 @@ If the registry has a minimum chunk size, the response SHOULD include the follow
OCI-Chunk-Min-Length: <size>
```


If the registry has a maximum chunk size, the response SHOULD include the following header, where `<size>` is the size in bytes (see the blob `PATCH` definition for usage):

```
OCI-Chunk-Max-Length: <size>
```

Please reference the above section for restrictions on the `<location>`.

---
Expand Down Expand Up @@ -353,6 +360,7 @@ It MUST match the following regular expression:
The `<length>` is the content-length, in bytes, of the current chunk.
If the registry provides a `OCI-Chunk-Min-Length` header in the `PUT` response, the size of each chunk, except for the final chunk, SHOULD be greater or equal to that value.
The final chunk MAY have any length.
If the registry provides a `OCI-Chunk-Max-Length` header in the `POST` response, the size of each chunk SHOULD be less or equal to that value.

Each successful chunk upload MUST have a `202 Accepted` response code, and MUST have the following headers:

Expand Down