Towards HTTPS by default
blog.chromium.org
For the past several years, more than 90% of Chrome users' navigations have been to HTTPS sites, across all major platforms. Thankfully, th...

cross-posted from: https://lemmy.world/post/3301227

Chrome will be experimenting with defaulting to https:// if the site supports it, even when an http:// link is used and will warn about downloads from insecure sources for “high-risk files” (example given is an exe). They’re also planning on enabling it by default for Incognito Mode and “sites that Chrome knows you typically access over HTTPS”.

  • Buddahriffic@lemmy.worldEnglish
    264·
    1 year ago

    Is this just general advice? If so, I agree, but if it’s specific to this, what’s the problem you see with it?

      • Buddahriffic@lemmy.worldEnglish
        8·
        1 year ago

        Agreed, but to clarify, I was asking if there was an issue with this specific change (always using https if it’s available even if the URL uses http), as it does seem to be a positive that makes me wonder why it’s only happening now.

    • the_q@lemmy.worldEnglish
      131·
      1 year ago

      It is general advice, but https should have been the default for a good while.

    • gravitas_deficiency@sh.itjust.worksEnglish
      82·
      1 year ago

      If we have to pick just one reason: WEI. As someone who’s been a professional software engineer for a decade and a half, this has the potential to mutate and ruin the internet at large in ways we’re only beginning to fully explore and understand.