nginx-proxy/test/test_virtual-path/test_forwarding.yml

web1:
  image: web
  expose:
    - "81"
  environment:
    WEB_PORTS: "81"
    VIRTUAL_HOST: "www.nginx-proxy.tld"
    VIRTUAL_PATH: "/web1/"
    VIRTUAL_DEST: "/"

sut:
  image: nginxproxy/nginx-proxy:test
  volumes:
    - /var/run/docker.sock:/tmp/docker.sock:ro
  environment:
    DEFAULT_ROOT: 301 http://$$host/web1$$request_uri
    HTTPS_METHOD: nohttps
test: Add test case for default app redirect Co-authored-by: Jonathan Underwood <junderwood@bitcoinbank.co.jp> 2021-08-17 11:08:56 +02:00			`web1:`
			`image: web`
			`expose:`
			`- "81"`
			`environment:`
			`WEB_PORTS: "81"`
			`VIRTUAL_HOST: "www.nginx-proxy.tld"`
			`VIRTUAL_PATH: "/web1/"`
			`VIRTUAL_DEST: "/"`

			`sut:`
			`image: nginxproxy/nginx-proxy:test`
			`volumes:`
			`- /var/run/docker.sock:/tmp/docker.sock:ro`
			`environment:`
fix: Don't downgrade from https to http if certificate is missing 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. 2023-02-03 08:31:08 +01:00			`DEFAULT_ROOT: 301 http://$$host/web1$$request_uri`
			`HTTPS_METHOD: nohttps`