Retry-After header in Rest API - Time & Space Complexity

Time Complexity: Retry-After header

O(n)

Understanding Time Complexity

When using the Retry-After header in REST APIs, it's important to understand how the server handles repeated requests over time.

We want to know how the number of retries affects the server's processing time.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// Pseudocode for handling Retry-After header
function handleRequest(request) {
  if (serverIsBusy()) {
    return response(503, { 'Retry-After': 10 });
  } else {
    return processRequest(request);
  }
}
    

This code checks if the server is busy and, if so, tells the client to retry after 10 seconds. Otherwise, it processes the request immediately.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The client retries sending the request after waiting the specified time.
• How many times: Depends on how many times the server responds with Retry-After before processing succeeds.

How Execution Grows With Input

Each retry causes the server to handle the request again, increasing total processing time linearly with the number of retries.

Number of Retries (n)	Approx. Server Handling Operations
1	1 request handling
5	5 request handlings
10	10 request handlings

Pattern observation: The total work grows directly with the number of retries.

Final Time Complexity

Time Complexity: O(n)

This means the total time the server spends grows linearly with the number of retry attempts.

Common Mistake

[X] Wrong: "The Retry-After header makes the server handle all retries instantly without extra cost."

[OK] Correct: Each retry is a new request the server must process, so the total work adds up with each retry.

Interview Connect

Understanding how retry mechanisms affect server load helps you design APIs that handle traffic smoothly and avoid overload.

Self-Check

What if the Retry-After header used exponential backoff instead of a fixed time? How would the time complexity change?

Practice

1.

What is the main purpose of the Retry-After header in REST APIs?

easy

A. To provide the client's IP address to the server

B. To specify the content type of the response

C. To tell the client how long to wait before making another request

D. To indicate the server's current time

Solution

1. Step 1: Understand the role of Retry-After header

   The Retry-After header is used by servers to tell clients when they can retry a request after being told to wait.

2. Step 2: Match purpose with options

   To tell the client how long to wait before making another request correctly states that it tells the client how long to wait before retrying, which matches the header's purpose.

3. Final Answer:

   To tell the client how long to wait before making another request -> Option C

4. Quick Check:

   Retry-After = wait time before retry [OK]

Hint: Retry-After tells when to retry, not server info [OK]

Common Mistakes:

• Confusing Retry-After with content type headers
• Thinking Retry-After provides server time
• Assuming Retry-After sends client info

2.

Which of the following is a correct example of the Retry-After header syntax?

Retry-After: ?

easy

A. Wed, 21 Oct 2015 07:28:00 GMT

B. "120 seconds"

C. 120 seconds

D. After 2 minutes

Solution

1. Step 1: Review Retry-After header formats

   Retry-After accepts either a number of seconds (integer) or a HTTP-date string.

2. Step 2: Check each option

   120 seconds includes invalid text; "120 seconds" incorrectly quotes the number with text; Wed, 21 Oct 2015 07:28:00 GMT is a valid HTTP-date format; After 2 minutes is not a valid format.

3. Final Answer:

   Wed, 21 Oct 2015 07:28:00 GMT -> Option A

4. Quick Check:

   Retry-After = seconds or HTTP-date [OK]

Hint: Retry-After uses seconds or HTTP-date format only [OK]

Common Mistakes:

• Adding quotes around seconds value
• Using natural language like 'After 2 minutes'
• Using invalid date formats

3.

Given the following HTTP response header:

HTTP/1.1 503 Service Unavailable
Retry-After: 60

What should the client do?

medium

A. Wait 60 seconds before retrying the request

B. Retry the request immediately

C. Ignore the Retry-After header and retry after 5 seconds

D. Abort the request permanently

Solution

1. Step 1: Interpret the Retry-After header value

   The header value '60' means the client should wait 60 seconds before retrying.

2. Step 2: Match client action to header instruction

   Wait 60 seconds before retrying the request correctly instructs to wait 60 seconds before retrying, which follows the server's guidance.

3. Final Answer:

   Wait 60 seconds before retrying the request -> Option A

4. Quick Check:

   Retry-After: 60 means wait 60 seconds [OK]

Hint: Retry-After number means wait that many seconds [OK]

Common Mistakes:

• Retrying immediately ignoring Retry-After
• Assuming Retry-After is in milliseconds
• Treating Retry-After as a permanent failure

4.

Identify the error in this HTTP response header snippet:

HTTP/1.1 429 Too Many Requests
Retry-After: "30 seconds"

medium

A. The header name should be lowercase

B. Retry-After value should not be quoted or include text

C. Retry-After header is missing

D. Status code 429 is invalid

Solution

1. Step 1: Check Retry-After header format

   The Retry-After header must be either an integer number of seconds or a valid HTTP-date string without quotes or extra text.

2. Step 2: Identify the error in the given header

   The value "30 seconds" is quoted and includes text, which is invalid syntax.

3. Final Answer:

   Retry-After value should not be quoted or include text -> Option B

4. Quick Check:

   Retry-After must be seconds or date, no quotes/text [OK]

Hint: Retry-After value is raw seconds or date, no quotes [OK]

Common Mistakes:

• Adding quotes around Retry-After value
• Including descriptive text in Retry-After
• Confusing header case sensitivity

5.

A server wants to tell clients to retry after 2 minutes using the Retry-After header. Which is the best way to set this header to ensure compatibility?

hard

A. Retry-After: Wed, 21 Oct 2030 07:28:00 GMT (current time + 2 minutes)

B. Retry-After: "120 seconds"

C. Retry-After: After 2 minutes

D. Retry-After: 120

Solution

1. Step 1: Understand Retry-After header formats

   Retry-After accepts either an integer number of seconds or a valid HTTP-date string.

2. Step 2: Evaluate options for compatibility

   Retry-After: 120 uses integer seconds (120) which is simple and widely supported. Retry-After: "120 seconds" incorrectly quotes and adds text. Retry-After: Wed, 21 Oct 2030 07:28:00 GMT (current time + 2 minutes) uses a date but must be exact and updated dynamically, which is complex. Retry-After: After 2 minutes is invalid text.

3. Final Answer:

   Retry-After: 120 -> Option D

4. Quick Check:

   Use seconds as integer for simple Retry-After [OK]

Hint: Use integer seconds for Retry-After to ensure compatibility [OK]

Common Mistakes:

• Adding quotes or text to seconds value
• Using a fixed date without updating
• Writing natural language instead of valid format