Closed stephanvane closed 3 years ago
@stephanvane I'm sure you have your reasons, and they're related to your workflow, but for future design consideration it would be helpful to understand those reasons more clearly. So ...
Question: Why do you want unsecure proxies? And is there a technical reason for wanting to bypass using SSL?
Hi @drbyte, thanks for your answer
I think that in general it would be for the same reason anyone wants to bypass SSL on parked / linked apps. There must be a reason why valet includes the valet secure/unsecure
commands at all :-)
In my specific case, I wanted to have a valet-proxied-app communicate with a http-only-local-api that was running. Unfortunately the browser blocked http resources requested from an https website.
If we decide to not to allow bypassing SSL for proxies, I think it should be reflected in the documentation, and return message.
The current message of The [foo.test] site will now serve traffic over HTTP.
while in reality the proxy is removed completely is confusing at least.
Do the changes proposed in #1005 accommodate the requirements you mention?
For my case, this would technically solve the problem, thank you!
From a usability's perspective I would propose using a more standard way of configuring it. having two different methods (valet unsecure foo
and valet proxy --unsecure
) and two differents defaults (secure for proxy / unsecure for park/link) might be confusing.
Using the same methods for both park/link and proxy would be more straightforward in my opinion.
valet link foo
valet secure foo
/ valet unsecure foo
valet unlink
valet proxy foo http://example.com
valet secure foo
/ valet unsecure foo
valet unproxy foo
Is this still an issue? There seems to be a change between Valet 2.14.0 and 2.15.0 that valet proxy
no longer creates an nginx configuration that listens on port 443, and instead now requires the --secure
flag to listen on port 443.
Correct. This issue can be closed due to the changes in 2.15.0
/cc @mattstauffer
Clear description of your problem
All proxies are using SSL by default. Trying to run
valet unsecure
removes the proxy completelyExpected behavior
minor issue:
valet proxy foo http://example.com
should leave SSL off by default, as the documentation suggests:main issue:
valet unsecure foo
doesn't remove SSL, but removes the proxy completely.Current behavior
valet proxy
enables SSL by default, and redirects http traffic to httpsSteps to Reproduce
valet proxy foo http://example.com
valet proxies # shows 'foo' with SSL enabled
valet unsecure foo # "The [foo.test] site will now serve traffic over HTTP."
valet proxies # 'foo' is now completely gone
Valet unsecure removes the
foo.test
file that was in~/.config/valet/Nginx/
Diagnosis
sw_vers
valet --version
cat ~/.config/valet/config.json
cat ~/.composer/composer.json
composer global diagnose
composer global outdated
ls -al /etc/sudoers.d/
brew config
brew services list
brew list --formula --versions | grep -E "(php|nginx|dnsmasq|mariadb|mysql|mailhog|openssl)(@\d\..*)?\s"
brew outdated
brew tap
php -v
which -a php
php --ini
nginx -v
curl --version
php --ri curl
~/.composer/vendor/laravel/valet/bin/ngrok version
ls -al ~/.ngrok2
brew info nginx
brew info php
brew info openssl
openssl version -a
openssl ciphers
sudo nginx -t
which -a php-fpm
/usr/local/opt/php/sbin/php-fpm -v
sudo /usr/local/opt/php/sbin/php-fpm -y /usr/local/etc/php/7.4/php-fpm.conf --test
ls -al ~/Library/LaunchAgents | grep homebrew
ls -al /Library/LaunchAgents | grep homebrew
ls -al /Library/LaunchDaemons | grep homebrew
ls -aln /etc/resolv.conf
cat /etc/resolv.conf