3 ms·
Define HTTPS. SSL? TLS? Which version? The oldest "safe" version is TLS 1.2, which only gained browser support late 2013, so 7 years ago. The article recommen
by pianom4n 6y ago
Define HTTPS. SSL? TLS? Which version?
The oldest "safe" version is TLS 1.2, which only gained browser support late 2013, so 7 years ago.
The article recommends not using the older unsafe versions for the sake of older browsers.
- SulfurHexaFluri 6y agoIMO its reasonable to require that users have close to the most up to date software that their devices support. So its fine to kill off browser support after a year as long as the site can still be accessed on a 10 year old bit of hardware.
- AnIdiotOnTheNet 6y ago1 year? Jesus christ. You know, in other industries things are routinely supported for decades. It is a good thing large chunks of actually essential infrastructure aren't designed by web people.
- SulfurHexaFluri 6y agoIts really not acceptable to be using a web browser 1 year behind on security updates. Especially since almost everyone is using an auto updating browser now. Once a feature has been out on all major browsers for a year than its fair game to use. Its also not wasting your time trying to develop a modern web app which has support for netscape navigator. Going off the usage stats of the site I work on, almost everyone is on the latest version of their browser and the ones that are not always end up upgrading after a warning notice is sent out about old borwsers.
- throwaway201103 6y agoYour web app should basically work (at least essential functionality) on something like lynx as that is a decent proxy for screen readers or other accessibility aids. You'll be looking at ADA complaints if you don't.