From 9d4c4a9f8313ab785cd577e266564e915a8be090 Mon Sep 17 00:00:00 2001 From: Ramkumar Chinchani Date: Wed, 29 May 2024 17:23:25 +0000 Subject: [PATCH] Add support for content range requests when getting blobs OCI artifacts support has landed in various OCI specs v1.1.0 which allows for arbitrary artifact types, small and large. Large artifacts (even existing container images) pose a particular challenge that: 1) it takes too long to download 2) it takes too long to unpack This PR begins to address 1) above. The client can initiate a HEAD request to get the size and later multiple GET range requests to download a blob in parallel. Signed-off-by: Ramkumar Chinchani --- spec.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/spec.md b/spec.md index 2d50799f..c0ad49a5 100644 --- a/spec.md +++ b/spec.md @@ -190,6 +190,8 @@ If present, the value of this header MUST be a digest matching that of the respo If the blob is not found in the registry, the response code MUST be `404 Not Found`. +A registry SHOULD support the `Range` request header in accordance with [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-range-requests). + ##### Checking if content exists in the registry In order to verify that a repository contains a given manifest or blob, make a `HEAD` request to a URL in the following form: