docker/registry
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
auth_test.go
config.go
config_test.go
config_unix.go
config_windows.go
endpoint_test.go
endpoint_v1.go
registry.go
registry_mock_test.go
registry_test.go
service.go
service_v1.go
service_v1_test.go
service_v2.go
session.go
types.go