15 Jun
2022
15 Jun
'22
7:53 a.m.
Yes, tuhs.org:80 &443 could permanently redirect to www.tuhs.org so
browsers update to the full canonical name (assuming that's the desired
name).
Though I think Norman was drawing an analogy between A-records/hard links
and CNAME/symlinks, then observing that prior to 4.2BSD in 1983 there were
no symlinks only hard links, ditto CNAMEs in RFC-882, also 1983.
So if we're going back further, we shouldn't use them (it breaks down a
little when considering A-records though, since we can't easily not use
those!)
On Tue, 14 Jun 2022, 00:44 Michael Kjörling, <michael(a)kjorling.se> wrote:
On 13 Jun 2022 11:49 -0400, from norman(a)oclsc.org
(Norman Wilson):
Surely a site that aims to collect information should have a single
canonical name, not multiple ones that lead to the same content on the
same host.
I would suggest to pick either www.tuhs.org or tuhs.org as the HTTP
hostname, and make the other redirect to the first (or remove HTTP
service from the not-chosen one entirely) only so as to not break
existing links from elsewhere.
--
Michael Kjörling • https://michael.kjorling.se • michael(a)kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
Maybe
make www.tuhs.org a CNAME for tuhs.org?
Surely a site devoted to the history of UNIX should use a
real link, not a symbolic one.