5 commits

Author	SHA1	Message	Date
Milos Gajdos	45b7b9cec3	Dont parse errors as JSON unless Content-Type is set to JSON ... Client attempts to parse the body of every error it receives as JSON regardless of the content-type. This commit rectifies by only parsing he error body as JSON if the Content-Type header is set to either "application/json" or "application/vnd.api+json". Signed-off-by: Milos Gajdos <milosthegajdos@gmail.com>	2023-08-28 12:35:33 +01:00
Paweł Gronowski	5f1df02149	registry/errors: Parse http forbidden as denied ... Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>	2023-04-27 19:48:32 +02:00
Aaron Lehmann	3a2231fe39	Include status code in UnexpectedHTTPResponseError ... Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>	2016-03-15 09:03:56 -07:00
Aaron Lehmann	cd6482ecb8	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
Kenny Leung	7ff5042c1e	Merge branch 'print-error-msg' of https://github.com/k4leung4/distribution into print-error-msg ... Changed to use typed error instead of formatted string. Added tests for new public method. Signed-off-by: Kenny Leung <kleung@google.com>	2015-12-29 16:26:13 -08:00