[nginx] limit_rate_after

洪志道 hongzhidao at gmail.com
Tue Feb 14 14:40:06 UTC 2017

Thanks a lot for your reply.

So we can regard the patch is right, but it's not recommended.
Because it's more easily to break the request behavior in limiting rate.
And the limit_rate variable is also deprecated though it's so useful
that we can dynamically change the rate.

2017-02-14 21:11 GMT+08:00 Maxim Dounin <mdounin at mdounin.ru>:

> Hello!
> On Tue, Feb 14, 2017 at 03:54:35PM +0800, 洪志道 wrote:
> > Dose nginx consider support setting variable about limit_rate_after?
> > We can limit rate after $n bytes received from upstream.
> No.  A patch to introduce the $limit_rate_after variable was made
> several years ago, see this ticket:
> https://trac.nginx.org/nginx/ticket/293
> This approach is considered wrong though, and the patch wasn't
> committed.  Proper way to go is believed to be variables support
> in the limit_rate_after directive, see here:
> https://trac.nginx.org/nginx/ticket/293#comment:5
> --
> Maxim Dounin
> http://nginx.org/
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20170214/77634889/attachment.html>

More information about the nginx-devel mailing list