From a5b2b63bcb3c29ce82967c9a624e66a24d67dc95 Mon Sep 17 00:00:00 2001 From: Wang Jie Date: Thu, 25 May 2017 07:48:29 +0800 Subject: [PATCH] Update deploying.md (#3373) --- docs/deploying.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/deploying.md b/docs/deploying.md index 4f68661d3..0ec593cdf 100644 --- a/docs/deploying.md +++ b/docs/deploying.md @@ -83,7 +83,7 @@ A certificate issuer may supply you with an *intermediate* certificate. In this ### Let's Encrypt -The registry supports using Let's Encrypt to automatically obtain a browser-trusted certificate. For more +The registry supports using Let's Encrypt to automatically obtain a browser-trusted certificate. For more information on Let's Encrypt, see [https://letsencrypt.org/how-it-works/](https://letsencrypt.org/how-it-works/) and the relevant section of the [registry configuration](configuration.md#letsencrypt). ### Alternatives @@ -124,7 +124,7 @@ and fallback to version 1 registries, if necessary. Confirming this is setup correctly can help avoid problems with fallback. In the same train of thought, you must make sure you are properly sending the -`X-Forwarded-Proto`, `X-Forwarded-For` and `Host` headers to their "client-side" +`X-Forwarded-Proto`, `X-Forwarded-For`, and `Host` headers to their "client-side" values. Failure to do so usually makes the registry issue redirects to internal hostnames or downgrading from https to http.