Opened 4 years ago
Closed 4 years ago
#2092 closed enhancement (wontfix)
The description about directive "proxy_redirect" is not clear.
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | documentation | Version: | 1.18.x |
| Keywords: | Cc: | zhoushulin1992@… | |
| uname -a: | Linux xlarge 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux | ||
| nginx -V: |
nginx version: nginx/1.18.0
built by gcc 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) configure arguments: --prefix=/usr/local/nginx --with-pcre=/root/Downloads/pcre-8.43 |
||
Description
In the description of directive "proxy_redirect" in https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_redirect, "The default replacement specified by the default parameter uses the parameters of the location and proxy_pass directives", this indicates that "proxy_redirect" uses the value of "proxy_pass", implicitly specify the order of these two directives, i.e. "proxy_redirect default" should be placed after the "proxy_pass" directive. However, in case of unintentional error, I suggest we explicitly state this information in the doc.
Note:
See TracTickets
for help on using tickets.
Thank you for your suggestion. It is believed that the current description is clear enough, at least we've never seen any complaints from the users about this.