From 321694a9e1870220a4722376f900c9c77ccf8d76 Mon Sep 17 00:00:00 2001 From: Peter Engelbert Date: Wed, 11 Nov 2020 16:42:54 -0600 Subject: [PATCH] Revert to old wording pertaining to digests Signed-off-by: Peter Engelbert --- spec.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/spec.md b/spec.md index 9d5bb595..a4e02aa3 100644 --- a/spec.md +++ b/spec.md @@ -333,9 +333,12 @@ The response to a successful mount MUST be `201 Created`, and MUST contain the f Location: ``` +The Location header will contain the registry URL to access the accepted layer file. The Docker-Content-Digest +header returns the canonical digest of the uploaded blob which MAY differ from the provided digest. Most clients MAY +ignore the value but if it is used, the client SHOULD verify the value against the uploaded blob data. -Alternatively, if a registry does not support cross-repository mounting, it SHOULD return a `202`, indicating that the -upload session has begun and that the client MAY proceed with the upload. +Alternatively, if a registry does not support cross-repository mounting or is unable to mount the requested blob, +it SHOULD return a `202`. This indicates that the upload session has begun and that the client MAY proceed with the upload. ##### Pushing Manifests