2 ms·
And people still fight "HTTPS everywhere"... Secure should be the default with insecure being left for special cases that need it.
by Klathmon 11y ago
And people still fight "HTTPS everywhere"...
Secure should be the default with insecure being left for special cases that need it.
- r3bl 11y agoIf by "HTTPS everywhere" you mean the browser extension, that isn't very helpful since a huge chunk of websites that have properly implemented HTTPS turn it on by default. If by "HTTPS everywhere" you mean enabling HTTPS on all websites, I could not agree more. In any case, I haven't heard of a single source fighting against this switch. Some sources please?
- Klathmon 11y agoI mean the latter. And it's generally random web developers who are against HTTPS on everything. Generally the reasons are: * Cost (this one is going away hopefully) * Performance (tls is too slow!) * CPU/Memory overhead on the server * What they are showing doesn't need to be secured anyway. I don't really agree with any of those points, but that is what I hear when I bring it up.