Can a URL Record Redirect Requests Over SSL?
No. Our redirector service can only redirect non-HTTPS requests.
It’s not possible to use the URL record to redirect the www to the non-www version of your domain with HTTPS. You can redirect
http://www.example.com but not
This table shows a list of most common redirect options and whether they’re supported by the redirector:
|http://example.com||http://www.example.com||YES||Redirect a host name to another URL|
|http://example.com||https://www.example.com||YES||Redirect a host name to another HTTPS URL|
|http://example.com||https://example.com||NO||Redirect a host name to the same host name, but HTTPS|
|https://example.com||https://www.example.com||NO||Redirect a host name via HTTPS|
URL forwarding isn’t really a DNS record type. It produces an A record that points to an HTTP server. The HTTP server is responsible for issuing the 301 redirect when it receives HTTP requests.
For an HTTP server to respond to HTTPS requests for your domain, the redirector would need to have your SSL certificate and private key installed on the redirector server, since it’s the HTTP server that negotiates the SSL connection. It’s impractical to have a shared URL forwarding service that would allow you to upload your SSL certificate and private key.
Instead of using a URL record to redirect requests, you can use an ALIAS record, A record, or CNAME record to point both the redirecting domain and the target domain to your application, then handle a redirect in your HTTP server or inside your application.