Aaron Lehmann 5a2664e0b1 Do not require "charset=utf-8" for a schema1 with content type application/json ... For compatibility with other registries that don't use this exact variant of the Content-Type header, we need to be more flexible about what we accept. Any form of "application/json" should be allowed. The charset should not be included in the comparison. See docker/docker#19400. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>		2016-01-18 09:59:50 -08:00
..
config_builder_test.go	Adds functional options arguments to the Blobs Create method	2016-01-13 16:42:59 -08:00
config_builder.go	Add schema2 manifest support	2016-01-07 15:26:26 -08:00
manifest_test.go	Implementation of the Manifest Service API refactor.	2015-12-17 17:09:14 -08:00
manifest.go	Do not require "charset=utf-8" for a schema1 with content type application/json	2016-01-18 09:59:50 -08:00
reference_builder_test.go	Add schema2 manifest support	2016-01-07 15:26:26 -08:00
reference_builder.go	Add schema2 manifest support	2016-01-07 15:26:26 -08:00
sign.go	Implementation of the Manifest Service API refactor.	2015-12-17 17:09:14 -08:00
verify.go	Implementation of the Manifest Service API refactor.	2015-12-17 17:09:14 -08:00