change order of limit_req lookup result processing2010-10-14T09:20:01+00:00Igor Sysoevigor@sysoev.ru2010-10-14T09:20:01+00:00c5d1790e1d7c04599975ccf8697688d3be99157c
an excess was logged as 0.000 if requests were limited without delay:2010-10-13T20:58:41+00:00Igor Sysoevigor@sysoev.ru2010-10-13T20:58:41+00:00622721a598e272ccea54dba8dda2b89227f0d372
*) use a real excess value instead of non-updated limit_req rbtree node field,
*) move inactivity queue handling inside ngx_http_limit_req_lookup()
since the node is not required outside the lookup function;
the bug has been introduced in r3184
*) use a real excess value instead of non-updated limit_req rbtree node field,
*) move inactivity queue handling inside ngx_http_limit_req_lookup()
since the node is not required outside the lookup function;
the bug has been introduced in r3184