XPost: alt.comp.software.firefox, alt.comp.os.windows-10   
   From: V@nguard.LH   
      
   "Carlos E.R."  wrote:   
      
   > Incubus wrote:   
   >   
   >> Nil  wrote:   
   >>   
   >>> How about HTTPS-Only Mode, under Privacy & Security?   
   >>>   
   >>> HTTPS provides a secure, encrypted connection between Firefox and the   
   >>> websites you visit. Most websites support HTTPS, and if HTTPS-Only   
   >>> Mode is enabled, then Firefox will upgrade all connections to HTTPS.   
   >>>   
   >>> [ ] Enable HTTPS-Only Mode in all windows   (Manage Exceptions...)   
   >>> [ ] Enable HTTPS-Only Mode in private windows only   
   >>> [x] Don't enable HTTPS-Only Mode   
   >>   
   >> When I did that the strange thing is I was able to get, momentarily,   
   >> a log in into the router but then it reverted instantly back to   
   >> wanting https! https://i.postimg.cc/5tNdmWVZ/Screenshot-49.png   
   >   
   > That's because the router itself supports https and has a certificate   
   > for it. It is the router itself who is insisting on https.   
      
   In that screenshot-49.png, notice the crossed-out padlock in the address   
   bar.  The router does not have a site certificate for its internal web   
   server, so the router cannot use HTTPS.  The user is connecting via   
   HTTP, and why the cross-out padlock appears to warn HTTPS is *not* being   
   used.   
      
   The router is an intranet host of the OP's network.  Why would it need   
   to use HTTPS?  Also, Firefox cannot upgrade a connection to HTTPS if the   
   site does not support it.  All Firefox is doing is checking if an HTTPS   
   connect is allowed when the user instead specified HTTP.  For sites that   
   do support HTTPS, they [should] redirect an HTTP connect to an HTTPS web   
   page, so Firefox's HTTPS-Only Mode is redundant (and can interfere with   
   the programmed navigation at the site).   
      
   The pic shows HTTPS was not used when getting the start.htm web page in   
   the router's internal web server.  The OP's screenshot shows HTTPS was   
   *not* used to connect to the start.htm web page in the router.  The OP   
   said the router reverted to wanting HTTPS, but didn't show a pic of that   
   router's web page or mention the URL.  Did the OP get to start.htm okay   
   using HTTP, and then the same page refreshed trying to use HTTPS, and   
   Firefox then displayed an error page?  The OP shows he got to start.htm   
   in his router's web server.  Where's the info on what happened for the   
   "revert" to HTTPS?   
      
   The cross-out padlock icon in the address will always be shown when   
   connecting to an HTTP web document.  It's to alert you that the   
   connection is not secure, not that the connection failed.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)