Yong Tang e49589505a Validate insecure registry (--insecure-registry) values ... This fix is based on: https://github.com/docker/docker/issues/29936#issuecomment-277494885 Currently the insecure registry is only checked to see if it contains scheme (`http(s)://`) or not. No fully validation is done and this caused many confusions like in #29936. This fix tries to address the issue. This fix adds additional validation so that an insecure registry is validated to make sure it is in `host:port` format where host could be IPv4/IPv6 or a host name, and port could be an integer between 0-65535. Additional unit tests have been added. This fix is related to #29936. Signed-off-by: Yong Tang <yong.tang.github@outlook.com>		2017-02-14 13:13:23 -08:00
..
auth.go	fix infinite recursion	2016-11-18 10:57:50 -02:00
auth_test.go
config.go	Validate insecure registry (--insecure-registry) values	2017-02-14 13:13:23 -08:00
config_test.go	Validate insecure registry (--insecure-registry) values	2017-02-14 13:13:23 -08:00
config_unix.go
config_windows.go
endpoint_test.go
endpoint_v1.go
registry.go
registry_mock_test.go	Use distribution reference	2017-02-07 11:08:37 -08:00
registry_test.go	Use distribution reference	2017-02-07 11:08:37 -08:00
service.go	Remove use of forked reference package for cli	2017-01-19 16:04:50 -08:00
service_v1.go	Disable v1 protocol for the default registry	2016-11-11 00:23:25 -08:00
service_v1_test.go	Disable v1 protocol for the default registry	2016-11-11 00:23:25 -08:00
service_v2.go	Disable v1 protocol for the default registry	2016-11-11 00:23:25 -08:00
session.go	Use distribution reference	2017-02-07 11:08:37 -08:00
types.go	Use distribution reference	2017-02-07 11:08:37 -08:00