phpmon/laravel-valet
1
0
Fork 0
mirror of https://github.com/laravel/valet.git synced 2026-02-05 08:30:07 +01:00
Code Activity

Improve security by listening on 127.0.0.1 only

Browse Source 
Fixes #772

I've been using this config change since Aug 17, 2019, without any negative side-effects.
All Valet services continue to work properly, and Valet Share still works just as expected.

If someone were to have a challenge with it, there's an easy downgrade: just remove the `127.0.0.1:` from these files, and run `valet tld test` to rebuild the individual site configs. Or just manually edit the `~/.config/valet/Nginx` site file manually.
This commit is contained in:
Chris Brown
2019-09-07 17:44:19 -04:00
parent b14ce74087
commit fcd73d73bc
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
cli/stubs/secure.valet.conf
View File

@@ -1,11 +1,11 @@
server {
listen 80;
listen 127.0.0.1:80;
server_name VALET_SITE www.VALET_SITE *.VALET_SITE;
return 301 https://$host$request_uri;
}
server {
listen 443 ssl http2;
listen 127.0.0.1:443 ssl http2;
server_name VALET_SITE www.VALET_SITE *.VALET_SITE;
root /;
charset utf-8;
@@ -43,7 +43,7 @@ server {
}
server {
listen 60;
listen 127.0.0.1:60;
server_name VALET_SITE www.VALET_SITE *.VALET_SITE;
root /;
charset utf-8;

2
cli/stubs/valet.conf
View File

@@ -1,5 +1,5 @@
server {
listen 80 default_server;
listen 127.0.0.1:80 default_server;
root /;
charset utf-8;
client_max_body_size 128M;