distribution/registry
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
..
api registry: feed the linter by removing redundant err check 2017-09-29 13:27:49 -07:00
auth context: remove definition of Context 2017-08-11 15:53:31 -07:00
client Properly follow relative links when listing tags 2017-11-18 22:04:19 -08:00
handlers registry/handlers: ignore notfound on storage driver healthcheck 2017-08-21 15:04: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: feed the linter by removing redundant err check 2017-09-29 13:27:49 -07:00
storage registry: feed the linter by removing redundant err check 2017-09-29 13:27:49 -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