Platform intercepts requests to .well-known/acme-challenge/

[kirrrk]

Re: https://docs.pantheon.io/guides/global-cdn/https
Priority: Low

Issue Description

• The platform intercepts requests to .well-known/acme-challenge/ in order to serve the HTTP-01 challenge responses for Let's Encrypt, but this is not publicly documented anywhere.
• Customers sometimes need to verify their ownership of domains for third-party services and attempt to upload challenge files to .well-known/acme-challenge on their site.
• This has created confusing on the part of both customers and CSEs who end up troubleshooting when customers open tickets about being unable to update these files, sometimes mistakenly thinking this a problem with the CDN cache.

Could we add a note to our documentation to make it clear that these requests are intercepted and customers may need to use alternative methods of domain verification for third party services?

[rachelwhitton]

@kirrrk re: this bit in here

and customers may need to use alternative methods of domain verification for third party services

What sort of alternative methods do you recommend? Like another verification method entirely? Or workarounds so that the file method is possible?