3 ms·

>> Https is better, but there are still valuable use cases for unencrypted web traffic. > Like what? Things like this: https://utcc.utoronto.ca/~cks/space/blo

• Cyphase 9y ago
  Let's take it as given that HTTP is the right answer in that situation; I'm not saying it is or isn't, but let's assume it is. We're talking about HTTP(S) in web browsers and client-side applications; no one is actually talking about _banning_ HTTP, e.g. blocking port 80 or filtering via deep packet inspection. If you have a use case where after careful thought you decide that HTTP is better than HTTPS, then fine. But HTTPS should be the default.
  • droopybuns 9y ago
    The functional result for the chrome browser’s ui warnings will be almost indistinguishable from banning http.
    • Cyphase 9y ago
      For web sites and web browsers, sure. But if you want to use HTTP for your BIOS updates (dozzie's example), then go ahead; I don't think anyone is seriously proposing to stop you. Just please make sure that it's done securely. Anyway, TLS is not enough for secure updates.