puma-dev: Chrome 63 breaks .dev without SSL

I’m sure plenty of us read about this already, but in case you’re a little late to the party…

https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/

Should/can puma-dev be changed to default to something like .localhost since .dev is essentially dead?

Fixing this for me as was easy as killing puma-dev in Activity Monitor, then…

puma-dev -install -d localhost

Just like the instructions demonstrate using pdev.

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 8
Comments: 21 (2 by maintainers)

Most upvoted comments

FYI pow switched from .dev to .test: https://github.com/basecamp/pow/pull/547.

jeromedalbert on Dec 18, 2017

This could easily be bikeshedded into oblivion. If .test is becoming the de facto standard, that seems like a good way to go in the interest of getting a new safe, usable default into the world.

subvertallchris on Feb 5, 2018

I’ve just started using Firefox Developer Edition because of this issue.

nyjt on Dec 12, 2017

Is there any workaround to make Chrome just work? I’ve been using .dev for many years, don’t want to switch everything to localhost or test just because of Googles whims…

JustinAiken on Dec 9, 2017

It looks like that .app domain is also affected. Redirecting me to https://

robertmiekwicz on Dec 19, 2017