4 ms·
In what way are they a broken concept? What justification is there for serving HTTPS in a way users can't expect to consume?
by ivanbakel 7y ago
In what way are they a broken concept? What justification is there for serving HTTPS in a way users can't expect to consume?
- tych0 7y agoIf you don't serve the same content on :80 and :443. For example, you might be running a Tor relay node which would serve the node directory list on :443 to help people bypass firewalls, but also be using it as a useful and legitimate web server in order to prevent organizations from blocking it wholesale.
- Lex-2008 7y agoSomebody might prefer using http for public stuff (reading blog posts), https for private (editing them).
- q3k 7y ago> In what way are they a broken concept? Because it's blindly following an inadequate heuristic, and not gracefully degrading if it fails - instead, you get comments like these blaming the author. Even though the author never wanted you to use HTTPS in the first place. > What justification is there for serving HTTPS in a way users can't expect to consume? Plenty of technical reasons (eg. what the sibling comments mentioned), but most importantly: there's no Internet/Web standard that I'm aware of which would prohibit me from doing so.