distribution/registry/api/v2
Stephen J Day 006214d902 Paginate catalog and tag results with Link header
Move the specification to use a Link header, rather than a "next" entry in the
json results. This prevents requiring clients from parsing the request body to
issue the next request. It also ensures that the returned response body does
not change in between requests.

The ordering of the specification has been slightly tweaked, as well. Listing
image tags has been moved after the catalog specification. Tag pagination now
heavily references catalog pagination.

Signed-off-by: Stephen J Day <stephen.day@docker.com>
2015-07-21 21:45:14 -07:00
..
descriptors.go Paginate catalog and tag results with Link header 2015-07-21 21:45:14 -07:00
doc.go Move registry api definitions under registry package 2015-02-10 17:32:22 -08:00
errors.go Move challenge http status code logic 2015-06-17 18:23:55 -07:00
names.go Allow single character repository names 2015-07-10 12:10:42 -06:00
names_test.go Allow single character repository names 2015-07-10 12:10:42 -06:00
routes.go Catalog V2 API specification proposal 2015-07-21 21:45:14 -07:00
routes_test.go Allow single character repository names 2015-07-10 12:10:42 -06:00
urls.go Updated urlbuilder X-Forwarded-Host logic 2015-04-24 14:16:49 -07:00
urls_test.go Updated urlbuilder X-Forwarded-Host logic 2015-04-24 14:16:49 -07:00