Starting today, Google Chrome is rolling out v63 that now forces all .dev domains to use HTTPS. There is no workaround and they are apparently not changing this. Back in September Mattias Geniar wrote a post warning every one of the changes, and his post is a great primer on what the Chrome team has done.
This will affect everyone using .dev and if you are using Valet the recommended fix is to switch to a new unused extension like
.test. To change this in valet you can run the following:
valet domain test
Based on this article by Danny Wahl he recommends you use one of the following: “.localhost”, “.invalid”, “.test”, or “.example”.
If all this sounds like too much trouble another viable option is to switch to Firefox as your development browser. It’s fast, has comfortable dev tools, and has really made a ton of improvements over the past few years.Filed in: News / Chrome
- Backend Software Engineer (PHP Developer)
Austin TX, Bonita Springs FL
Certified eSupport Corp
- Laravel Developer
Glendale, CA (COVID Remote)
- Full-Stack Engineer (Mid to Senior)
Remote (EST, CST)
- Senior Laravel Developer (AI Applications)
Remote from anywhere in the UK or from our London office
- Full Stack Engineer
Join 31,000+ others and never miss out on new tips, tutorials, and more.
Creating Your Own PHP Helpers in a Laravel Project
Laravel provides many excellent helper functions that are convenient for doing things like working with arrays, file…
Laracon US 2018 Announces Speaker Evan You
Laracon US—the annual Laravel conference in the United States—has announced Evan You will be returning to Laracon 201…