curiously
"slashdot.org." redirects to "slashdot.slashdot.org"
curiouser and curiouser, "slashdot.slashdot.org." redirects to "slashdot.slashdot.slashdot.org"
and so on... =)
The danger of the trailing dot in the domain name
71–75 of 75 posts
Re: The danger of the trailing dot in the domain name
#72Earlier quoted context omitted.
Not the same thing, really, since domains are reversed compared to file paths. In domains, the root token is optional and assumed; like if 'home/user' meant the same thing as '/home/user'.
Well, reverse the path then. "news.ycombinator.com." is equivalent to "/com/ycombinator/news", but more commonly we use "news.ycombinator.com", equivalent to "com/ycombinator/news". The root token is not optional and assumed at all. Instead, there are multiple "search paths", like with binaries on *nix and Windows/DOS. Now, usually, it will check "." ("/") somewhere along the way, but people often have intranet domai…
That doesn't make sense. In filesystem-land /com/ycombinator/news is not equivalent to com/ycombinator/news. The latter depends on your current location in the filesystem, while the former does not.
The search domains vs. search paths comparison is interesting, but I'd argue not equivalent either. Filesystem search paths only apply to binary executables, for one thing. On unix-like systems, at least, it is recommended that you do not have '.' in your search path. Regardless, there isn't really a "default" search path. If it's empty, you get nothing, and you'll be unable to execute anything without specifying a path. If your search domain list is empty, you still get the default, which is the root.
I guess you can draw some parallels here and there, but it feels a bit forced to me.
Re: The danger of the trailing dot in the domain name
#73Earlier quoted context omitted.
Well, reverse the path then. "news.ycombinator.com." is equivalent to "/com/ycombinator/news", but more commonly we use "news.ycombinator.com", equivalent to "com/ycombinator/news". The root token is not optional and assumed at all. Instead, there are multiple "search paths", like with binaries on *nix and Windows/DOS. Now, usually, it will check "." ("/") somewhere along the way, but people often have intranet domai…
That doesn't make sense. In filesystem-land /com/ycombinator/news is not equivalent to com/ycombinator/news. The latter depends on your current location in the filesystem, while the former does not. The search domains vs. search paths comparison is interesting, but I'd argue not equivalent either. Filesystem search paths only apply to binary executables, for one thing. On unix-like systems, at least, it is recommende…
Sure, it's like both in some ways but also quite unlike both in other ways.
Re: The danger of the trailing dot in the domain name
#74Soooo does anyone have any reason to believe this matters in the wild?
I like the article it's interesting though, but to me it seems purely theoretical.
Re: The danger of the trailing dot in the domain name
#75Earlier quoted context omitted.
What does IIS have to do with the UI, exactly? It's just a web server.
The site's UI is simple and yet the server still can't handle it perhaps was the implication.
I'm not seeing a direct connection between UI simplicity and server capability. I can serve a hideously complex UI with a very minimal demand on the server. Demand on the server is much more about actual traffic, not the UI being rendered in the browser.