moby--moby/registry
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 Move IndexInfo and ServiceConfig types to api/types/registry/registry.go 2015-12-14 11:28:02 -05:00
auth_test.go Move the TestEncodeAuth test to the correct package. 2015-12-15 13:36:52 -05:00
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 Check if CertsDir is not empty 2015-11-25 18:12:19 +01:00
config_windows.go
endpoint.go Move IndexInfo and ServiceConfig types to api/types/registry/registry.go 2015-12-14 11:28:02 -05:00
endpoint_test.go
reference.go
registry.go Add missing bounds in ContinueOnError 2015-12-08 09:54:20 -08:00
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