4 ms·
so this is not like the URL that would be typed into a browser? like this sort of thing: https://www.webopedia.com/TERM/U/URL.html https://www.webopedia.com/T
by RouterRooter 8y ago
so this is not like the URL that would be typed into a browser?
like this sort of thing:
https://www.webopedia.com/TERM/U/URL.html https://www.webopedia.com/TERM/U/URL.html
- naniwaduni 8y agoThis is a URL: https://news.ycombinator.com/item?id=18995045 We'd look for it on port 443, not 80. This is also a URL: mailto:example@example.org?subject=This%20is%20an%20example&body=This%20is%20a%20continuation%20of%20the%20example. There are a bunch of ports that might be used in the course of handling it, but most of them aren't port 80. URLs are a quite general concept that don't necessarily even require networking: data:text/plain;base64,SGVsbG8sIFdvcmxkIQ
- RouterRooter 8y agoyess port 443 for a https address, and port 80 for an http address. The impression i immediately had was that windows 10 system settings of an individual machine could be reached, across the web , using a URL just like any webbrowser and server normally would operate.
- WorldMaker 8y agoThese URLs use a custom protocol handler that is only registered on that machine and is never exposed externally. It's the same technique that is used in every operating system these days to handle application-specific URLs, such as the exact same way that most iOS and Android apps launch each other. There's no "server", it's just Windows looking up "Does any application handle `ms-settings:`? Oh yes, this one is registered to do that." and then passing on whatever information was provided after the colon to that app's startup handler. URLs are the modern CLI. It's not a secret.