Re: nginx limit_rate if in location - strange behaviour - possible bug ?

2014-02-17 Thread Jonathan Matthews
On 17 February 2014 10:02, Bozhidara Marinchovska wrote: > My question is what may be the reason when downloading the example file with > download manager not to match limit_rate directive "Download managers" open multiple connections and grab different byte ranges of the same file across those c

Re: nginx limit_rate if in location - strange behaviour - possible bug ?

2014-02-17 Thread Bozhidara Marinchovska
Hi, again FreeBSD 9.1-STABLE #0: Sat May 18 00:32:18 EEST 2013 amd64 nginx version: nginx/1.4.4 TLS SNI support enabled configure arguments: --prefix=/usr/local/etc/nginx --with-cc-opt='-I /usr/local/include' --with-ld-opt='-L /usr/local/lib' --conf-path=/usr/local/etc/nginx/nginx.conf --sbin

Re: nginx limit_rate if in location - strange behaviour - possible bug ?

2013-10-09 Thread Maxim Dounin
Hello! On Wed, Oct 09, 2013 at 05:21:51PM +0300, Bozhidara Marinchovska wrote: [...] > I'm using limit_rate case if in location. Regarding documentation > "if in location" context is avaiable. > > My configuration is as follows: > > location some_extension { > > # case 1 > if match_something

Re: nginx limit_rate if in location - strange behaviour - possible bug ?

2013-10-09 Thread Bozhidara Marinchovska
I'm sorry, misread documentation. Placed set $limit_rate 0 in my case1 instead limit_rate 0 and now works as expected. On 09.10.2013 17:21 ч., Bozhidara Marinchovska wrote: Hi, nginx -V nginx version: nginx/1.4.2 configure arguments: --prefix=/usr/local/etc/nginx --with-cc-opt='-I /usr/loc

nginx limit_rate if in location - strange behaviour - possible bug ?

2013-10-09 Thread Bozhidara Marinchovska
Hi, nginx -V nginx version: nginx/1.4.2 configure arguments: --prefix=/usr/local/etc/nginx --with-cc-opt='-I /usr/local/include' --with-ld-opt='-L /usr/local/lib' --conf-path=/usr/local/etc/nginx/nginx.conf --sbin-path=/usr/local/sbin/nginx --pid-path=/var/run/nginx.pid --error-log-path=/var/