distribution/registry
a-palchikov 82609180a1 tag service: properly handle error responses on HEAD requests by (#1918)
* tag service: properly handle error responses on HEAD requests by
re-issuing requests as GET for proper error details.

Fixes #1911.

Signed-off-by: dmitri <deemok@gmail.com>

* Simplify handling of failing HEAD requests in TagService and
make a GET request for cases:
  - if the server does not handle HEAD
  - if the response was an error to get error details

Signed-off-by: dmitri <deemok@gmail.com>

* Add a missing http.Response.Body.Close call for the GET request.

Signed-off-by: dmitri <deemok@gmail.com>
2016-08-26 14:35:04 -07:00
..
api
auth Merge pull request #1686 from marcusmartins/nbf-leeway 2016-07-19 17:41:57 -07:00
client tag service: properly handle error responses on HEAD requests by (#1918) 2016-08-26 14:35:04 -07:00
handlers Stop ErrFinishedWalk from escaping from Repositories walk 2016-08-05 17:21:48 -07:00
listener
middleware
proxy when deploy registry as a pull through cache ,function copeContent() may cause a socket leak when docker user canceled its pull operation. 2016-08-02 11:10:10 +08:00
storage Swift driver now bulk deletes in chunks specified by the server (#1915) 2016-08-24 10:09:25 -07:00
doc.go
registry.go Allow registry clients to connect via http2 2016-08-13 22:07:42 -04:00
registry_test.go Allow registry clients to connect via http2 2016-08-13 22:07:42 -04:00
root.go