Don't place the verificationtoken.txt file on a page with multiple redirects

When using the HTTP Practical Demonstration method for domain validation, the verificationtoken.txt file may be placed on a page that contains up to one redirect. With a single redirect, we are still able to locate the verificationtoken.txt file and verify your control over the domain.

For example, you need a certificate for http://example.com. However, the page redirects to https://www.example.com. That’s okay. You can place the verificationtoken.txt file on the http://example.com page. We can follow the single redirect to validate your control over http://example.com.

However, if you place the verificationtoken.txt file on a page with multiple redirects, we won’t be able to locate the file. Multiple redirects block us from locating the verificationtoken.txt file and validating your control over the domain.

For example, you need a certificate for http://multiple-redirect.com. However, the page redirects to https://www.multiple-redirect.com and then redirects again to https://www.single-redirect.com.

In situation, you must still place the verificationtoken.txt file on the http://multiple-redirect.com page. However, you'll need to disable the second redirect (https://www.single-redirect.com) long enough for us to locate the verificationtoken.txt and validate your control over http://multiple-redirect.com.