nginx.git/src/http/modules, branch release-1.7.7 nginx Upstream: proxy_limit_rate and friends. 2014-10-28T09:29:59+00:00 Roman Arutyunyan arut@nginx.com 2014-10-28T09:29:59+00:00 18e4d042b04e1ec09d1b74537541b3bb99a75c3f The directives limit the upstream read rate. For example, "proxy_limit_rate 42" limits proxy upstream read rate to 42 bytes per second. 
The directives limit the upstream read rate.  For example,
"proxy_limit_rate 42" limits proxy upstream read rate to
42 bytes per second.
Gzip, gunzip: flush busy buffers if any. 2014-10-15T18:57:23+00:00 Maxim Dounin mdounin@mdounin.ru 2014-10-15T18:57:23+00:00 97e618c55602aeb241c2adcb2fc8d00c02104653 Previous code resulted in transfer stalls when client happened to read all the data in buffers at once, while all gzip buffers were exhausted (but ctx->nomem wasn't set). Make sure to call next body filter at least once per call if there are busy buffers. Additionally, handling of calls with NULL chain was changed to follow the same logic, i.e., next body filter is only called with NULL chain if there are busy buffers. This is expected to fix "output chain is empty" alerts as reported by some users after c52a761a2029 (1.5.7). 
Previous code resulted in transfer stalls when client happened
to read all the data in buffers at once, while all gzip buffers
were exhausted (but ctx->nomem wasn't set).  Make sure to call
next body filter at least once per call if there are busy buffers.

Additionally, handling of calls with NULL chain was changed to follow
the same logic, i.e., next body filter is only called with NULL chain
if there are busy buffers.  This is expected to fix "output chain is empty"
alerts as reported by some users after c52a761a2029 (1.5.7).
Upstream: proxy_force_ranges and friends. 2014-10-14T14:32:01+00:00 Roman Arutyunyan arut@nginx.com 2014-10-14T14:32:01+00:00 2244a5e9cf40d271ddf31f083acd694b5d9f13b4 The directives enable byte ranges for both cached and uncached responses regardless of backend headers. 
The directives enable byte ranges for both cached and uncached
responses regardless of backend headers.
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.