mirror of
https://github.com/nginx-proxy/nginx-proxy
synced 2025-07-15 08:24:27 +02:00
Before, if a site's certificate was not found, the site was served over http rather than https. Failing open like this is problematic for sites where security is important. Presumably the user set `HTTPS_METHOD` to a non-`noredirect` value (or left it unset) for a good reason; we should honor it even if it means serving error messages. WARNING: This change breaks compatibility. Any vhost where all of the following are true will fail after this change: * `HTTPS_METHOD` is either unset or set to a value other than `nohttps`. * The vhost does not have its own certificate (`default.crt` doesn't count). * Clients expect to be able to access the vhost by using plain http to nginx-proxy. To get the previous behavior, set `HTTPS_METHOD` to `nohttps` for the vhost. |
||
---|---|---|
.. | ||
my_custom_proxy_settings_bar.conf | ||
my_custom_proxy_settings.conf | ||
test_defaults-location.py | ||
test_defaults-location.yml | ||
test_defaults.py | ||
test_defaults.yml | ||
test_location-per-vhost.py | ||
test_location-per-vhost.yml | ||
test_per-vhost.py | ||
test_per-vhost.yml | ||
test_proxy-wide.py | ||
test_proxy-wide.yml |