Proxy timeouts in Nginx - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of proxy timeouts in nginx?

Proxy timeouts control how long nginx waits for responses from a backend server before giving up. They help avoid hanging connections and improve reliability.

beginner

Which nginx directive sets the timeout for establishing a connection with the proxied server?

proxy_connect_timeout sets the maximum time nginx waits to connect to the backend server.

beginner

What does proxy_read_timeout control in nginx?

proxy_read_timeout sets how long nginx waits to receive data from the backend server after the connection is established.

intermediate

How does proxy_send_timeout affect nginx proxy behavior?

proxy_send_timeout defines the timeout for sending a request to the backend server. If nginx cannot send data in this time, it closes the connection.

intermediate

Why is it important to configure proxy timeouts properly in nginx?

Proper proxy timeouts prevent nginx from waiting too long on slow or unresponsive backend servers, improving user experience and resource use.

Which directive controls how long nginx waits to connect to a backend server?

A proxy_connect_timeout

B proxy_read_timeout

C proxy_send_timeout

D proxy_pass

proxy_connect_timeout sets the time nginx waits to establish a connection with the backend server.

What happens if proxy_read_timeout is reached before the backend sends data?

A Nginx waits indefinitely

B Nginx retries the request automatically

C Nginx sends a new request

D Nginx closes the connection and returns an error

If the backend does not send data within proxy_read_timeout, nginx closes the connection and returns an error to the client.

Which timeout controls how long nginx waits to send data to the backend?

A proxy_connect_timeout

B client_body_timeout

C proxy_send_timeout

D proxy_read_timeout

proxy_send_timeout sets the timeout for sending data to the backend server.

If a backend server is very slow, what is a good practice regarding proxy timeouts?

A Set timeouts to zero to wait forever

B Set reasonable timeouts to balance wait and fail fast

C Set timeouts too low to avoid waiting

D Disable timeouts completely

Setting reasonable timeouts helps nginx wait enough for slow servers but also fail fast if the server is unresponsive.

Which directive is NOT related to proxy timeouts in nginx?

A proxy_cache_path

B proxy_connect_timeout

C proxy_send_timeout

D proxy_read_timeout

proxy_cache_path is for caching, not timeouts.

Explain the roles of proxy_connect_timeout, proxy_read_timeout, and proxy_send_timeout in nginx proxy configuration.

Think about connection, sending, and receiving phases.

Why should you avoid setting proxy timeouts too high or too low in nginx?

Consider user experience and server responsiveness.

Practice

1. What does the proxy_connect_timeout directive control in Nginx?

easy

A. The time Nginx waits to receive the full response from the backend

B. The time Nginx waits to send the full request to the backend

C. The time Nginx waits to establish a connection with the backend server

D. The time Nginx caches the response from the backend

Solution

1. Step 1: Understand proxy_connect_timeout purpose

   This directive sets how long Nginx waits to connect to the backend server before giving up.

2. Step 2: Differentiate from other timeouts

   proxy_send_timeout controls sending request time, proxy_read_timeout controls response wait time, so they are different.

3. Final Answer:

   The time Nginx waits to establish a connection with the backend server -> Option C

4. Quick Check:

   proxy_connect_timeout = connection wait time [OK]

Hint: Connect timeout is for establishing backend connection only [OK]

Common Mistakes:

• Confusing connect timeout with read or send timeout
• Thinking it controls response wait time
• Assuming it caches responses

2. Which of the following is the correct syntax to set a 10-second proxy read timeout in Nginx?

easy

A. proxy_read_timeout 10;

B. proxy_read_timeout 10s;

C. proxy_read_timeout = 10s;

D. proxy_read_timeout: 10s;

Solution

1. Step 1: Recall Nginx timeout syntax

   Timeout values are set as numbers with optional time units, but seconds are default so '10' means 10 seconds.

2. Step 2: Check syntax correctness

   Correct syntax is proxy_read_timeout 10; without '=' or ':' and without 's' suffix.

