summaryrefslogtreecommitdiffstats
path: root/docs/reference/plugins/validation/http/index.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/reference/plugins/validation/http/index.md')
-rw-r--r--docs/reference/plugins/validation/http/index.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/reference/plugins/validation/http/index.md b/docs/reference/plugins/validation/http/index.md
index 71a67b9..41a4f3d 100644
--- a/docs/reference/plugins/validation/http/index.md
+++ b/docs/reference/plugins/validation/http/index.md
@@ -10,8 +10,9 @@ but for the sake of this explanation it will suffice).
- The client has to make sure that when the ACME server makes a request
to `http://sub.example.com/.well-known/acme-challenge/x`, the answer will be exactly `y`.
- The validation request is *always* made to port 80, that cannot be changed.
+- Let's Encrypt **does** follow 301/302 redirects
- There may be more than one validation request for the same token, e.g. from
different locations or different protocols (IPv4/IPv6).
-- Let's Encrypt does *not* disclose the source locations of these requests, which
+- Let's Encrypt does **not** disclose the source locations of these requests, which
effectively means that the domain has to be accessible for the public,
at least for the duration of the validation. \ No newline at end of file