[sclu1034]

From the user's point of view, yes, that is intended behavior. But the browser can't know that, all it sees is a dropped connection. For all it knows, there could be an actual issue with the network.

But unless you open the dev tools' network tab, you don't know about that request failing.

[NoZebra120vClip]

TCP RST is indeed considered a transient failure, and the RFCs specify that it should be retried several times before giving up.

My ad blocker returns "0.0.0.0" for A records, which in practice means attempts to connect to 127.0.0.1, which isn't running a server of any kind on port 443/tcp or 80/tcp. So a standards-compliant client would really hang awhile, or hold rendering, until several connects have been attempted and they all failed.