Aaron Lehmann a57478d65f Do not fall back to the V1 protocol when we know we are talking to a V2 registry ... If we detect a Docker-Distribution-Api-Version header indicating that the registry speaks the V2 protocol, no fallback to V1 should take place. The same applies if a V2 registry operation succeeds while attempting a push or pull. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>		2015-12-16 15:02:03 -08:00
..
auth.go
auth_test.go
authchallenge.go
config.go	Update Named reference with validation of conversions	2015-12-16 11:58:52 -08:00
config_test.go
config_unix.go
config_windows.go
endpoint.go
endpoint_test.go
reference.go
registry.go
registry_mock_test.go	Update Named reference with validation of conversions	2015-12-16 11:58:52 -08:00
registry_test.go	Update Named reference with validation of conversions	2015-12-16 11:58:52 -08:00
service.go	Do not fall back to the V1 protocol when we know we are talking to a V2 registry	2015-12-16 15:02:03 -08:00
service_v1.go	Update Named reference with validation of conversions	2015-12-16 11:58:52 -08:00
service_v2.go	Do not fall back to the V1 protocol when we know we are talking to a V2 registry	2015-12-16 15:02:03 -08:00
session.go	Update Named reference with validation of conversions	2015-12-16 11:58:52 -08:00
token.go
types.go	Update Named reference with validation of conversions	2015-12-16 11:58:52 -08:00