On 25/01/2021 11:52, Tim via users wrote:
Tim:
>> 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.
Samuel Sieb:
> That's why you don't use a non-existent server. localhost exists,
> so you get an immediate rejection.
You can only get an immediate*rejection* if there's something there to
reject it.
Really? I just told my browser to connect to
https://127.0.5.6/ and it came back
immediately
with...
This site can’t be reached
127.0.5.6 refused to connect.
Am I missing something?
--
The key to getting good answers is to ask good questions.