Automated nginx proxy for Docker containers using docker-gen
X-Forwarded-*
headers from clients by @rhansen in https://github.com/nginx-proxy/nginx-proxy/pull/1927
X-Forwarded-Host
by @rhansen in https://github.com/nginx-proxy/nginx-proxy/pull/2121
Full Changelog: https://github.com/nginx-proxy/nginx-proxy/compare/1.0.4...1.1.0
Full Changelog: https://github.com/nginx-proxy/nginx-proxy/compare/1.0.3...1.0.4
Full Changelog: https://github.com/nginx-proxy/nginx-proxy/compare/1.0.2...1.0.3
Full Changelog: https://github.com/nginx-proxy/nginx-proxy/compare/1.0.1...1.0.2
7.0.1
to 7.1.1
in /test/requirements by @dependabot in https://github.com/nginx-proxy/nginx-proxy/pull/1929
0.8.2
to 0.9.0
by @buchdag in https://github.com/nginx-proxy/nginx-proxy/pull/1933 and https://github.com/nginx-proxy/nginx-proxy/pull/1940
Full Changelog: https://github.com/nginx-proxy/nginx-proxy/compare/1.0.0...1.0.1
VIRTUAL_PATH
) by @buchdag in https://github.com/nginx-proxy/nginx-proxy/pull/1901
0.8.2
by @buchdag in https://github.com/nginx-proxy/nginx-proxy/pull/1902
1.16.7
to 1.17.8
by @dependabot in https://github.com/nginx-proxy/nginx-proxy/pull/1884 and https://github.com/nginx-proxy/nginx-proxy/pull/1917
ghcr.io/nginx-proxy/nginx-proxy
Many thanks to the following people for their work and/or feedback on the path based routing feature. @AlexanderLieret @junderw @warren-ru @JMLX42 @OliverRhyme @trowj @WolfspiritM @rodrigoaguilera @RafaelKr @gregsymons
Full Changelog: https://github.com/nginx-proxy/nginx-proxy/compare/0.10.1...1.0.0
Full Changelog: https://github.com/nginx-proxy/nginx-proxy/compare/0.10.0...0.10.1
This is a minor release.
Bugs fixed:
/app
(fixed by #1770)Changes since 0.9.3:
Dependencies:
nginx
-> 1.21.5
Other changes:
Thanks to @crazy-max, @kevinnls, @polarathene, @ucyang and @HPPinata for their contributions to this release.
This is a patch release.
Changes since 0.9.2:
upstream
names where reverted to the legacy (pre 0.9.1
) behaviour to avoid breaking existing setups that rely on them. A new optional SHA1_UPSTREAM_NAME
environment variable enable 0.9.2
behaviour if needed. See #1736 for more information.Default behaviour:
# example.com
upstream example.com {
server 172.16.0.2:80;
}
server {
server_name example.com;
#[…]
location / {
proxy_pass http://example.com;
}
}
With SHA1_UPSTREAM_NAME
set to true
:
# example.com
upstream 0caaf24ab1a0c33440c06afe99df986365b0781f {
server 172.16.0.2:80;
}
server {
server_name example.com;
#[…]
location / {
proxy_pass http://0caaf24ab1a0c33440c06afe99df986365b0781f;
}
}
Plus some CI and docs updates.
This is a patch release.
Bugs fixed:
HTTPS_PORT
(fixed by #1662)server 127.0.0.1 down
entry in upstream
blocks, and only when required (fixed by #1667, #1679)Changes since 0.9.1:
1.19.10
-> 1.21.1
0.7.6
-> 0.7.7
1.16.5
-> 1.16.7
Various CI and docs updates.
Note:
0.9.1
, the upstream
names where changed and "-upstream" was appended to the bare reverse proxied hostname.0.9.2
, they were changed again to an sha1
hash of the hostname to prevent further issues with incorrect upstream
names.If you relied on those upstream
names in your custom configuration(s), please be aware that you'll have to update them if you use version 0.9.1
or higher.
0.9.0
and prior:
# example.com
upstream example.com {
server 172.16.0.2:80;
}
server {
server_name example.com;
#[…]
location / {
proxy_pass http://example.com;
}
}
0.9.1
:
# example.com
upstream example.com-upstream {
server 172.16.0.2:80;
}
server {
server_name example.com;
#[…]
location / {
proxy_pass http://example.com-upstream;
}
}
0.9.2
+:
# example.com
upstream 0caaf24ab1a0c33440c06afe99df986365b0781f {
server 172.16.0.2:80;
}
server {
server_name example.com;
#[…]
location / {
proxy_pass http://0caaf24ab1a0c33440c06afe99df986365b0781f;
}
}