3 ms·
I bet Apple transitioning to https-only has played a huge role in this. Even as an iOS developer I think this move was too drastic when there are so many http b
by cocktailpeanuts 10y ago
I bet Apple transitioning to https-only has played a huge role in this. Even as an iOS developer I think this move was too drastic when there are so many http based websites out there. Nowadays when you build an app and even try to display a non-https image they don't render at all (unless you go through the trouble of customizing the security settings in the bundle, and even this is going to go away soon as far as I know)
- JoshTriplett 10y agoThere will always be "so many http-based websites out there", as long as there's no forcing function. I look forward to the point where browsers start flagging any use of http as insecure; there's a gradual transition in that direction. It won't take too long after that point for http to disappear completely, with some lingering use in specialized or un-upgradeable devices for a while. I think we're still missing one more ecosystem component to make such a transition successfully, though: free wildcard certificates through Let's Encrypt.
- mintplant 10y agoFirefox already marks sites loaded over HTTP with a red slash in the URL bar, at least on the current Aurora channel build.
- Buge 10y agoI thought that was only sites that have a password box on them.
- spikengineer 10y agoYeah. It's only when there is a password box on them or requests things like location, notifcations support etc.