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
I'd like to see few more lines about SHA-2 support in glibc crypt() in
documentation. I've created small patch for nginx.org repo, it's
WBRBW, Leonid Evdokimov, xmpp:firstname.lastname@example.org http://darkk.net.ru tel:+79816800702
PGP: 6691 DE6B 4CCD C1C1 76A0 0D4A E1F2 A980 7F50 FAB2
I saw there's an issue talking about "implement keepalive timeout for
I have a different scenario for this requirement.
I'm using Node.js web server as upstream, and set keep alive time out to 60
second in nodejs server. The problem is I found more than a hundred
"Connection reset by peer" errors everyday.
Because there's no any errors on nodejs side, I guess it was because of the
upstream has disconnected, and at the same time, nginx send a new request,
then received a TCP RST.
I tried Tengine <http://tengine.taobao.org/> which is a taobao cloned
version of nginx, and set upstream keep alive timeout to 30s, then there's
no errors any more.
So I want to know is there any plan to work on this enhancement? or can I
submit a patch for it?