3 ms·

How would "secure://" differ from "https://" https://"?

• peterwwillis 9y ago
  Most 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.