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.

Practice

1. What is the main purpose of enabling chunked transfer encoding in nginx streaming?

easy

A. To block the client from receiving partial data

B. To compress all data before sending it to the client

C. To send data in smaller parts so the client can start processing early

D. To cache the entire response before sending it

Solution

1. Step 1: Understand chunked transfer encoding

   Chunked transfer encoding breaks the response into smaller pieces called chunks.

2. Step 2: Identify the benefit in streaming

   This allows the client to start receiving and processing data immediately without waiting for the full response.

3. Final Answer:

   To send data in smaller parts so the client can start processing early -> Option C

4. Quick Check:

   Chunked transfer = send data in parts [OK]

Hint: Chunked transfer means sending data in parts, not all at once [OK]

Common Mistakes:

• Thinking chunked transfer compresses data
• Assuming chunked transfer caches full response
• Believing chunked transfer blocks partial data

2. Which nginx directive disables response buffering to enable streaming with chunked transfer?

easy

A. proxy_buffering off;

B. chunked_transfer on;

C. streaming_enable yes;

D. buffer_response off;

Solution

1. Step 1: Identify the directive for buffering control

   In nginx, proxy_buffering controls whether responses are buffered.

2. Step 2: Find the correct syntax to disable buffering

   Setting proxy_buffering off; disables buffering, allowing streaming.

3. Final Answer:

   proxy_buffering off; -> Option A

4. Quick Check:

   Disable buffering = proxy_buffering off [OK]

Hint: Disable buffering with 'proxy_buffering off;' in nginx config [OK]

Common Mistakes:

• Using non-existent directives like chunked_transfer
• Confusing buffering with streaming_enable
• Wrong syntax like buffer_response off

3. Given this nginx config snippet:

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

What will happen when a client requests /stream?

medium

A. Client receives the full response only after backend finishes sending

B. Client receives data in chunks as backend sends it

C. Client connection will be refused due to syntax error

D. Client receives compressed data without chunking

Solution

1. Step 1: Analyze proxy_buffering off;

   This disables buffering, so nginx forwards data immediately.

2. Step 2: Analyze chunked_transfer_encoding on;

   This enables chunked transfer encoding, sending data in parts.

3. Final Answer:

   Client receives data in chunks as backend sends it -> Option B

4. Quick Check:

   Buffering off + chunked on = streaming chunks [OK]

Hint: Buffering off + chunked on means streaming chunks to client [OK]

Common Mistakes:

• Assuming full response is buffered before sending
• Thinking config has syntax errors
• Confusing chunked transfer with compression

4. You configured nginx with:

proxy_buffering off;
chunked_transfer_encoding off;

But streaming is slow and client waits for full response. What is the likely issue?

medium

A. Missing gzip on directive slows down streaming

B. proxy_buffering off causes buffering and delays streaming

C. proxy_pass directive is missing, so no backend connection

D. chunked_transfer_encoding off disables chunked streaming, causing delay

Solution

1. Step 1: Understand effect of chunked_transfer_encoding off;

   Disabling chunked transfer means data is sent as one block, not in parts.

2. Step 2: Analyze impact on streaming

   Without chunked transfer, client waits for full response before receiving data, causing delay.

3. Final Answer:

   chunked_transfer_encoding off disables chunked streaming, causing delay -> Option D

4. Quick Check:

   Chunked off = no streaming chunks [OK]

Hint: Chunked transfer must be on for streaming, else client waits [OK]

Common Mistakes:

• Thinking proxy_buffering off causes buffering
• Assuming gzip affects chunked streaming
• Ignoring missing proxy_pass as cause

5. You want to stream a live video feed through nginx using chunked transfer. Which combination of directives correctly enables streaming with chunked transfer and disables buffering?

hard

A. proxy_buffering off; chunked_transfer_encoding on;

B. proxy_buffering on; chunked_transfer_encoding off;

C. proxy_buffering off; chunked_transfer_encoding off;

D. proxy_buffering on; chunked_transfer_encoding on;

Solution

1. Step 1: Disable buffering for immediate data forwarding

   Set proxy_buffering off; to prevent nginx from waiting to buffer full response.

2. Step 2: Enable chunked transfer encoding for partial data sending

   Set chunked_transfer_encoding on; to send data in chunks to the client.

3. Final Answer:

   proxy_buffering off; chunked_transfer_encoding on; -> Option A

4. Quick Check:

   Disable buffering + enable chunked = streaming [OK]

Hint: Disable buffering and enable chunked transfer for streaming [OK]

Common Mistakes:

• Enabling buffering blocks streaming
• Disabling chunked transfer stops chunked sending
• Mixing buffering and chunked transfer settings incorrectly