Resolves issue with proxy-redirect nginx configuration
Resolves an issue where the proxy-redirect annotations were not generating the correct configuration possibly because of user error. This is done by only setting the proxy_redirect if both proxy-redirect-from and proxy-redirect-to have valid values. Also adds the e2e tests. Fixes #2074
This commit is contained in:
parent
d577fe2c15
commit
e224259e38
6 changed files with 179 additions and 7 deletions
|
|
@ -443,11 +443,13 @@ In some scenarios is required to have different values. To allow this we provide
|
|||
|
||||
### Proxy redirect
|
||||
|
||||
With the annotations `nginx.ingress.kubernetes.io/proxy-redirect-from` and `nginx.ingress.kubernetes.io/proxy-redirect-to` it is possible to set the text that should be changed in the `Location` and `Refresh` header fields of a proxied server response (http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_redirect)
|
||||
With the annotations `nginx.ingress.kubernetes.io/proxy-redirect-from` and `nginx.ingress.kubernetes.io/proxy-redirect-to` it is possible to
|
||||
set the text that should be changed in the `Location` and `Refresh` header fields of a proxied server response (http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_redirect)
|
||||
|
||||
Setting "off" or "default" in the annotation `nginx.ingress.kubernetes.io/proxy-redirect-from` disables `nginx.ingress.kubernetes.io/proxy-redirect-to`.
|
||||
Setting "off" or "default" in the annotation `nginx.ingress.kubernetes.io/proxy-redirect-from` disables `nginx.ingress.kubernetes.io/proxy-redirect-to`,
|
||||
otherwise, both annotations must be used in unison. Note that each annotation must be a string without spaces.
|
||||
|
||||
Both annotations will be used in any other case. By default the value is "off".
|
||||
By default the value of each annotation is "off".
|
||||
|
||||
### Custom max body size
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue