Re:Does “www.” Mean Better Transport Layer Security?
by zamadatix on Monday August 19, 2019 @08:26AM
(#20737110)
If you're just going to redirect www to . why not make it a CNAME instead of a hop?
[ Parent
| on HN ]
Re:Does “www.” Mean Better Transport Layer Security?
by simcop2387 on Monday August 19, 2019 @08:52AM
(#20737262)
CNAME in this case makes no difference vs an A/AAAA record. The HTTP side of things doesn't care what kind of DNS record it was, but will be affected by what the fqdn is, since it will affect cookie propagation and other security things in the browser.
Re:Does “www.” Mean Better Transport Layer Security?
by Avamander on Monday August 19, 2019 @08:43AM
(#20737196)
CNAME would just resolve `www.` as `.`. Browsers and search engines would still need to be instructed to use the non www. address.
Re:Does “www.” Mean Better Transport Layer Security?
by toast0 on Monday August 19, 2019 @03:14PM
(#20740837)
It's usually better not to have the same content at two urls. Whichever one you choose, the other should redirect to; or if you're picky like me, trying to go to the non-published one should send you to the home page on the other --- this reduces the tendency of others to link to the wrong form.