I’ve never had an issue before using the SSL applied to the domain, using a custom domain name. My DNS is being managed elsewhere.
According to the SSL certificate check in Netlify’s control panel, the Let’s Encrypt has been successfully applied. However, It’s not redirecting to https. For example, if user types in mydomain.com, I’d it expect https not http. Or if user types in http://mydomain.com, I’d expect it to redirect to https://mydomain.com. Is there something else I need to set within Netlify, or some other record I need to add to my registrar?
HTTPS does work, but as I mentioned the problem is when visiting http://katinawilson.com or just katinawilson.com – it doesn’t redirect to https.
BTW, I’ve cleared my browser cache, and have tried in multiple browsers.
Hi, @djmtype. That is quite odd above. There is no x-nf-request-id header which is unusual. Also, I would recommend not testing with the curl option -I.
The -I option uses the HEAD method. You shouldn’t test the CDN using HEAD if you want to see how it will behave during real world use. It should be tested using GET (and using compression with the --compressed option) to see the real CDN behavior.
For example, these are the curl options I use in my own testing:
That is using a GET method above. Using that I see both the header X-Nf-Request-Id: 01GVPCH3GBVF42SPAYMW5WX727 and I also see the redirect to HTTPS. That x-nf-request-id header is a key piece of debugging information as it is unique to a single HTTP response and allows our support team to examine the path the request takes through our infrastructure.
@jasiqli, would you please try the command above and then share the output here? Note, that command above is using Unix/Linux syntax (MacOS is a Unix variant) so it may need to be modified if you are using Windows.
hi @djmtype glad to hear it is working for you. Excellent debugging skills @jasiqli you were incredibly helpful. SSL should be virtually immediate upon creation of a Netlify subdomain . SSL provisioning delays should only occur with custom domains due to DNS propagation (usually).