3. Final Answer:

   proxy_read_timeout 10; -> Option A

4. Quick Check:

   Timeouts use number only, no '=' or ':' [OK]

Hint: Use number only for seconds, no '=' or ':' in directives [OK]

Common Mistakes:

• Adding '=' sign which is invalid
• Using ':' instead of space
• Adding 's' suffix which is not required

3. Given this Nginx config snippet:

location /api/ {
  proxy_pass http://backend;
  proxy_connect_timeout 5;
  proxy_send_timeout 10;
  proxy_read_timeout 15;
}

What happens if the backend server takes 20 seconds to send the full response?

medium

A. Nginx closes connection after 10 seconds waiting to send request

B. Nginx closes connection after 5 seconds trying to connect

C. Nginx waits indefinitely for the backend response

D. Nginx closes connection after 15 seconds waiting for response

Solution

1. Step 1: Identify relevant timeout for response wait

   proxy_read_timeout controls how long Nginx waits for the backend to send the full response.

2. Step 2: Compare backend response time with proxy_read_timeout

   Backend takes 20 seconds, proxy_read_timeout is 15 seconds, so Nginx closes the connection after 15 seconds.

3. Final Answer:

   Nginx closes connection after 15 seconds waiting for response -> Option D

4. Quick Check:

   Response wait = proxy_read_timeout = 15 [OK]

Hint: Response wait time controlled by proxy_read_timeout [OK]

Common Mistakes:

• Confusing send timeout with read timeout
• Assuming connect timeout applies to response wait
• Thinking Nginx waits forever

4. You set proxy_connect_timeout 10; but Nginx still times out connecting to backend after 5 seconds. What is the likely cause?

medium

A. The backend server is closing connections early

B. There is a lower timeout set by proxy_connect_timeout in a lower-level block

C. Nginx ignores proxy_connect_timeout and uses default 5 seconds

D. The proxy_connect_timeout directive is misspelled

Solution

1. Step 1: Understand directive inheritance in Nginx

   Timeout directives can be set at multiple levels; lower-level settings override higher-level ones.

2. Step 2: Identify cause of shorter timeout

   If a lower-level block has a 5-second timeout, it overrides the 10-second setting.

3. Final Answer:

   There is a lower timeout set by proxy_connect_timeout in a lower-level block -> Option B

4. Quick Check:

   Timeouts can be overridden by lower-level config [OK]

Hint: Check for overriding timeouts in child blocks [OK]

Common Mistakes:

• Assuming Nginx ignores the directive
• Blaming backend without checking config
• Misspelling directive (would cause error, not timeout)

5. You want Nginx to wait up to 20 seconds to connect to backend, 30 seconds to send the request, and 40 seconds to receive the response. Which configuration snippet correctly sets these timeouts?

hard

A. proxy_connect_timeout 20;
proxy_send_timeout 30;
proxy_read_timeout 40;

B. proxy_connect_timeout 20s;
proxy_send_timeout 30s;
proxy_read_timeout 40s;

C. proxy_connect_timeout=20;
proxy_send_timeout=30;
proxy_read_timeout=40;

D. proxy_connect_timeout: 20;
proxy_send_timeout: 30;
proxy_read_timeout: 40;

Solution

1. Step 1: Recall correct syntax for timeout directives

   Timeouts are set as directive name followed by a space and number (seconds), ending with semicolon; no '=' or ':' or 's' suffix needed.

2. Step 2: Validate each option

   proxy_connect_timeout 20; proxy_send_timeout 30; proxy_read_timeout 40; uses correct syntax; A uses ':'; B adds unnecessary 's'; C uses '='.

3. Final Answer:

   proxy_connect_timeout 20; proxy_send_timeout 30; proxy_read_timeout 40; -> Option A

4. Quick Check:

   Use number only with semicolon, no '=' or ':' [OK]

Hint: Timeouts use number only, no '=' or ':' [OK]

Common Mistakes:

• Adding 's' suffix to numbers
• Using '=' or ':' instead of space
• Missing semicolon at line end