Aaron Lehmann c94c2a47a3 Don't return empty errcode.Errors slices ... If this slice ends up empty after parsing the HTTP response body, it means the body is not well-formed. We've probably encountered an error message produced by something that uses a different JSON schema, or an error that just happens to validate as JSON. An empty errcode.Errors slice is not a very useful thing to return, since its Error() output is just `<nil>`. Detect this case, and instend return an UnexpectedHTTPResponseError. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>		2016-03-14 10:27:01 -07:00
..
api	Merge pull request #1364 from aaronlehmann/content-type-in-api-docs	2016-03-01 13:53:49 -08:00
auth	Fix some typos in comments and strings	2016-02-23 22:33:38 +01:00
client	Don't return empty errcode.Errors slices	2016-03-14 10:27:01 -07:00
handlers	Adds new storagedriver.FileWriter interface	2016-03-08 16:37:44 -08: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	Fetch token by credentials and refresh token	2016-03-04 00:34:17 -08:00
storage	registry/storage/driver/s3-aws kms support	2016-03-11 17:19:01 -06:00
doc.go	Move initialization code from main.go to the registry package	2015-09-09 14:39:31 -07:00
garbagecollect.go	Implements garbage collection subcommand	2016-02-29 14:15:21 -08:00
garbagecollect_test.go	Implements garbage collection subcommand	2016-02-29 14:15:21 -08:00
registry.go	Implements garbage collection subcommand	2016-02-29 14:15:21 -08:00
root.go	Implements garbage collection subcommand	2016-02-29 14:15:21 -08:00