As promised last year, we have now rolled out a change where Chrome explicitly asks users for permission before making an insecure HTTP connection. Earlier this year we …
    • Voytrekk@sopuli.xyzEnglish
      4·
      23 hours ago

      It’s been an option in Firefox since about then. Chrome has been pretty slow to add https only modes. This is them changing it to https by default, which is probably for the best. There aren’t a ton of reasons to visit http sites unless you intend to, like something hosted locally.

      • shortwavesurfer@lemmy.zipEnglish
        1·
        1 hour ago

        About the only thing I’m aware of that’s still HTTP that a person would have a reason to visit would be their router’s webpage and even then something like a self-signed Tofu’s certificate would be fine for something like that.

        If == 192.168., 10.0. then tofu

      • Turret3857@infosec.pubEnglish
        1·
        23 hours ago

        I guess I havent used default chrome in a long while but i know for at least the past couple years ive gotten a warning popup in Ungoogled Chromium