We are glad to share with first results of our ongoing efforts to create
documentation for nginx developers: the development guide document .
The guide is not yet 100% complete and more parts to follow.
Of course, your feedback is welcome.
Scanning nginx sources and nginx documentation
I found some directives, which present in nginx sources
but absent in nginx documentation:
post_action is known dangerous directive, it undocumented
by purpose and in vim syntax file it marked accordingly:
syn keyword ngxDirectiveError contained post_action
But what about all rest undocumented directives, they are undocumented
by purpose or through inadvertence, and may be in the near future
all it (except post_action directive) will be documented?
And second question: how they are should be marked in nginx syntax file,
as normal nginx directives, or color mark it as undocumented directives?
syn keyword ngxDirectiveUndocumented contained acceptex_read
syn keyword ngxDirectiveUndocumented contained degradation
syn keyword ngxDirectiveUndocumented contained uwsgi_string
hi link ngxDirectiveUndocumented Constant
when I try to enter a bug at https://trac.nginx.org/nginx/newticket#ticket, choose as version 1.12.x and submit the system rejects the ticket with the message:
Warning: The ticket field 'nginx_version' is invalid: nginx_version is required
And here is the actual question:
proxy_pass can accept an URL or a server group. When a server group (upstream) is defined, then with max_conns= the maximum number of simultaneous connections can be specified.
The documentation of proxy_pass shall clarify, whether by default with URL only consequent connections are allowed/whether defining upstream is the only way to introduce parallelism towards the proxy.