I have a static website on ipfs. I’ve set up CNAME with ‘www.nftpolygon.com’ pointing to ‘cloudflare-ipfs.com’ (and setup the corresponding txt records). The nameservers are on Cloudflare. Https redirect on the SSL edge certificates tab is enabled.
The issue is that naked domain (without the www) and also ‘http://www.nftpolygon.com’ all open non-ssl connection.
Now, the interesting part is, I have another domain, nftcanvas.app, with exact same setup as above, with all the https redirects working perfectly. Screenshot of that is below.
The only difference between the two domains that I can think of is that one is .com, which is a cloudflare supported TLD and the other is .app, which is not a TLD that cloudflare supports. Maybe cloudflare does something different in these two cases.
I’m not sure why this is not needed for my other domain.
Anyway, the only url now that is not redirected to https is “http://www.nftpolygon.com”. My understanding is that this is because the www subdomain is handled by cloudflare-ipfs.com (via CNAME record) so it’s not proxied. Technically, because Cloudflare also manages the target url, I would expect them to be handle the redirect to https. But I’m not sure if this is solvable. This is not a big deal, but let me know if anyone solved this.
Got it - thanks for clarifying. That explains why the .app domain didn’t need page rules to force https.
Still curious if anyone figured out a way to force https on the www subdomain when it points to cloudflare-ipfs (i.e. forcing https in the ipfs scenario).
For now, having HTTPS forced is a custom configuration on Cloudflare side. If you are willing to enable HTTP to HTTPS redirection, please comment below with the domains you want it on.
