distribution/registry
Stephen J Day d00586de9f Use correct path for manifest revision path
Unfortunately, the refactor used the incorrect path for manifest links within a
repository. While this didn't stop the registry from working, it did break
compatibility with 2.0 deployments for manifest fetches.

Tests were added to ensure these are locked down to the appropriate paths.

Signed-off-by: Stephen J Day <stephen.day@docker.com>
2015-08-12 13:10:15 -07:00
..
api Move common error codes to errcode package 2015-08-11 11:50:58 -07:00
auth auth.AccessController interface now uses distribution/context 2015-07-23 19:48:47 -07:00
client Move common error codes to errcode package 2015-08-11 11:50:58 -07:00
handlers Move common error codes to errcode package 2015-08-11 11:50:58 -07:00
listener [Server] Listen and serve on a unix socket 2015-05-11 16:00:14 +03:00
middleware Add pull through cache functionality to the Registry which can be configured 2015-08-04 16:09:55 -07:00
proxy Move common error codes to errcode package 2015-08-11 11:50:58 -07:00
storage Use correct path for manifest revision path 2015-08-12 13:10:15 -07:00
doc.go Integrate layer info cache with registry and storage 2015-04-02 20:15:16 -07:00