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
..
api	api: url typo in specification	2017-07-18 14:48:55 -07:00
auth	context: remove definition of Context	2017-08-11 15:53:31 -07:00
client	Support HEAD requests without Docker-Content-Digest header	2017-08-25 17:18:01 -04:00
handlers	context: remove definition of Context	2017-08-11 15:53:31 -07:00
listener	[Server] Listen and serve on a unix socket	2015-05-11 16:00:14 +03:00
middleware	context: remove definition of Context	2017-08-11 15:53:31 -07:00
proxy	registry: remove dependency on logrus for client	2017-08-15 10:28:38 -07:00
storage	registry: remove dependency on logrus for client	2017-08-15 10:28:38 -07:00
doc.go	Move initialization code from main.go to the registry package	2015-09-09 14:39:31 -07:00
registry.go	context: remove definition of Context	2017-08-11 15:53:31 -07:00
registry_test.go	Allow registry clients to connect via http2	2016-08-13 22:07:42 -04:00
root.go	context: remove definition of Context	2017-08-11 15:53:31 -07:00