distribution/registry/client
Damien Mathieu 8b31a894bd deduce blob UUID from location if it wasn't provided in the headers
Some registries (ECR) don't provide a `Docker-Upload-UUID` when creating
a blob. So we can't rely on that header. Fallback to reading it from the
URL.

Signed-off-by: Damien Mathieu <dmathieu@salesforce.com>
2019-06-25 09:29:38 +02:00
..
auth fix no error returned in fetchTokenWithOAuth 2019-04-14 11:05:59 +01:00
transport Enable static checks 2018-08-06 14:49:11 -07:00
blob_writer_test.go append the written bytes to the blob writer's size 2019-05-09 14:17:58 +02:00
blob_writer.go append the written bytes to the blob writer's size 2019-05-09 14:17:58 +02:00
errors_test.go Include status code in UnexpectedHTTPResponseError 2016-03-15 09:03:56 -07:00
errors.go Update oauth errors to use api errors 2016-11-09 19:29:18 -08:00
repository_test.go deduce blob UUID from location if it wasn't provided in the headers 2019-06-25 09:29:38 +02:00
repository.go deduce blob UUID from location if it wasn't provided in the headers 2019-06-25 09:29:38 +02:00