From 0481515ee56fff510fd96173fca26b9cbc9bae47 Mon Sep 17 00:00:00 2001
From: Jacob Hoffman-Andrews <github@hoffman-andrews.com>
Date: Mon, 13 Mar 2017 11:14:37 -0700
Subject: [PATCH] Specify server MAY follow HTTP redirects. (#238)

* Specify server MAY follow HTTP redirects.

Per HTTP RFC: https://tools.ietf.org/html/rfc7231#section-6.4

* MAY->SHOULD
---
 draft-ietf-acme-acme.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/draft-ietf-acme-acme.md b/draft-ietf-acme-acme.md
index a2cd7dd5..aa982358 100644
--- a/draft-ietf-acme-acme.md
+++ b/draft-ietf-acme-acme.md
@@ -1948,6 +1948,8 @@ domain by verifying that the resource was provisioned as expected.
 5. Verify that key authorization provided by the HTTP server matches the token
    for this challenge and the client's account key.
 
+The server SHOULD follow redirects when dereferencing the URI.
+
 If all of the above verifications succeed, then the validation is successful.
 If the request fails, or the body does not pass these checks, then it has
 failed.