Request body handling in Nginx - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the maximum allowed size of the client request body to 1 megabyte.

Nginx

client_max_body_size [1];

Drag options to blanks, or click blank then click option'

A1m

B512k

C2m

D10m

Attempts:

3 left

💡 Hint

Common Mistakes

Using '1mb' instead of '1m' which is invalid in nginx.

Setting the size too low or too high unintentionally.

The directive client_max_body_size controls the maximum size of the client request body. Setting it to 1m limits the size to 1 megabyte.

2fill in blank

medium

Complete the code to enable buffering of client request bodies in a temporary file.

Nginx

client_body_buffer_size [1];

Drag options to blanks, or click blank then click option'

A4k

B8k

C32k

D16k

Attempts:

3 left

💡 Hint

Common Mistakes

Setting the buffer size too small causing frequent disk writes.

Using invalid size units.

The directive client_body_buffer_size sets the buffer size for reading client request bodies. A common value is 16k to allow buffering in memory before using temporary files.

3fill in blank

hard

Fix the error in the code to correctly specify the temporary directory for client body files.

Nginx

client_body_temp_path [1];

Drag options to blanks, or click blank then click option'

A/tmp/nginx/client_body

B/var/nginx/tmp/client_body

C/var/tmp/nginx/client_body

D/usr/tmp/client_body

Attempts:

3 left

💡 Hint

Common Mistakes

Using a directory that nginx cannot write to.

Specifying a non-existent or incorrect path.

The client_body_temp_path directive specifies the directory for temporary files storing client request bodies. The default and recommended path is /var/tmp/nginx/client_body.

4fill in blank

hard

Fill both blanks to configure nginx to read client request bodies in 8k chunks and store temporary files in /var/tmp/nginx/client_body.

Nginx

client_body_buffer_size [1];
client_body_temp_path [2];

Drag options to blanks, or click blank then click option'

A8k

B/var/tmp/nginx/client_body

C/tmp/nginx/client_body

D16k

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up buffer size and temp path values.

Using invalid directory paths.

Setting client_body_buffer_size to 8k configures the buffer size for reading client bodies. Setting client_body_temp_path to /var/tmp/nginx/client_body defines the directory for temporary files.

5fill in blank

hard

Fill all three blanks to create a configuration that limits client request body size to 2 megabytes, buffers 16k chunks, and stores temporary files in /tmp/nginx/client_body.

Nginx

client_max_body_size [1];
client_body_buffer_size [2];
client_body_temp_path [3];

Drag options to blanks, or click blank then click option'

A1m

B16k

C/tmp/nginx/client_body

D2m

Attempts:

3 left

💡 Hint

Common Mistakes

Using '1m' instead of '2m' for max body size.

Confusing buffer size with max body size.

Specifying a non-existent temporary directory.

This configuration sets the maximum client body size to 2 megabytes, buffers 16k chunks in memory, and stores temporary files in /tmp/nginx/client_body.

Practice

1. What does the client_max_body_size directive control in nginx?

easy

A. The maximum number of requests per second

B. The maximum size of the client request body that nginx will accept

C. The timeout duration for client requests

D. The maximum number of client connections allowed

Solution

1. Step 1: Understand the purpose of client_max_body_size

   This directive sets a limit on how large the data sent by a client in the request body can be.

2. Step 2: Compare with other options

   Other options relate to connections, timeouts, or request rates, which are unrelated to request body size.

3. Final Answer:

   The maximum size of the client request body that nginx will accept -> Option B

4. Quick Check:

   Request body size limit = D [OK]

Hint: Remember: max_body_size limits upload size [OK]

Common Mistakes:

• Confusing body size with connection limits
• Mixing up timeout settings with body size
• Thinking it controls request rate

2. Which of the following is the correct syntax to set the maximum client request body size to 10 megabytes in nginx?

easy

A. client_max_body_size 10MB;

B. client_max_body_size 10M

C. client_max_body_size 10mb;

D. client_max_body_size 10m;

Solution

1. Step 1: Recall nginx size suffixes

   nginx uses lowercase 'm' for megabytes, so '10m' is correct syntax.

2. Step 2: Check other options

   Uppercase 'MB' or 'M' and lowercase 'mb' are invalid or not recognized by nginx.

3. Final Answer:

   client_max_body_size 10m; -> Option D

4. Quick Check:

   Size suffix 'm' lowercase = B [OK]

Hint: Use lowercase 'm' for megabytes in nginx sizes [OK]

Common Mistakes:

• Using uppercase 'MB' or 'M' suffix
• Using 'mb' instead of 'm'
• Omitting the semicolon

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

proxy_set_body $request_body;
proxy_pass http://backend;

What will be forwarded to the backend server?

medium

A. The original client request body content

B. An empty body regardless of client data

C. The request headers only, no body

D. The request URI instead of the body

Solution

1. Step 1: Understand proxy_set_body $request_body;

   This directive sets the body sent to the backend to the original client request body.

2. Step 2: Effect on proxy_pass

   With this setting, the backend receives the exact data the client sent in the request body.

3. Final Answer:

   The original client request body content -> Option A

4. Quick Check:

   proxy_set_body $request_body forwards client body = A [OK]

Hint: proxy_set_body $request_body forwards client data [OK]

Common Mistakes:

• Assuming body is empty by default
• Confusing headers with body content
• Thinking URI is sent as body

4. You set client_max_body_size 5m; but clients still upload files larger than 5MB without errors. What is the most likely cause?

medium

A. The server has no disk space left

B. The client is ignoring nginx limits

C. The directive is set in the wrong context and not applied

D. The proxy_set_body directive is missing

Solution

1. Step 1: Check directive context

   client_max_body_size must be set in http, server, or location context to apply properly.

2. Step 2: Understand client behavior and other options

   Clients cannot bypass nginx limits; disk space or proxy_set_body do not affect this limit.

3. Final Answer:

   The directive is set in the wrong context and not applied -> Option C

4. Quick Check:

   Wrong context means limit ignored = C [OK]

Hint: Set client_max_body_size in correct context (http/server/location) [OK]

Common Mistakes:

• Blaming clients for ignoring limits
• Confusing proxy_set_body with size limits
• Ignoring directive placement

5. You want nginx to reject client requests with bodies larger than 2MB and forward the exact request body to a backend server. Which configuration snippet achieves this?

hard

A. client_max_body_size 2m;
proxy_set_body $request_body;
proxy_pass http://backend;

B. client_max_body_size 2m;
proxy_pass http://backend;
proxy_set_body $request_body

C. proxy_set_body $request_body;
client_max_body_size 2m;
proxy_pass http://backend

D. proxy_pass http://backend;
client_max_body_size 2m;
proxy_set_body $request_body

Solution

1. Step 1: Set size limit before proxying

   client_max_body_size 2m; must be declared to reject large bodies before proxying.

2. Step 2: Forward original body to backend

   proxy_set_body $request_body; ensures the backend receives the client data exactly.

3. Step 3: Correct order and syntax

   client_max_body_size 2m; proxy_set_body $request_body; proxy_pass http://backend; lists directives in proper order and syntax inside the location block.

4. Final Answer:

   client_max_body_size 2m; proxy_set_body $request_body; proxy_pass http://backend; -> Option A

5. Quick Check:

   Limit then forward body then proxy = A [OK]

Hint: Set size limit first, then proxy_set_body, then proxy_pass [OK]

Common Mistakes:

• Wrong directive order causing ignored limits
• Missing semicolons
• Not forwarding the request body properly