update examples for upstream mapping

Author: Hisham

README.md

@@ -88,7 +88,7 @@ for this to work it requires inserting a root CA certificate into system trusted
 - Env `AUTH_REGISTRIES_DELIMITER` to change the separator between authentication info. By default, a space: "` `". If you use keys that contain spaces (as with Google Cloud Registry), you should update this variable, e.g. setting it to `AUTH_REGISTRIES_DELIMITER=";;;"`. In that case, `AUTH_REGISTRIES` could contain something like `registry1.com:user1:pass1;;;registry2.com:user2:pass2`.
 - Env `AUTH_REGISTRY_DELIMITER` to change the separator between authentication info *parts*. By default, a colon: "`:`". If you use keys that contain single colons, you should update this variable, e.g. setting it to `AUTH_REGISTRIES_DELIMITER=":::"`. In that case, `AUTH_REGISTRIES` could contain something like `registry1.com:::user1:::pass1 registry2.com:::user2:::pass2`.
 - Env `UPSTREAM_MAPPING` to configure upstream server mappings (similar in functionality to /etc/hosts entries but with round-robin selection).
-Useful when configured resolvers are unable to resolve a host. e.g. `UPSTREAM_MAPPING="registry1=10.0.1.10,10.0.1.11 registry2=5.0.1.10"`
+Useful when configured resolvers are unable to resolve a host. e.g. `UPSTREAM_MAPPING="registry1=10.0.1.10:443,10.0.1.11 registry2=5.0.1.10"`
 - Timeouts ENVS - all of them can pe specified to control different timeouts, and if not set, the defaults will be the ones from `Dockerfile`. The directives will be added into `http` block.:
   - SEND_TIMEOUT : see [send_timeout](http://nginx.org/en/docs/http/ngx_http_core_module.html#send_timeout)
   - CLIENT_BODY_TIMEOUT : see [client_body_timeout](http://nginx.org/en/docs/http/ngx_http_core_module.html#client_body_timeout)

entrypoint.sh

@@ -39,9 +39,9 @@ else
 fi
 
 # Generate nginx upstream blocks into file. Function similar to a /etc/hosts file but includes round-robin selection
-# e.g when UPSTREAM_MAPPING="registry1=10.0.1.10,10.0.1.11 registry2=5.0.1.10", the following file is generated
+# e.g when UPSTREAM_MAPPING="registry1=10.0.1.10:443,10.0.1.11 registry2=5.0.1.10", the following file is generated
 # upstream registry1 {
-#         server 10.0.1.10;
+#         server 10.0.1.10:443;
 #         server 10.0.1.11;
 # }
 # upstream registry2 {