Comment by musicale
16 hours ago
> "gatech.edu" really should be written as "gatech.edu."
https://www.gatech.edu./ does seem to work for me.
It is interesting that URLs often contain two hierarchies in opposite directions:
16 hours ago
> "gatech.edu" really should be written as "gatech.edu."
https://www.gatech.edu./ does seem to work for me.
It is interesting that URLs often contain two hierarchies in opposite directions:
Yeah of course adding the extra dot will work. The dot at the end simply means do not try to append the local search domain. Interestingly bad “security” software will often block domains without the trailing dot but permit the one with the trailing dot.
The problem of having two hierarchies in opposite directions means that it is advantageous to store it while reversing one of the hierarchies. I think the earliest Google Search backend used a format like org.myorg.something/something internally. This representation worked great for key-value storage systems where the keys are sorted.
Yes, that's how you're supposed to store URLs as keys in something like Cassandra.
Indeed, back in the 90s I remember trying to decide whether to do foo.bar.com or bar.com/foo for various subsites of my main domain back then.
What is your conclusion?
It’s thirty years later, so things have changed, but now I would be inclined to only use a different subdomain if it required a different server.
its not really two hierarchies, its just one written backwards for a while, and then forward.
if you reverse the backwards part you get
https://org.myorg.something./something/more/specific/
the dots separate computers or networks and the slashes separate folders.
well, more pedantically:
https://.org.myorg.something/something/more/specific/
you need the null-label on the left instead of the right.