Hi,
I’ve setup nginx (1.0.14) with mod_zip (1.1.6) and it runs fine “by
itself”.
The problem is that limit_rate and limit_rate_after directives (in the
location where the files are being
served from) are not respected.
I can download at full throttle while when not using mod_zip they work.
Anyone has encountered this issue, any workarounds?
Thanks
Stelios
Posted at Nginx Forum:
Ignore this msg. mod_zip works fine.
The problem was limit_rate_after that I’ve put in at some point, so I
didn’t download a large enough file to see the limit_rate kick in.
Posted at Nginx Forum:
On 9 May 2012 12:28, stelios [email protected] wrote:
Ignore this msg. mod_zip works fine.
The problem was limit_rate_after that I’ve put in at some point, so I
didn’t download a large enough file to see the limit_rate kick in.
Just out of interest, does this combination of directives rate limit
before or after the stream is zipped?
Jonathan
Jonathan M.
Oxford, London, UK
Hello!
On Wed, May 09, 2012 at 02:25:10PM +0100, Jonathan M. wrote:
On 9 May 2012 12:28, stelios [email protected] wrote:
Ignore this msg. mod_zip works fine.
The problem was limit_rate_after that I’ve put in at some point, so I
didn’t download a large enough file to see the limit_rate kick in.
Just out of interest, does this combination of directives rate limit
before or after the stream is zipped?
Directives limit_rate/limit_rate_after count (and limit) actual
bytes sent to a client, i.e. after the stream is zipped (or
gzipped, or whatever else).
Maxim D.