this post was submitted on 16 Aug 2023
85 points (90.5% liked)

Technology

60024 readers
3593 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago
MODERATORS
L3s
[email protected]
[email protected]
L4s
enu
85
Chromium Blog: Towards HTTPS by default (blog.chromium.org)
submitted 1 year ago by Spotlight7573 to c/technology
30 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
[–] [email protected] 8 points 1 year ago (1 children)

I agree. That would be absurd.

However, I don't like not having the option of using HTTP if I want to use it. It's okay if the webserver redirects me, but I don't like if my browser does it when I didn't tell it to. I might want this when doing development, port tunneling, VPN stuff, etc. In most cases, it won't matter, but when it does, it will be a pain in the ass.

[–] [email protected] 4 points 1 year ago (1 children)

Imagine you want to test your redirect from 80 to 443 when setting up your webserver.

While I think for the normal user this enhances security by defaulting to HTTPS, however this makes no sense for a browser. This should be enforced server side, the browser is for browsing, i.e. viewing. Not controlling and competing with the server software for competency.

Chromium is really leaning into bad code practice with the disregard for "separation of concerns".

[–] Spotlight7573 2 points 1 year ago

If it's enforced server-side, then there's still an initial connection that is unsecured and can potentially be intercepted/modified before it gets to the redirect from 80 to 443.