Request size limits (client_max_body_size) in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What happens when a client sends a request larger than the configured limit?

Given the nginx configuration directive client_max_body_size 1m;, what is the HTTP status code returned if a client uploads a file of 2 megabytes?

Nginx

client_max_body_size 1m;

A 404 Not Found

B 413 Payload Too Large

C 500 Internal Server Error

D 200 OK

💡 Hint

Think about what HTTP status code means the request is too big.

When the client sends a request body larger than client_max_body_size, nginx rejects it with HTTP status 413, meaning the payload is too large.

❓ Configuration

intermediate

How to set a 10 megabyte request size limit in nginx?

Which configuration snippet correctly sets the maximum allowed client request body size to 10 megabytes?

A client_max_body_size 10m;

B client_max_body_size 10mb;

C client_max_body_size 10

D client_max_body_size 10MB;

💡 Hint

Check the correct unit suffix for megabytes in nginx.

The correct unit suffix for megabytes in nginx is lowercase m. So 10m means 10 megabytes.

❓ Troubleshoot

advanced

Why does nginx still accept large uploads despite setting client_max_body_size?

You set client_max_body_size 1m; in the http block of nginx.conf, but clients can still upload files larger than 1 megabyte. What is the most likely reason?

A The client is using chunked transfer encoding which bypasses the limit

B nginx does not enforce client_max_body_size in the http block

C The directive is overridden by a <code>server</code> or <code>location</code> block with a higher limit

D The directive requires a reload of the operating system to take effect

💡 Hint

Remember nginx configuration inheritance and overrides.

Directives in server or location blocks override those in the http block. If a lower limit is set globally but a higher limit is set in a specific block, the higher limit applies there.

🔀 Workflow

advanced

Order the steps to apply a new client_max_body_size setting in nginx

Put these steps in the correct order to change the client_max_body_size to 5 megabytes and apply it safely.

A 1,2,4,3

B 2,1,3,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

Think about safe configuration changes and verification.

First edit the config, then test syntax, reload nginx to apply, and finally verify the change works.

✅ Best Practice

expert

What is the best practice for setting client_max_body_size in a multi-site nginx server?

You manage an nginx server hosting multiple websites with different upload size needs. What is the best practice for setting client_max_body_size?

A Set a global default in the http block and override per server or location as needed

B Set the largest needed size globally in the http block to cover all sites

C Set client_max_body_size only in the main nginx.conf file without overrides

D Do not set client_max_body_size and rely on application-level limits

💡 Hint

Consider flexibility and security for different sites.

Setting a global default ensures a baseline limit. Overriding per site or location allows tailored limits, improving security and resource control.

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