While the more commonly-asked-for HTTP to HTTPS request can be easily satisfied via a switch in our UI Request Settings, there’s also the situation where customers would like to redirect HTTPS to HTTP. There are two ways in which to accomplish this.
1.Check for TLS & Redirect
Use this guide to create the redirect: https://docs.fastly.com/guides/backend-servers/generating-http-redirects-at-the-edge
The condition for the above would use
Fastly-SSLto check whether the request is HTTP or HTTPS https://docs.fastly.com/guides/ssl/how-do-i-tell-if-this-is-an-ssl-request-or-not
Please NOTE: Users will still see the TLS error for this domain.
- Your other option would be to point your traffic away from TLS. You can accomplish this by changing your CNAME to an endpoint which doesn’t listen for TLS requests:
global-nossl.fastly.net.There is a billing implication to using our global datacenters, so please let us know if for example, you’re only utilizing our U.S. & E.U. PoPs, and we can give you an endpoint that matches your requirements. Requests can be sent to support@fastly.