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

services:
  nginx-proxy:
    environment:
      HTTPS_METHOD: redirect

  http-only:
    image: web
    expose:
      - "83"
    environment:
      WEB_PORTS: "83"
      HTTPS_METHOD: nohttps
      VIRTUAL_HOST: http-only.nginx-proxy.test
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:`
tests: factor out base nginx-proxy config 2024-12-30 11:59:07 +01:00			`nginx-proxy:`
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			`environment:`
			`HTTPS_METHOD: redirect`
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"`
			`HTTPS_METHOD: nohttps`
			`VIRTUAL_HOST: http-only.nginx-proxy.test`