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
..
api	Adds cross-repository blob mounting behavior	2016-01-08 13:53:18 -08:00
auth	De-obfuscate error message	2015-11-06 17:10:28 -08:00
client	Splits up blob create options definitions to be package-specific	2016-01-14 10:47:33 -08:00
handlers	Do not require "charset=utf-8" for a schema1 with content type application/json	2016-01-18 09:59:50 -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	Adds functional options arguments to the Blobs Create method	2016-01-13 16:42:59 -08:00
storage	Merge pull request #1332 from RichardScothern/gcs-params	2016-01-14 15:50:09 -08:00
doc.go	Move initialization code from main.go to the registry package	2015-09-09 14:39:31 -07:00
registry.go	Add WithVersion to context and other cleanup	2015-09-14 17:14:31 -07:00