4 ms·

This is great and all until you (like me) need to be able to differentiate www.example.com from example.com and https:// https:// example.com versus http:// htt

This is great and all until you (like me) need to be able to differentiate www.example.com from example.com and https:// https:// example.com versus http:// http:// example.com. My website doesn't forward example.com to www.example.com (due to errors on my part that I don't know how to fix, my email is in my profile and if you can help I'd greatly appreciate it). I don't know if there are any scenarios in which a properly-configured website (mine isn't) needs to differentiate example.com from www.example.com. But I liked the ability to do so easily.

notatoad 7y ago
>need to be able to differentiate ... https:// https:// example.com versus http:// http:// example.com this requirement is handled by the "not secure" badging, which is much more obvious that requiring users to pick out the "s" in the middle of a string. https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html https://security.googleblog.com/2016/09/moving-towards-more-...
jammygit 7y ago
Can you just set a CNAME record in your DNS settings for that redirect?
JorgeGT 7y ago
Based on your certificate, are you using Cloudflare? If so, this shows how to handle these redirects: https://www.bybe.net/cloudflare-enforce-ssl-redirect-http-https/ https://www.bybe.net/cloudflare-enforce-ssl-redirect-http-ht... I use Github pages+Cloudflare to host my page and that's how I do it, free and quite resilient.
UncleMeat 7y ago
HTTP headers are hidden. That's great and all until you need to examine them for some development task. iframe URLs are hidden. That's great and all until you need to verify that your iframe is loading the correct content. Yet people don't complain about these. They are happy using the dev tools to access this information that is sometimes useful for developers and almost entirely useless for ordinary users.

notatoad 7y ago

>need to be able to differentiate ... https:// https:// example.com versus http:// http:// example.com this requirement is handled by the "not secure" badging, which is much more obvious that requiring users to pick out the "s" in the middle of a string. https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html https://security.googleblog.com/2016/09/moving-towards-more-...

jammygit 7y ago

Can you just set a CNAME record in your DNS settings for that redirect?

JorgeGT 7y ago

Based on your certificate, are you using Cloudflare? If so, this shows how to handle these redirects: https://www.bybe.net/cloudflare-enforce-ssl-redirect-http-https/ https://www.bybe.net/cloudflare-enforce-ssl-redirect-http-ht... I use Github pages+Cloudflare to host my page and that's how I do it, free and quite resilient.

UncleMeat 7y ago

HTTP headers are hidden. That's great and all until you need to examine them for some development task. iframe URLs are hidden. That's great and all until you need to verify that your iframe is loading the correct content. Yet people don't complain about these. They are happy using the dev tools to access this information that is sometimes useful for developers and almost entirely useless for ordinary users.