Timeline for Is it safe to use HTTP if no sensitive information is being transmitted?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 30 at 0:49 | comment | added | security_paranoid | Times change quickly with cybersec. | |
| Aug 30 at 0:49 | comment | added | security_paranoid |
Yeah, that’s true. In fact, on another level entirely, it may be that in the near future, HTTP without the S might be illegal…
|
|
| Aug 30 at 0:02 | comment | added | Ja1024 | @security_paranoid: At least Firefox and Chrome now always use HTTPS by default, and if only HTTP is available, they put up an entire warning page that must be actively closed to proceed. With HSTS (preloading or not), it's not even possible to get past the warning. Browser vendors cannot do much more without breaking parts of the WWW. | |
| Aug 29 at 23:48 | comment | added | security_paranoid | Thanks, this is what I had expected. I still think that it's funny that modern browsers even allow users to visit sites with unencrypted connections, seeing as most people don't know the risk. And not to mention that browsers only warn users about not to enter information such as credit card details, and don't even bother warning users about the several points you've listed above. | |
| Aug 29 at 23:27 | history | answered | Ja1024 | CC BY-SA 4.0 |