Request size limits (client_max_body_size) in Nginx - Commands & Configuration

Introduction

Sometimes users upload files or send data that is too large for a web server to handle safely. Nginx can limit the size of client requests to prevent overload or abuse by setting a maximum allowed size.

When you want to stop users from uploading files larger than 10MB to your website.

When your server has limited memory and you want to avoid crashes from huge requests.

When you want to protect your backend services from receiving unexpectedly large data.

When you want to return a clear error message if a user sends too much data.

When you want to control bandwidth usage by limiting request sizes.

Config File - nginx.conf

nginx.conf

events {
    worker_connections 1024;
}

http {
    server {
        listen 80;
        server_name example.com;

        client_max_body_size 10M;

        location /upload {
            root /var/www/html;
            index index.html;
        }
    }
}

The client_max_body_size 10M; line sets the maximum allowed size of client request bodies to 10 megabytes. If a client sends more data, nginx will reject it with an error.

The server block defines the website listening on port 80 for example.com. The location /upload block serves files from /var/www/html.

Commands

This command tests the nginx configuration file for syntax errors before applying changes.

Terminal

sudo nginx -t

Expected Output

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok

nginx: configuration file /etc/nginx/nginx.conf test is successful

This command reloads nginx to apply the new configuration without stopping the server.

Terminal

sudo systemctl reload nginx

Expected Output

No output (command runs silently)

This command tries to upload a file larger than 10MB to test if nginx blocks it according to the limit.

Terminal

curl -X POST -F 'file=@largefile.zip' http://example.com/upload

Expected Output

curl: (22) The requested URL returned error: 413 Request Entity Too Large

→

-X POST - Specifies the POST method to send data.

→

-F - Uploads a file as form data.

Key Concept

If you remember nothing else from this pattern, remember: client_max_body_size controls the largest request size nginx will accept from clients.

Common Mistakes

Setting client_max_body_size inside the wrong block like 'events' instead of 'http' or 'server'.

Nginx ignores the directive if placed in an invalid context, so the limit won't apply.

Always place client_max_body_size inside the 'http', 'server', or 'location' blocks.

Not reloading nginx after changing the configuration.

Changes won't take effect until nginx reloads or restarts.

Run 'sudo nginx -t' to test, then 'sudo systemctl reload nginx' to apply changes.

Setting client_max_body_size too low without considering legitimate upload sizes.

Users may get blocked unexpectedly, causing frustration.

Choose a size that balances protection and user needs, like 10M for typical uploads.

Summary

Add 'client_max_body_size' in nginx.conf inside the server block to limit request size.

Test the configuration with 'sudo nginx -t' before reloading nginx.

Reload nginx with 'sudo systemctl reload nginx' to apply the new limit.

Use curl or similar tools to verify that large requests are blocked with a 413 error.

Practice

1. What does the client_max_body_size directive control in nginx?

easy

A. The maximum size of server response body

B. The maximum number of client connections

C. The maximum size of a client request body

D. The maximum number of requests per second

Solution

1. Step 1: Understand the directive purpose

   The client_max_body_size directive limits how large the client request body can be, such as file uploads.

2. Step 2: Compare options with directive meaning

   Server response body size, maximum client connections, and maximum requests per second are unrelated to this directive.

3. Final Answer:

   The maximum size of a client request body -> Option C

4. Quick Check:

   client_max_body_size = max request size [OK]

Hint: Remember: 'body_size' means request size limit [OK]

Common Mistakes:

• Confusing request size with response size
• Thinking it limits connections or requests per second
• Assuming it controls server memory usage

2. Which of the following is the correct syntax to set client_max_body_size to 10 megabytes in nginx?

easy

A. client_max_body_size 10m;

B. client_max_body_size = 10MB;

C. client_max_body_size: 10mb

D. client_max_body_size 10;

Solution

1. Step 1: Recall nginx directive syntax

   Directives use the format: directive_name value; without equals or colons.

