nginx-proxy/test/test_fallback.data/nohttps.yml

version: "2"

services:
  sut:
    image: nginxproxy/nginx-proxy:test
    volumes:
      - /var/run/docker.sock:/tmp/docker.sock:ro
    environment:
      HTTPS_METHOD: nohttps

  http-only:
    image: web
    expose:
      - "83"
    environment:
      WEB_PORTS: "83"
      VIRTUAL_HOST: http-only.nginx-proxy.test
ci: ensure all compose files are valid compose v2 + formatting 2023-12-11 14:25:04 +01:00			`version: "2"`

fix: Don't create fallback http(s) server when http(s) disabled Before, a fallback http server was created to handle requests for unknown virtual hosts even when `HTTPS_METHOD=nohttp`. (In this case, all http vhosts would be unknown.) Likewise, a catch-all fallback https server was still created even if `HTTPS_METHOD=nohttps`. Now the fallback servers are created only if needed. This brings the behavior in line with the documentation and user expectation. It will also make it easier to implement a planned feature: different servers on different ports. 2023-02-04 18:59:38 -05:00			`services:`
			`sut:`
			`image: nginxproxy/nginx-proxy:test`
			`volumes:`
			`- /var/run/docker.sock:/tmp/docker.sock:ro`
			`environment:`
			`HTTPS_METHOD: nohttps`
ci: ensure all compose files are valid compose v2 + formatting 2023-12-11 14:25:04 +01:00
fix: Don't create fallback http(s) server when http(s) disabled Before, a fallback http server was created to handle requests for unknown virtual hosts even when `HTTPS_METHOD=nohttp`. (In this case, all http vhosts would be unknown.) Likewise, a catch-all fallback https server was still created even if `HTTPS_METHOD=nohttps`. Now the fallback servers are created only if needed. This brings the behavior in line with the documentation and user expectation. It will also make it easier to implement a planned feature: different servers on different ports. 2023-02-04 18:59:38 -05:00			`http-only:`
			`image: web`
			`expose:`
			`- "83"`
			`environment:`
			`WEB_PORTS: "83"`
			`VIRTUAL_HOST: http-only.nginx-proxy.test`