Valet: Use .test instead of .dev as default development domain

[rensverschuren]

Since .dev is an official Top Level Domain it should not be used for local development. Also, Chrome will force https on these domains in the future:

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

Valet should adopt .test or another domain for special use cases:

https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml

[freddyheppell]

For now it's possible to switch Valet to using .test by running valet domain test, but this should be the default really.

[adamwathan]

Happy to accept a PR for this, I think we'll do .localhost rather than .test though.

[drbyte]

Just pointing out that PR #436 is in progress to address this.

[gayansanjeewa]

Sad that we have to drop .dev. .localhost or .test are not cool enough as .dev

[curtisblackwell]

Has anyone discovered a TLD working in Chrome Canary?

After .dev stopped working, I switched to .app which worked for about a week. Now nothing seems to work (including .test and .localhost). They all just perform a Google search.

Using .app in conjunction with Browsersync accessing at localhost:3000 is still working somehow, but after redirects, it goes to the URL in my .env, which just displays a ERR_CONNECTION_REFUSED error.

[drbyte]

They all just perform a Google search.

To get around that I just add http:// or https:// the first time, and then it seems to be fine after that.

[adamwathan]

@curtisblackwell Like @drbyte said, you can add the protocol to the beginning to make sure Chrome knows you are trying to resolve an address, or you can also add a trailing slash, like my-project.test/

[ctf0]

app for some reason stopped working today, so using .test will lead into a search but then chrome will show a small bar at top asking did you mean http://bla.test/.

so as @adamwathan said, simply add / to the end will fix the issue "for now"

[DCzajkowski]

Can be closed

[vrajroham]

.app again stopped working and .test leads to google search. @ctf0 adding / at end also won't fixes it.

[adamwathan]

Trailing slash should fix it but if not add the protocol to the beginning,
like http://myproject.test
On Sat, Dec 16, 2017 at 9:40 AM Vaibhavraj Roham [e-mail]
wrote:

.app again stopped working and .test leads to google search. @ctf0
https://github.com/ctf0 adding / at end also won't fixes it.

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/laravel/valet/issues/433#issuecomment-352187439, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEH3bHVtULC0biMrTWQwLfYBrhp3Pemaks5tA9ZagaJpZM4PaF93
.

[timbeadle]

.app again stopped working

.app is a gTLD as well, also registered by Google, and not released for public use.

[bobtherobot]

I switched from .dev to .ved because it's therapy for my dyslexic brain. And I like 3 letter TDLs.

[ptisinge]

How annoying is this! Took me forever to find this out. I just thought valet had stopped working.

[jashirouprotips]

@ptisinge I've just read a note when mention this issue for us as developers....hahahaha and I was fighting whit my localhost weeks ago to run "HTTPS" with my own SSL Certificate, and when I finally run the SSL - HTTPS the "Add Exception..." button doesn't appear to run this. 😆 🤣

[teslimni]

It's annoying. But I discovered when you're offline, the test tld works without problem.