Timeline for Safari inserts "localhost" in URLs with three slashes after the scheme
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 16, 2022 at 17:42 | comment | added | Polygnome | The RFC simply doesn't apply to that field. As long as the browser correctly uses the protocol behind the curtain, there is no RFC violation. Assuming a technical specification is good UX is bad, that is why most browsers have an added layer of abstraction on top of it. | |
| Feb 16, 2022 at 17:41 | comment | added | Polygnome | Yes, and? That is the protocol the browser uses to talk to other programs. The browser should adhere to it when doing that. But the interaction with the user happens on a different OSI level. Hell, there are many web clients out there which completely hide the URI from the user and you can't even type any in. You assume the address bar of the browser must be an URI, that is definitely wrong. In chrome, can even type in math equations there and get a result, or a google query, or wikipedia query. | |
| Feb 16, 2022 at 17:34 | comment | added | mmmmmm | Becaus RFC7230 says at the top "This document provides an overview of HTTP architecture and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) scheme" and the slashes are part of the scheme. | |
| Feb 16, 2022 at 17:31 | comment | added | Polygnome | Why would the protocol -- which governs how a browser should communicate with a server -- dictate how the UI/UX -- the interaction between browser and user -- works? | |
| Feb 16, 2022 at 9:19 | history | answered | mmmmmm | CC BY-SA 4.0 |