Request processing rate and reverse proxy

Guillaume Charhon guillaume at databerries.com
Mon Feb 29 16:05:16 UTC 2016


Hello,

I have setup nginx 1.9.3 as a reverse proxy [1] with a rate limitation per
server [2]. The rate limitation does not work on this scenario. The rate
request limitation works well if I use nginx as a normal webserver (for
example to serve the default welcome page).

I have attached my configuration files (listen on 80 and redirect to
another webserver running lighttpd).


[1] http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_pass
[2] http://nginx.org/en/docs/http/ngx_http_limit_req_module.html

Best Regards,
poiuytrez

PS : You can run it in a docker using the following commands if you need:

docker run --rm --name nginx -p 8082:80 -v
/yourdir/nginx.conf:/etc/nginx/nginx.conf:ro -v
/yourdir/default.conf:/etc/nginx/conf.d/default.conf --link backend:backend
nginx

docker run --rm --name backend -p 8081:80 jprjr/lighttpd

Go to http://localhost:8082/ in your web browser.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20160229/44f22bd6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nginx.conf
Type: application/octet-stream
Size: 705 bytes
Desc: not available
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20160229/44f22bd6/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: default.conf
Type: application/octet-stream
Size: 411 bytes
Desc: not available
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20160229/44f22bd6/attachment-0001.obj>


More information about the nginx mailing list