mirror of
https://github.com/nginx-proxy/nginx-proxy
synced 2024-05-09 09:06:16 +02:00
dfd4f54c61
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.
29 lines
437 B
YAML
29 lines
437 B
YAML
version: '2'
|
|
|
|
networks:
|
|
net1: {}
|
|
net2: {}
|
|
net3: {}
|
|
|
|
services:
|
|
nginx-proxy:
|
|
image: nginxproxy/nginx-proxy:test
|
|
volumes:
|
|
- /var/run/docker.sock:/tmp/docker.sock:ro
|
|
networks:
|
|
- net1
|
|
environment:
|
|
HTTPS_METHOD: nohttps
|
|
|
|
web:
|
|
image: web
|
|
expose:
|
|
- "81"
|
|
environment:
|
|
WEB_PORTS: 81
|
|
VIRTUAL_HOST: web1.nginx-proxy.local
|
|
networks:
|
|
- net1
|
|
- net2
|
|
- net3
|