nginx.git/src/http/modules, branch release-1.7.6 nginx Upstream keepalive: reset c->sent on cached connections. 2014-09-29T18:27:45+00:00 Maxim Dounin mdounin@mdounin.ru 2014-09-29T18:27:45+00:00 403a9efc0c1f50333b65d5c86deb80c794e45595 The c->sent is reset to 0 on each request by server-side http code, so do the same on client side. This allows to count number of bytes sent in a particular request. 
The c->sent is reset to 0 on each request by server-side http code,
so do the same on client side.  This allows to count number of bytes
sent in a particular request.
Limit req: reduced number of parameters in the lookup function. 2014-09-24T17:55:19+00:00 Valentin Bartenev vbart@nginx.com 2014-09-24T17:55:19+00:00 c9fbbc82731fe54f08bf53fa41677d3f1fd6fbcb No functional changes. 
No functional changes.
Limit req: use complex value in limit_req_zone. 2014-09-24T17:55:19+00:00 Valentin Bartenev vbart@nginx.com 2014-09-24T17:55:19+00:00 021a9df15b94af3b5a524cac9c67f9f0e21c37d1 One intentional side effect of this change is that key is allowed only in the first position. Previously, it was possible to specify the key variable at any position, but that was never documented, and is contrary with nginx configuration practice for positional parameters. 
One intentional side effect of this change is that key is allowed only
in the first position.  Previously, it was possible to specify the key
variable at any position, but that was never documented, and is contrary
with nginx configuration practice for positional parameters.
Limit conn: aligned field names in structures. 2014-09-24T17:55:19+00:00 Valentin Bartenev vbart@nginx.com 2014-09-24T17:55:19+00:00 98f7d0efb2f6b6d62f4684750676ba2581f333c0 No functional changes. 
No functional changes.
Limit conn: use complex value in limit_conn_zone (ticket #121). 2014-09-24T17:55:19+00:00 Valentin Bartenev vbart@nginx.com 2014-09-24T17:55:19+00:00 dd1ae4348a58c16a16b6e70c81875a2f751f661c One intentional side effect of this change is that key is allowed only in the first position. Previously, it was possible to specify the key variable at any position, but that was never documented, and is contrary to nginx configuration practice for positional parameters. 
One intentional side effect of this change is that key is allowed only
in the first position.  Previously, it was possible to specify the key
variable at any position, but that was never documented, and is contrary
to nginx configuration practice for positional parameters.
Limit conn: removed deprecated "limit_zone" directive. 2014-09-24T17:55:19+00:00 Valentin Bartenev vbart@nginx.com 2014-09-24T17:55:19+00:00 1866f15d7d938d8b78e94839b00db06df98d8cb8 It's deprecated since 260d591cb6a3 (1.1.8). The "limit_conn_zone" directive should be used instead. 
It's deprecated since 260d591cb6a3 (1.1.8).  The "limit_conn_zone" directive
should be used instead.
FastCGI: fixed start pointers in request buffers. 2014-09-18T12:37:14+00:00 Roman Arutyunyan arut@nginx.com 2014-09-18T12:37:14+00:00 66876d0b098fee3e3a0cbdf039a11050814f55e0 The start pointers are used in ngx_http_upstream_reinit() to reinit FastCGI requests. 
The start pointers are used in ngx_http_upstream_reinit() to
reinit FastCGI requests.
Limit req: don't truncate key value to 255 bytes. 2014-09-16T17:12:51+00:00 Valentin Bartenev vbart@nginx.com 2014-09-16T17:12:51+00:00 a7798de9bd8f1f4fd5bce6d77631073d472bed8a While the module allows to use values up to 65535 bytes as a key, that actually never worked properly. 
While the module allows to use values up to 65535 bytes as a key,
that actually never worked properly.
Access log: fixed the "if=" parameter with buffering (ticket #625). 2014-09-13T17:47:13+00:00 Valentin Bartenev vbart@nginx.com 2014-09-13T17:47:13+00:00 152d92b4b76303d7b2d64e76cadf6d466df48f7f It might not work if there were more than one "access_log" directives pointed to the same file and duplicate buffer parameters. 
It might not work if there were more than one "access_log" directives
pointed to the same file and duplicate buffer parameters.
Upstream: limited next_upstream time and tries (ticket #544). 2014-09-12T14:50:47+00:00 Roman Arutyunyan arut@nginx.com 2014-09-12T14:50:47+00:00 02ce6c415f07ea8d7fa6b59a17ee2f02e77ab66b The new directives {proxy,fastcgi,scgi,uwsgi,memcached}_next_upstream_tries and {proxy,fastcgi,scgi,uwsgi,memcached}_next_upstream_timeout limit the number of upstreams tried and the maximum time spent for these tries when searching for a valid upstream. 
The new directives {proxy,fastcgi,scgi,uwsgi,memcached}_next_upstream_tries
and {proxy,fastcgi,scgi,uwsgi,memcached}_next_upstream_timeout limit
the number of upstreams tried and the maximum time spent for these tries
when searching for a valid upstream.