11-09-2020, 04:23 PM
(This post was last modified: 11-09-2020, 04:31 PM by BronzeBeard.)
jed and fsflover,
Bullet point arguments in favor of allowing HTTP are included in post #11, if you care to read the entire thread before rehashing the same arguments others have already made. Rebuttles to common cited reasons for removing HTTP from everywhere is in post #13.
In short, it's the user's responsibility to use HTTPS. If the user is too stupid to do that, then it's Firefox and Chrome's fault. Websites shouldn't be redirecting your protocol. Your browser should check if HTTPS exists and default to that. Sadly, the popular browsers require a plugin for that functionality.
Content providers should provide their content in any reasonable format they deem cost effective. In HTTP and HTTPS' case, there isn't any administrative costs. Refer to post #11 for reasons why HTTP is still a valid choice for some users.
Bullet point arguments in favor of allowing HTTP are included in post #11, if you care to read the entire thread before rehashing the same arguments others have already made. Rebuttles to common cited reasons for removing HTTP from everywhere is in post #13.
In short, it's the user's responsibility to use HTTPS. If the user is too stupid to do that, then it's Firefox and Chrome's fault. Websites shouldn't be redirecting your protocol. Your browser should check if HTTPS exists and default to that. Sadly, the popular browsers require a plugin for that functionality.
Content providers should provide their content in any reasonable format they deem cost effective. In HTTP and HTTPS' case, there isn't any administrative costs. Refer to post #11 for reasons why HTTP is still a valid choice for some users.
