3 ms·
Potential source of frustration: naked domains on http that upgrade to https after redirect to www or some other subdomain. It’s a problem to me now - if I name
by asplake 6y ago
Potential source of frustration: naked domains on http that upgrade to https after redirect to www or some other subdomain. It’s a problem to me now - if I name my naked .org site in GMail it assumes https. At some point I will have to host my own redirection service, just for this one issue.
Side note: it beats me why browsers couldn’t agree a way to specify at least the first redirect in DNS, no web server needed for that part.
- CodesInChaos 6y agoYou'd need to authenticate that redirect, so it isn't as easy as it looks. (something like DANE and DNSSEC) The benefit doesn't seem big to me. You're already running a http server for the original domain, and an https server for the target domain, so extending the http server for the original domain to https doesn't sound like a big step.
- asplake 6y agoI'm using AWS Elastic Beanstalk, and you're not supposed to point a naked domain at the load balancer. On reflection though, it's a problem Amazon could solve there. None of this is super hard but it is annoying, some complexity that feels removable.