distribution/registry/client
Kevin Lin 1bfbeca726 Properly follow relative links when listing tags
The previous code assumed that the link returned when listing tags was
always absolute. However, some registries, such as quay.io, return the
link as a relative link (e.g. the second page for the quay.io/coreos/etcd
image is /v2/coreos/etcd/tags/list?next_page=<truncated>&n=50). Because
the relative link was retrieved directly, the fetch failed (with the
error `unsupported protocol scheme ""`).

Signed-off-by: Kevin Lin <kevin@kelda.io>
2017-11-18 22:04:19 -08: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 Properly follow relative links when listing tags 2017-11-18 22:04:19 -08:00
repository_test.go Properly follow relative links when listing tags 2017-11-18 22:04:19 -08:00