You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: spec.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -226,6 +226,8 @@ When a manifest is rejected for this reason, it MUST result in one or more `MANI
226
226
227
227
There are two ways to push blobs: chunked or monolithic.
228
228
229
+
In each implementation, if the client provided digest is invalid or uses an unsupported algorithm, the registry SHOULD respond with a response code `400 Bad Request`.
230
+
229
231
#### Pushing a blob monolithically
230
232
231
233
There are two ways to push a blob monolithically:
@@ -330,6 +332,12 @@ The process remains unchanged for chunked upload, except that the post request M
330
332
Content-Length: 0
331
333
```
332
334
335
+
When pushing a blob with a digest algorithm other than `sha256`, the post request SHOULD include the `digest-algorithm` parameter:
Here, `<digest-algorithm>` is the algorithm the registry should use for the blob, e.g. `digest-algorithm=sha512`.
340
+
333
341
If the registry has a minimum chunk size, the `POST` response SHOULD include the following header, where `<size>` is the size in bytes (see the blob `PATCH` definition for usage):
334
342
335
343
```
@@ -835,6 +843,7 @@ This endpoint MAY be used for authentication/authorization purposes, but this is
0 commit comments