From 5025143d4d1cac5961afd504026d5da90c49d013 Mon Sep 17 00:00:00 2001 From: Jason Hall Date: Thu, 2 Feb 2023 19:49:45 -0500 Subject: [PATCH] OCI-Subject: Signed-off-by: Jason Hall --- spec.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spec.md b/spec.md index b0d24d50..00f3ab13 100644 --- a/spec.md +++ b/spec.md @@ -454,9 +454,9 @@ Client and registry implementations SHOULD expect to be able to support manifest ###### Pushing Manifests with Subject -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 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: ` to indicate to the client that the registry processed 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: +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: 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.