Proxy buffering in Nginx - Step-by-Step Execution

Process Flow - Proxy buffering

Client sends request

↓

Nginx receives request

↓

Check proxy_buffering setting

↓

Buffer response

↓

Send buffered

↓

response to client

↓

End

Nginx receives a client request and checks if proxy buffering is enabled. If yes, it buffers the response from the backend before sending it to the client; if no, it streams the response directly.

Execution Sample

Nginx

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

This config proxies requests to a backend server with buffering enabled, so responses are buffered before sending to clients.

Process Table

Step	Action	proxy_buffering	Response Handling	Client Output
1	Client sends request to Nginx	on	Waiting for backend response	No output yet
2	Nginx forwards request to backend	on	Receiving response chunks	No output yet
3	Nginx buffers response chunks	on	Buffering data internally	No output yet
4	Buffer full or response complete	on	Send buffered response to client	Client receives full buffered response
5	Request complete	on	Close connection or wait for next	Client has full response

💡 Response fully buffered and sent to client, request cycle ends

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
proxy_buffering	on	on	on	on	on
buffered_data	empty	partial chunks	full response	sent to client	empty
client_output	none	none	none	full response	full response

Key Moments - 2 Insights

Why does Nginx wait before sending data to the client when proxy_buffering is on?

Because with proxy_buffering on, Nginx collects response data in a buffer first (see execution_table step 3), then sends it all at once to improve performance and reduce client-side delays.

What happens if proxy_buffering is off?

Nginx streams data directly to the client as it receives it from the backend, without waiting to buffer (not shown in this table but implied by the 'No' branch in concept_flow).

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what is Nginx doing with the response?

A Sending response directly to client

B Waiting for client request

C Buffering response chunks internally

D Closing connection

💡 Hint

Check the 'Response Handling' column at step 3 in execution_table

At which step does the client start receiving the full buffered response?

A Step 4

B Step 3

C Step 2

D Step 5

💡 Hint

Look at the 'Client Output' column in execution_table

If proxy_buffering was set to off, how would the 'Response Handling' change at step 3?

A Nginx would buffer response chunks internally

B Nginx would stream response directly to client

C Nginx would wait for full response before sending

D Nginx would drop the response

💡 Hint

Refer to concept_flow where 'No' branch for proxy_buffering leads to streaming response

Concept Snapshot

proxy_buffering in nginx controls if responses from backend are buffered before sending to clients.
When on, nginx collects response data fully or in chunks before sending.
When off, nginx streams data directly to clients as it arrives.
Buffering improves performance and reduces client wait times.
Set with 'proxy_buffering on;' inside location or server blocks.

Full Transcript

Proxy buffering in nginx means nginx can hold the backend server's response in a temporary storage called a buffer before sending it to the client. When a client sends a request, nginx forwards it to the backend. If proxy_buffering is on, nginx collects the response data in chunks and stores it internally. Once the buffer is full or the response is complete, nginx sends the entire buffered response to the client. This helps improve performance and reduce delays. If proxy_buffering is off, nginx streams the response directly to the client without waiting. This visual trace shows each step from receiving the request, buffering the response, and finally sending it to the client.