distribution/registry/client
Clayton Coleman a2015272c1
Support HEAD requests without Docker-Content-Digest header
A statically hosted registry that responds correctly to GET with a
manifest will load the right digest (by looking at the manifest body and
calculating the digest). If the registry returns a HEAD without
`Docker-Content-Digest`, then the client Tags().Get() call will return
an empty digest.

This commit changes the client to fallback to loading the tag via GET if
the `Docker-Content-Digest` header is not set.

Signed-off-by: Clayton Coleman <ccoleman@redhat.com>
2017-08-25 17:18:01 -04:00
..
auth If the request already has the scope, don't force token fetch 2017-08-23 19:27:37 -04:00
transport registry/client: set Accept: identity header when getting layers 2016-10-25 10:33:11 +02:00
blob_writer.go context: remove definition of Context 2017-08-11 15:53:31 -07:00
blob_writer_test.go Add ability to pass in substitution args into an Error 2015-07-15 11:02:10 -07:00
errors.go Update oauth errors to use api errors 2016-11-09 19:29:18 -08:00
errors_test.go Include status code in UnexpectedHTTPResponseError 2016-03-15 09:03:56 -07:00
repository.go Support HEAD requests without Docker-Content-Digest header 2017-08-25 17:18:01 -04:00
repository_test.go Support HEAD requests without Docker-Content-Digest header 2017-08-25 17:18:01 -04:00