Skip to content

Commit 5025143

Browse files
committed
OCI-Subject: <subject digest>
Signed-off-by: Jason Hall <[email protected]>
1 parent 16cc054 commit 5025143

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

spec.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -454,9 +454,9 @@ Client and registry implementations SHOULD expect to be able to support manifest
454454

455455
###### Pushing Manifests with Subject
456456

457-
When processing a request for an image or artifact manfiest with the `subject` field, a registry implementation that supports the [referrers API](#listing-referrers) MUST respond with the response header `OCI-Subject-Processed: true` to indicate to the client that the registry understands the request's `subject`.
457+
When processing a request for an image or artifact manfiest with the `subject` field, a registry implementation that supports the [referrers API](#listing-referrers) MUST respond with the response header `OCI-Subject: <subject digest>` to indicate to the client that the registry processed the request's `subject`.
458458

459-
When pushing an image or artifact manifest with the `subject` field and the [referrers API](#listing-referrers) returns a 404 or the `OCI-Subject-Processed: true` header was not set, the client MUST:
459+
When pushing an image or artifact manifest with the `subject` field and the [referrers API](#listing-referrers) returns a 404 or the `OCI-Subject` header was not set, the client MUST:
460460

461461
1. Pull the current referrers list using the [referrers tag schema](#referrers-tag-schema).
462462
1. If that pull returns a manifest other than the expected image index, the client SHOULD report a failure and skip the remaining steps.

0 commit comments

Comments
 (0)