Request body handling in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the effect of the directive 'client_max_body_size 1m;' in nginx?

Consider the nginx configuration snippet below:

client_max_body_size 1m;

What happens when a client sends a request body larger than 1 megabyte?

A nginx returns a 413 Request Entity Too Large error to the client.

B nginx silently truncates the request body to 1 megabyte and processes it.

C nginx accepts the full request body but logs a warning.

D nginx closes the connection without any response.

💡 Hint

Think about how nginx enforces limits on client request sizes.

The client_max_body_size directive sets the maximum allowed size of the client request body. If the client sends a body larger than this limit, nginx responds with a 413 error.

❓ Configuration

intermediate

How to configure nginx to save client request bodies to a specific directory?

You want nginx to save the full client request body to files in /var/tmp/nginx_body for later inspection. Which configuration snippet correctly enables this?

A client_body_save /var/tmp/nginx_body;

B client_body_directory /var/tmp/nginx_body;

C client_body_path /var/tmp/nginx_body;

D client_body_temp_path /var/tmp/nginx_body 1 2;

💡 Hint

Look for the directive that controls the temporary storage path for client request bodies.

The client_body_temp_path directive sets the directory where nginx stores temporary files for client request bodies. The numbers specify subdirectory levels for better file distribution.

❓ Troubleshoot

advanced

Why does nginx return a 400 Bad Request when client_body_buffer_size is too small?

Given this nginx configuration:

client_body_buffer_size 1k;

A client sends a POST request with a 2 KB body. nginx returns a 400 Bad Request error. Why?

A The buffer size is too small to hold the entire request body in memory, and nginx fails to buffer it properly.

B nginx does not support buffering request bodies larger than 1 KB.

C The client request body is corrupted, causing nginx to reject it.

D The 400 error is unrelated to buffer size and caused by a syntax error in the configuration.

💡 Hint

Consider how nginx buffers client request bodies before processing.

The client_body_buffer_size sets the size of the buffer used to read the client request body. If the body is larger than this buffer and nginx cannot write to disk (due to permissions or other issues), it may reject the request with a 400 error.

🔀 Workflow

advanced

Order the steps nginx follows to handle a client request body

Arrange the following steps in the correct order nginx processes a client request body:

A 2,1,4,3

B 1,2,3,4

C 1,4,2,3

D 1,2,4,3

💡 Hint

Think about how nginx validates size before reading the body.

nginx first checks if the body size exceeds the limit (1). If yes, it returns an error (4). Otherwise, it reads the body (2) and then passes it to the backend (3).

✅ Best Practice

expert

Which nginx configuration best prevents denial-of-service attacks via large request bodies?

You want to protect your nginx server from clients sending very large request bodies that could exhaust resources. Which configuration snippet is the best practice?

A client_max_body_size 10m; client_body_buffer_size 128k;

B client_max_body_size 1m; client_body_buffer_size 512k;

C client_max_body_size 100m; client_body_buffer_size 1m;

D client_max_body_size 0; client_body_buffer_size 64k;

💡 Hint

Consider reasonable limits to block very large bodies but allow normal usage.

Setting client_max_body_size to 1m limits request bodies to 1 megabyte, preventing very large uploads. A buffer size of 512k balances memory use and performance. Setting max size to 0 disables body reading, which breaks many applications.