84
Chromium Blog: Towards HTTPS by default (blog.chromium.org)
submitted 3 years ago by to c/technology@lemmy.world
32 comments fedilink hide all child comments
 

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".

you are viewing a single comment's thread
view the rest of the comments
[–] 19 points 3 years ago (1 child)

Pushing traffic to https isn’t the worst thing. My ask would be to have a toggle to disable due to local development or server deployments where http/port 80 is the only choice.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 10 points 3 years ago (2 children)

    It does specifically say "defaulting to https:// if the site supports it", so I think specifying http will still work if the site doesn't actually support https.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 3 years ago*

    No testing a server side http-to-https upgrade/redirect without reconfiguring your browser. This seems like an unnecessary and bad idea.

    This could be easily done better by promoting such server-side configurations as a default.

    I mean, why should the browser attempt to correct inappropriately configured servers? Shouldn't they rather be making PRs to NGINX/Apache/CAs or whatever?

    Also: can't this be exploited to spoof an unavailable HTTPS and coerce an unencrypted connection?

  • permalink
  • fedilink
  • source
  • parent