Opened 3 years ago
Closed 3 years ago
#2084 closed enhancement (wontfix)
The restriction on directive "proxy_buffers" is not complete.
| 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
Based on the handling logic in src/http/modules/ngx_http_proxy_module.c, the "proxy_buffers" must be at least 2 buffers, but the document doesn't mentioned it. It is better to add this information in the doc https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_buffers.
A similar situation also happens in directive "scgi_buffers"(https://nginx.org/en/docs/http/ngx_http_scgi_module.html#scgi_buffers) and "uwsgi_buffers"(https://nginx.org/en/docs/http/ngx_http_uwsgi_module.html#uwsgi_buffers).
Change History (2)
comment:1 by , 3 years ago
comment:2 by , 3 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Thank you for your suggestion. It is believed that not all limitations have to be documented, mostly because this needlessly complicates reading of the documentation, and appropriate error reported during configuration parsing is enough. This especially applies to cases like this one, when a limitation is very unlikely to be hit in practice.
See also #2083.