Answers.Body: <p>This seems missing from the other answers, so I feel the need to emphasize it here...</p>
  
  <p><strong>Craft does not require .dev for local development.</strong></p>
  
  <p>Your local URL can be anything you want, Craft does not care. There is no requirement whatsoever on using a <code>.dev</code> domain. That being said, it is recommended that you use a <a href="https://craftcms.com/support/license-enforcement#how-do-we-determine-craft-is-running-on-a-public-domain" rel="nofollow noreferrer">"dev-sounding"</a> URL, in order to avoid the licensing nag warning. And even if you're getting the warning, it won't have any negative impact on the capabilities your site.</p>
  
  <p>The other answers already address what to do if you <em>do</em> use a <code>.dev</code> URL, so I won't cover it here. You may also want to read <a href="https://craftcms.stackexchange.com/a/23193/45">this helpful answer</a> on a related question.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-11T21:33:25.387Z
Answers.LastActivityDate: 2018-01-11T21:33:25.387Z
Answers.UserDisplayName: Lindsey D
Answers.Body: <p>Yea Google bought .dev a few years back and now chrome forces https on all .dev domains.  I switched to using .test which has been reserved.  So far, so good.</p>
  
  <p><a href="https://medium.engineering/use-a-dev-domain-not-anymore-95219778e6fd" rel="nofollow noreferrer">https://medium.engineering/use-a-dev-domain-not-anymore-95219778e6fd</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-11T16:49:47.093Z
Answers.LastActivityDate: 2018-01-11T16:49:47.093Z
Answers.UserDisplayName: sgtpenguin
Answers.Body: <p>If you are using <a href="https://laravel.com/docs/master/valet" rel="nofollow noreferrer">Laravel Valet</a>, the newest version takes care of that. You may either change the domain with <code>valet domain test</code>, or better: automatically secure your project it with <code>valet secure</code>.</p>
  
  <p>It's very smooth.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-11T16:55:31.240Z
Answers.Text: Would you mind explaining how it is able to bypass the chromium engine logics? Or does it contain a custom browser?
Answers.UserDisplayName: Robin Schambach
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-11T20:09:38.803Z
Answers.Text: It generates a self-signed certificate for each local domain. Very smooth.
Answers.UserDisplayName: Fred Carlsen
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-11T16:50:56.673Z
Answers.LastActivityDate: 2018-01-11T16:50:56.673Z
Answers.UserDisplayName: Fred Carlsen
Body: <p>I'm getting SSL errors when developing using .dev as a domain name. I believe it's because browsers are now automatically forwarding these to HTTPS://.</p>
  
  <p>Any ideas how to get around this with Craft? I can change the extension but Craft requires .dev for local development I believe.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-01-11T16:49:25.933Z
Comments.Text: What setup are you using? MAMP or something else?
Comments.UserDisplayName: Fred Carlsen
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-01-11T16:53:30.980Z
Comments.Text: Possible duplicate of [Problems setting up a local site](https://craftcms.stackexchange.com/questions/23192/problems-setting-up-a-local-site)
Comments.UserDisplayName: Robin Schambach
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-01-11T17:10:50.850Z
Comments.Text: Craft does not require .dev for local development. You can use any “dev-sounding” domain, it does not require the .dev suffix.
Comments.UserDisplayName: Lindsey D
Tags: <https><ssl>
Title: .dev local development
ThreadText: # .dev local development
  
  (Asked by: username_0 on 2018-01-11)
  
  I'm getting SSL errors when developing using .dev as a domain name. I believe it's because browsers are now automatically forwarding these to HTTPS://.
  
  Any ideas how to get around this with Craft? I can change the extension but Craft requires .dev for local development I believe.
  
  **Tags:** https, ssl
  
  > **Comments:**
  > **username_1**: What setup are you using? MAMP or something else?  
  > **username_2**: Possible duplicate of [Problems setting up a local site](https://craftcms.stackexchange.com/questions/23192/problems-setting-up-a-local-site)  
  > **username_3**: Craft does not require .dev for local development. You can use any “dev-sounding” domain, it does not require the .dev suffix.  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_3 on 2018-01-11. Score: 4
  
  This seems missing from the other answers, so I feel the need to emphasize it here...
  
  **Craft does not require .dev for local development.**
  
  Your local URL can be anything you want, Craft does not care. There is no requirement whatsoever on using a `.dev` domain. That being said, it is recommended that you use a ["dev-sounding"](https://craftcms.com/support/license-enforcement#how-do-we-determine-craft-is-running-on-a-public-domain) URL, in order to avoid the licensing nag warning. And even if you're getting the warning, it won't have any negative impact on the capabilities your site.
  
  The other answers already address what to do if you *do* use a `.dev` URL, so I won't cover it here. You may also want to read [this helpful answer](https://craftcms.stackexchange.com/a/23193/45) on a related question.
  
  
  ---
  
  ### Answer by username_4 on 2018-01-11. Score: 3
  
  Yea Google bought .dev a few years back and now chrome forces https on all .dev domains. I switched to using .test which has been reserved. So far, so good.
  
  <https://medium.engineering/use-a-dev-domain-not-anymore-95219778e6fd>
  
  
  ---
  
  ### Answer by username_1 on 2018-01-11. Score: 1
  
  If you are using [Laravel Valet](https://laravel.com/docs/master/valet), the newest version takes care of that. You may either change the domain with `valet domain test`, or better: automatically secure your project it with `valet secure`.
  
  It's very smooth.
  
  > **Comments:**
  > **username_2**: Would you mind explaining how it is able to bypass the chromium engine logics? Or does it contain a custom browser?  
  > **username_1**: It generates a self-signed certificate for each local domain. Very smooth.  
  
  ---
  
  