The docs <http://nginx.org/en/docs/http/ngx_http_core_module.html#limit_rate> suggest using 'if', even though it is uncertain under which conditions this directive works/should be used or not...
You could either set the logic in 'if' or use a map matching the $http_method variable and setting an intermediary variable which will be used in turn by 'if' to set the rate_limit feature or not. That is the most efficient way of doing that I can think of. --- *B. R.* On Fri, Apr 10, 2015 at 11:22 PM, jb <[email protected]> wrote: > Anyone? no ideas? > > how would i go about getting such a feature added. I imagine it would be > much the same code, just applied to reading the request body rather than > writing it. And since it is core functionality I'm not sure one for POST > should be an extension? > > On Wed, Apr 8, 2015 at 4:23 PM, jb <[email protected]> wrote: > >> Is there a module that does throttled reading for POST and works the same >> way as limit_rate does for GET (per stream, X bytes per second). >> >> I got some kind of throttle effect by putting a usleep() into the >> os/unix/ngx_recv.c file reader, but I want to use something that works the >> same way as limit_rate. >> >> thanks >> > > > _______________________________________________ > nginx mailing list > [email protected] > http://mailman.nginx.org/mailman/listinfo/nginx >
_______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
