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

switch to another tld #61

Closed
alexanderadam opened this issue Sep 26, 2017 · 2 comments
Closed

switch to another tld #61

alexanderadam opened this issue Sep 26, 2017 · 2 comments

Comments

@alexanderadam
Copy link

alexanderadam commented Sep 26, 2017

It seems that .dev is an official gTLD and Chrome will soon force https if I understood this correctly.

So it might be be to switch to another tld (alone to avoid conflicts).

EDIT: here is another good article that explains the topic a bit better and recommends .localhost, .invalid and .test and .example more or less for different purposes. But I guess in the end it doesn't matter and depends on personal taste.

@ysbaddaden
Copy link
Owner

ysbaddaden commented Sep 26, 2017

Yeah, I guess :(

Prax handles other TLDs transparently, so we may use .localhost or configure dnsmasq to resolve *.test as 127.0.0.1 as well as *.localhost to 127.0.0.1 (it doesn't hurt); sadly .hostname.local won't resolve subdomains.

We should change the default .dev to either one, thought.

BTW: chrome won't consider myapp.test or myapp.localhost as URL and will issue a search by default, despite their bundled DNS resolver resolving .localhost as 127.0.0.1 by itself. We must specify http://myapp.test or myapp.test/... seriously, they **** big time.

@jacksonrayhamilton
Copy link
Contributor

A bug has been filed for the ".test"/".localhost" URL bar searching behavior: https://bugs.chromium.org/p/chromium/issues/detail?id=794001

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

3 participants