2. Step 2: Check units and case sensitivity

   Units are lowercase letters like m for megabytes, no uppercase or equals sign.

3. Final Answer:

   client_max_body_size 10m; -> Option A

4. Quick Check:

   Correct syntax uses no '=' and lowercase 'm' [OK]

Hint: Use lowercase units and no '=' sign [OK]

Common Mistakes:

• Using '=' sign in directive
• Writing units in uppercase (MB instead of m)
• Omitting semicolon at the end
• Using colon instead of space

3. Given this nginx config snippet inside a server block:

client_max_body_size 5m;

What happens if a client tries to upload a 6MB file?

medium

A. The client receives a 413 Request Entity Too Large error

B. The upload is accepted without errors

C. The server crashes due to overload

D. The file is silently truncated to 5MB

Solution

1. Step 1: Understand the limit effect

   The client_max_body_size 5m; sets max upload size to 5 megabytes.

2. Step 2: Check behavior on exceeding limit

   If a client sends more than 5MB, nginx rejects the request with HTTP 413 error.

3. Final Answer:

   The client receives a 413 Request Entity Too Large error -> Option A

4. Quick Check:

   Exceeding client_max_body_size = 413 error [OK]

Hint: Uploads over limit cause 413 error [OK]

Common Mistakes:

• Assuming server crashes on large upload
• Thinking file is truncated automatically
• Believing large uploads are accepted silently

4. You set client_max_body_size 20m; inside an nginx location block, but uploads larger than 1MB still fail. What is the most likely cause?

medium

A. The location block syntax is incorrect and ignored

B. A smaller client_max_body_size is set in the http or server block overriding it

C. nginx does not support setting client_max_body_size in location blocks

D. The client is using HTTP/1.0 which ignores this directive

Solution

1. Step 1: Understand directive inheritance

   nginx directives like client_max_body_size are inherited from higher-level blocks unless overridden. If uploads larger than 1MB fail despite setting 20m in location, it is likely that a smaller limit is set in http or server block that overrides or conflicts.

2. Step 2: Eliminate incorrect causes

   While syntax errors can cause ignoring, the most common cause is conflicting smaller limits at higher levels. nginx supports setting this directive in location blocks. HTTP version does not affect this directive.

3. Final Answer:

   A smaller client_max_body_size is set in the http or server block overriding it -> Option B

4. Quick Check:

   Conflicting smaller limits at higher levels cause upload failures [OK]

Hint: Check for conflicting limits in higher-level blocks [OK]

Common Mistakes:

• Believing location block settings are always absolute
• Assuming nginx ignores client_max_body_size in location
• Blaming HTTP version for upload size limits

5. You want to allow uploads up to 50MB only for the /upload path, but keep the default limit 1MB elsewhere. Which nginx config snippet achieves this?

hard

A. location /upload { client_max_body_size 50m; } server { client_max_body_size 1m; }

B. server { client_max_body_size 50m; location /upload { client_max_body_size 1m; } }

C. server { location /upload { client_max_body_size 50m; } } http { client_max_body_size 1m; }

D. http { client_max_body_size 1m; server { location /upload { client_max_body_size 50m; } } }

Solution

1. Step 1: Set default limit globally

   Set client_max_body_size 1m; in the http block to apply 1MB limit everywhere by default.

2. Step 2: Override limit for /upload path

   Inside the server block, set client_max_body_size 50m; in the location /upload block to allow larger uploads only there.

3. Final Answer:

   http { client_max_body_size 1m; server { location /upload { client_max_body_size 50m; } } } -> Option D

4. Quick Check:

   Global small limit + location override = correct config [OK]

Hint: Set small global limit, override in location block [OK]

Common Mistakes:

• Setting larger limit globally and smaller in location (wrong order)
• Placing directives outside proper blocks
• Missing semicolons or braces causing config errors