id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	uname	nginx_version
293	implement $limit_rate_after, similar to $limit_rate	Yuntaek LIM	Maxim Dounin	"Hi,

This issue would be out of AMI-Support range. However, I would like to know if this is a bug before creating new ticket on 'nignx.org'.

When I set 'ri' and 'rs' parameters together, the value of 'rs' is not applied.
When client requests as an below example with a following configuration, 'limit_rate_after', which is dependent on 'rs' parameter,does not work.

'''Configuation'''

{{{ 
server {
        server_name test-domain.com
        root    /htdocs;

        location ~* \.flv {
            flv;
            if ($arg_LRA) {
                set $limit_rate_after $arg_LRA;
            }
            if ($arg_LR) {
                set $limit_rate ""${arg_LR}k"";
            }
        }
    }
}}}
    
'''Example of client request'''

 {{{
curl -o /dev/null -H ""Host: test-domain.com"" http://localhost/test.flv?ri=100&rs=8192000
}}}

The result of client request shows that 'limit_rate' 100k has worked but limit_rate_after 8192000 has not worked.

I assumed that this is bug, so I've adjusted attached patch file which are modified below files.
{{{
./src/http/ngx_http_request.h
./src/http/ngx_http_variables.c
./src/http/ngx_http_write_filter_module.c
}}}



I would like to know if there is a problem in my configuration or it is bug."	enhancement	closed	minor		nginx-core	1.2.x	fixed			Linux SVC2-01 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux	nginx version: nginx/1.2.6