4 ms·
Why can't they add a new URL scheme "secure://" to Chrome that will only support HTTPS? Adding a new scheme would support all existing https websites on the in
by peterwwillis 9y ago
Why can't they add a new URL scheme "secure://" to Chrome that will only support HTTPS?
Adding a new scheme would support all existing https websites on the internet today with no need to pay anyone money or rush to reserve domains.
This .app thing is needlessly difficult, and just a way for Google to push its brand on technology concepts en-masse, like the .dev fiasco. Now everyone in the world has to register a new domain (and make it work for their site) to make sure their URL is always secure.
- SahAssar 9y agoHow would "secure://" differ from "https://" https://"?
- peterwwillis 9y agoMost people don't know what https:// https:// means, and is often confused with http:// http://. Plus, https:// https:// has allowed people to do things like click through certificate warnings, which secure:// should never do. Finally, secure:// should require all standard best practices for the security of web apps, first simply by refusing to render obviously insecure sites, and then by requiring extra parameters.