Streaming and chunked transfer in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding chunked transfer encoding in nginx

What does enabling chunked_transfer_encoding on; in nginx do?

A It caches the entire response on disk before sending it to the client.

B It compresses the response data before sending it to the client.

C It disables buffering of the response and sends it all at once after completion.

D It allows nginx to send response data in chunks without knowing the full content length beforehand.

💡 Hint

Think about how data can be sent when the total size is unknown.

Chunked transfer encoding allows nginx to send parts of the response as they are generated, without waiting for the full content length. This is useful for streaming data.

💻 Command Output

intermediate

Output of nginx log with chunked transfer

Given nginx is configured with chunked_transfer_encoding on; and serves a large file, what will the Content-Length header show in the response?

A No <code>Content-Length</code> header will be present; instead, <code>Transfer-Encoding: chunked</code> will be set.

B <code>Content-Length</code> will show the full size of the file in bytes.

C <code>Content-Length</code> will show zero.

D <code>Content-Length</code> will show the size of the first chunk only.

💡 Hint

Chunked transfer replaces the need for a content length header.

When chunked transfer encoding is used, the Content-Length header is omitted because the data is sent in chunks with their own size indicators.

❓ Configuration

advanced

Configuring nginx for streaming large files

Which nginx configuration snippet correctly enables streaming of large files using chunked transfer encoding?

A

location /files/ {
    proxy_pass http://backend;
    proxy_buffering on;
    chunked_transfer_encoding on;
}

B

location /files/ {
    proxy_pass http://backend;
    proxy_buffering on;
    chunked_transfer_encoding off;
}

C

location /files/ {
    proxy_pass http://backend;
    proxy_buffering off;
    chunked_transfer_encoding on;
}

D

location /files/ {
    proxy_pass http://backend;
    proxy_buffering off;
    chunked_transfer_encoding off;
}

💡 Hint

Streaming requires buffering off and chunked transfer enabled.

Disabling proxy_buffering allows data to be sent immediately. Enabling chunked_transfer_encoding allows sending data in chunks without full content length.

❓ Troubleshoot

advanced

Troubleshooting missing chunked transfer encoding

You enabled chunked_transfer_encoding on; in nginx, but clients still receive a Content-Length header and no chunked transfer. What is a likely cause?

A The client does not support chunked transfer encoding.

B The response is fully buffered by nginx because <code>proxy_buffering</code> is still enabled.

C The <code>chunked_transfer_encoding</code> directive is deprecated and ignored.

D The backend server is sending a <code>Transfer-Encoding</code> header that conflicts with nginx.

💡 Hint

Check if buffering is disabled to allow streaming.

If proxy_buffering is enabled, nginx waits for the full response before sending it, so chunked transfer encoding is not used.

🔀 Workflow

expert

Order of steps to enable streaming with chunked transfer in nginx

Arrange the steps in the correct order to enable streaming of dynamic content using chunked transfer encoding in nginx.

A 4,1,2,3

B 2,1,4,3

C 1,2,4,3

D 1,4,2,3

💡 Hint

Think about backend readiness before nginx settings and reload.

First, backend must send data in chunks. Then disable buffering and enable chunked transfer in nginx. Finally, reload nginx to apply changes.