5 ms·

Chrome to force .dev domains to HTTPS via preloaded HSTS

• stephenr 9y ago
  This is from September but maybe its posted again now because the change is/has shipp(ing/ed) to users? Personally, I prefer to go the other way and use a local environment subdomain with local stuff anyway (ie local.foo.company.com rather than foo.dev).
  • gmemstr 9y ago
    I noticed users on reddit reporting this was rolling out.
• mgor 9y ago
  I always use .local: https://en.m.wikipedia.org/wiki/.local https://en.m.wikipedia.org/wiki/.local
  • jwilk 9y ago
    Non-mobile link: https://en.wikipedia.org/wiki/.local https://en.wikipedia.org/wiki/.local
  • tinus_hn 9y ago
    So you use it while you know it is reserved for something else?
  • purephase 9y ago
    Could run into the same issue there as well. The only reserved tlds are: .localhost .example .invalid .test The rest are up for grabs. For the life of me, I can't figure out why .test would make the list and not .dev (or some equivalent) but it is what it is.
    • WorldMaker 9y ago
      Linked Wikipedia article points out towards the top that RFC 6762 reserves .local for mDNS (fka Zeroconf/Bonjour) multicast DNS lookups on a local area network. (Which is why you probably don't want to use .local for non-multicast DNS lookups as you may break mDNS applications.)
  • astrodust 9y ago
    .local is for mDNS. You're just asking for conflicts.
• jwilk 9y ago
  Previous discussion: https://news.ycombinator.com/item?id=15268701 https://news.ycombinator.com/item?id=15268701
• idooontcare 9y ago
  Chrome forcing anything sounds a bit scary. I hope google do not repeat Microsoft mistakes.. with this "forcing" ..