0

How to create limit rate on Nginx, I read many articles any apply it but it doesn't work on NginX container and testing using siege , here is my nginx.conf

    user  nginx;
worker_processes  1;

error_log  /var/log/nginx/error.log warn;
pid        /var/run/nginx.pid;


events {
    worker_connections  1024;
}


http {
    include       /etc/nginx/mime.types;
    default_type  application/octet-stream;

    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  /var/log/nginx/access.log  main;

    sendfile        on;
    #tcp_nopush     on;

    keepalive_timeout  65;

    #gzip  on;

    include /etc/nginx/conf.d/*.conf;
    limit_req_zone  $binary_remote_addr  zone=one:10m   rate=1r/s;

The default.conf

server {
    listen       80;
    server_name  localhost;

    #charset koi8-r;
    access_log  /var/log/nginx/host.access.log  main;

    location / {
        root   /usr/share/nginx/html;
        index  index.html index.htm;
        limit_req zone=one burst=5 nodelay;
    }

    error_page  404              /404.html;

    # redirect server error pages to the static page /50x.html
    #
    error_page   500 502 503 504  /50x.html;
    location = /50x.html {
        root   /usr/share/nginx/html;
    }

    # proxy the PHP scripts to Apache listening on 127.0.0.1:80
    #
    #location ~ \.php$ {
    #    proxy_pass   http://127.0.0.1;
    #}

    # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
    #
    #location ~ \.php$ {
    #    root           html;
    #    fastcgi_pass   127.0.0.1:9000;
    #    fastcgi_index  index.php;
    #    fastcgi_param  SCRIPT_FILENAME  /scripts$fastcgi_script_name;
    #    include        fastcgi_params;
    #}

    # deny access to .htaccess files, if Apache's document root
    # concurs with nginx's one
    #
    #location ~ /\.ht {
    #    deny  all;
    #}
}

and using Siege for testing

 siege -r 1 -c 30 http://localhost:8080

the output is

HTTP/1.1 200     0.01 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.01 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.02 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.03 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.03 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.03 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.03 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.03 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.03 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.03 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.03 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.03 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.03 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.03 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.04 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.04 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.04 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.04 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.04 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.04 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.04 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.04 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.04 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.04 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.04 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.04 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.04 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.04 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.05 secs:     156 bytes ==> GET  /
HTTP/1.1 200     0.04 secs:     156 bytes ==> GET  /

there is something wrong because Siege can't get any errors or 404 or any error message, something-something wrong I am doing

  • 1
    Your nginx listens to port 80 and your siege goes to port 8080. – Alexey Ten Jun 22 '18 at 11:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.