On 1/24/21 3:21 AM, Tim via users wrote:
On Sun, 2021-01-24 at 00:07 -0700, Joe Zeff wrote:
Or, you do the sensible thing and point said domain to 127.0.0.1, so that it times out almost instantly.
It doesn't. The web browser waits for something to answer it. Go on, try to get your web browser to connect to a non-existent server, it doesn't immediately stop looking. If you load up a page that might try waiting for a dozen different things before it will proceed and let you read something, it's a pain.
That's why you don't use a non-existent server. localhost exists, so you get an immediate rejection.
And, in my case, I do have a local webserver running.
That could be a problem. It depends on if it answers to only 127.0.0.1 or any localhost IP.