Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use .test instead of .dev as default development domain #433

Closed
rensverschuren opened this issue Sep 17, 2017 · 16 comments
Closed

Use .test instead of .dev as default development domain #433

rensverschuren opened this issue Sep 17, 2017 · 16 comments

Comments

@rensverschuren
Copy link

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
Copy link

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

@adamwathan
Copy link
Contributor

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

@drbyte
Copy link
Contributor

drbyte commented Sep 18, 2017

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

@gayansanjeewa
Copy link

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

@curtisblackwell
Copy link

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
Copy link
Contributor

drbyte commented Oct 17, 2017

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
Copy link
Contributor

@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
Copy link

ctf0 commented Dec 9, 2017

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
Copy link

Can be closed

@vrajroham
Copy link

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

@adamwathan
Copy link
Contributor

adamwathan commented Dec 16, 2017 via email

@timbeadle
Copy link

.app again stopped working

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

@bobtherobot
Copy link

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

@ptisinge
Copy link

ptisinge commented Mar 17, 2018

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

@jashirouprotips
Copy link

@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
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests