Proxy timeouts in Nginx - Step-by-Step Execution

Process Flow - Proxy timeouts

Client sends request

↓

Nginx receives request

↓

Nginx forwards request to backend

↓

Wait for backend response

↓

Timeout reached?

Yes→Return error to client

↓

Timeout reached?

No→Receive backend response

↓

Send response to client

Nginx receives a client request, forwards it to the backend server, waits for a response until a timeout occurs, then either returns the backend response or an error if timeout is reached.

Execution Sample

Nginx

proxy_connect_timeout 5s;
proxy_read_timeout 10s;
proxy_send_timeout 5s;

This config sets time limits for connecting, reading, and sending data to the backend server.

Process Table

Step	Action	Timeout Type	Timeout Value	Result
1	Client sends request	N/A	N/A	Request received by Nginx
2	Nginx tries to connect to backend	proxy_connect_timeout	5s	Connection established within 5s
3	Nginx sends request data to backend	proxy_send_timeout	5s	Data sent successfully within 5s
4	Nginx waits for backend response	proxy_read_timeout	10s	Response received within 10s
5	Nginx sends response to client	N/A	N/A	Response delivered successfully
6	If connection not established in 5s	proxy_connect_timeout	5s	Timeout error returned to client
7	If sending data exceeds 5s	proxy_send_timeout	5s	Timeout error returned to client
8	If backend response not received in 10s	proxy_read_timeout	10s	Timeout error returned to client

💡 Execution stops when response is sent to client or timeout error occurs.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
Connection Status	Not connected	Connected	Connected	Connected	Connected or Timeout Error
Data Sent Status	Not sent	Not sent	Sent	Sent	Sent or Timeout Error
Response Status	No response	No response	No response	Received	Received or Timeout Error

Key Moments - 3 Insights

Why does Nginx return a timeout error even if the backend server is up?

Because the timeout can occur at different stages: connection, sending data, or waiting for response. If any stage exceeds its timeout (see steps 6-8 in execution_table), Nginx returns an error.

What happens if the backend responds just before the proxy_read_timeout expires?

Nginx accepts the response and forwards it to the client successfully (see step 4 and 5 in execution_table). The timeout only triggers if the wait exceeds the configured time.

Can proxy_send_timeout cause a timeout if the backend is slow to receive data?

Yes, if sending data to the backend takes longer than proxy_send_timeout (step 7), Nginx returns a timeout error.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does Nginx check if the backend response timeout is reached?

A Step 4

B Step 2

C Step 6

D Step 3

💡 Hint

Check the 'Timeout Type' column for 'proxy_read_timeout' in execution_table step 4.

According to variable_tracker, what is the 'Connection Status' after step 2?

A Not connected

B Connected

C Timeout Error

D No response

💡 Hint

Look at the 'Connection Status' row and the 'After Step 2' column in variable_tracker.

If proxy_send_timeout is set to 3s instead of 5s, which step in execution_table would most likely change?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

proxy_send_timeout relates to sending data to backend, shown in step 3 of execution_table.

Concept Snapshot

Nginx proxy timeouts control how long Nginx waits at each stage:
- proxy_connect_timeout: max time to connect to backend
- proxy_send_timeout: max time to send request data
- proxy_read_timeout: max time to wait for backend response
If any timeout is exceeded, Nginx returns an error to client.

Full Transcript

This visual execution shows how Nginx handles proxy timeouts. When a client sends a request, Nginx tries to connect to the backend within proxy_connect_timeout. Then it sends data within proxy_send_timeout. Next, it waits for the backend response within proxy_read_timeout. If any of these steps take longer than their timeout, Nginx returns a timeout error to the client. Otherwise, it forwards the backend response. Variables like connection status, data sent status, and response status change step-by-step as shown. Key moments clarify common confusions about when timeouts happen and their effects.