Skip to content

use .test instead of .dev as development domain #8567

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

Merged
merged 1 commit into from
Nov 2, 2017
Merged

use .test instead of .dev as development domain #8567

merged 1 commit into from
Nov 2, 2017

Conversation

snoek09
Copy link

@snoek09 snoek09 commented Oct 30, 2017

Since .dev is an official Top Level Domain it should not be used for local development.
Also, Chrome forces https on these domains.

Since .dev is an official Top Level Domain it should not be used for local development.
Also, Chrome forces https on these domains.
@javiereguiluz
Copy link
Member

I've discussed this issue privately with some community members. It's true that .dev is problematic because it belongs to Google and Chrome does undesirable things with it ... but .test doesn't feel 100% right.

@wouterj
Copy link
Member

wouterj commented Oct 30, 2017

This used to be .dev as, at the time of writing this docs, the official Homestead docs used .dev as well.

Meanwhile, the TLD used in the official docs was changed a couple time (e.g. .app, .localhost laravel/homestead#674 and .test laravel/homestead#697 ).

According to RFC 2606, these TLDs are reserved:

To safely satisfy these needs, four domain names are reserved as
listed and described below.

               .test
            .example
            .invalid
          .localhost

  ".test" is recommended for use in testing of current or new DNS
  related code.

  ".example" is recommended for use in documentation or as examples.

  ".invalid" is intended for use in online construction of domain
  names that are sure to be invalid and which it is obvious at a
  glance are invalid.

  The ".localhost" TLD has traditionally been statically defined in
  host DNS implementations as having an A record pointing to the
  loop back IP address and is reserved for such use.  Any other use
  would conflict with widely deployed code which assumes this use.

As MacOS does the loopback to 127.0.0.1 as described in the final paragraph, it is unusable for Homestead. .example and .invalid don't seem to be correct for these cases, as it's focused on documentation purposes.

To make a long story short: Big 👍 for using .test, which is also in sync with the current official Homestead docs.

@javiereguiluz
Copy link
Member

javiereguiluz commented Oct 30, 2017

It's "funny" that the right one (.localhost) doesn't work as expected ... and the one which works (.test) is "the wrong one" because it's intended for DNS testing 😲

@wouterj
Copy link
Member

wouterj commented Oct 30, 2017

Well, .localhost is only good for localhost running sites. In this case, it's not a localhost but a virtual Homestead host running your site, so .localhost isn't the good one. Actually, there is no real good TLD for this purpose...

@weaverryan
Copy link
Member

Thanks Henry!

@weaverryan weaverryan merged commit 7cd40bf into symfony:2.7 Nov 2, 2017
weaverryan added a commit that referenced this pull request Nov 2, 2017
This PR was merged into the 2.7 branch.

Discussion
----------

use .test instead of .dev as development domain

Since `.dev` is an official Top Level Domain it should not be used for local development.
Also, Chrome forces https on these domains.

Commits
-------

7cd40bf use .test instead of .dev as development domain
@snoek09 snoek09 deleted the use-test-instead-of-dev-as-development-domain branch November 2, 2017 08:04
@xabbuh xabbuh added this to the 2.7 milestone Nov 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants