3 ms·
google.com could even be QUIC which could be any UDP port but in most cases is 443. That information isn't displayed either. Not to mention the difference of ht
by Avamander 7y ago
google.com could even be QUIC which could be any UDP port but in most cases is 443. That information isn't displayed either. Not to mention the difference of http1, http1.1, http2, quic, shouldn't the all be displayed if we really care about displaying the protocol?
- zAy0LfpBZLC8mAC 7y agoThe protocol is irrelevant. The identity is what this is about. URIs identify resources, and conflating different URIs is violating the relevant standards.
- Avamander 7y agoIt's hiding though, not conflating, it isn't violating any standard. Not to mention, how is a protocol irrelevant but a "www." subdomain isn't? Both are equally useless for most users when browsing.
- zAy0LfpBZLC8mAC 7y ago> It's hiding though, not conflating, it isn't violating any standard. By doing what? > Not to mention, how is a protocol irrelevant but a "www." subdomain isn't? Because the "www." hostname is part of the identity, the protocol is not (if we are talking about HTTP/1.x vs. HTTP/2 or QUIC--HTTP vs. HTTPS is part of the identity, of course). > Both are equally useless for most users when browsing. That's irrelevant. It still is part of the identity of the document.