From 16cc054de70442ea08e1aa269cee1c6cda5e7c96 Mon Sep 17 00:00:00 2001 From: Jason Hall Date: Thu, 2 Feb 2023 11:04:41 -0500 Subject: [PATCH] Specify subject-processed response header Signed-off-by: Jason Hall --- spec.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/spec.md b/spec.md index c306aa11..b0d24d50 100644 --- a/spec.md +++ b/spec.md @@ -454,7 +454,9 @@ Client and registry implementations SHOULD expect to be able to support manifest ###### Pushing Manifests with Subject -When pushing an image or artifact manifest with the `subject` field and the [referrers API](#listing-referrers) returns a 404, the client MUST: +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`. + +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: 1. Pull the current referrers list using the [referrers tag schema](#referrers-tag-schema). 1. If that pull returns a manifest other than the expected image index, the client SHOULD report a failure and skip the remaining steps.