[Solved] Given this HTTP response:HTTP/1.1 429 Too Many Requests Retry-After: 60What should the client do next? | Rest API

Rest API - Error Handling

Given this HTTP response:

HTTP/1.1 429 Too Many Requests
Retry-After: 60

What should the client do next?

AWait 60 seconds before retrying

BImmediately retry the request

CIgnore the Retry-After header and retry later

DSend authentication credentials

Step-by-Step Solution

Solution:

Step 1: Understand the meaning of 429 status and Retry-After header
429 means too many requests; Retry-After tells how long to wait before retrying.
Step 2: Determine correct client behavior
The client should wait the specified 60 seconds before sending another request to avoid further errors.
Final Answer:
Wait 60 seconds before retrying -> Option A
Quick Check:
Client waits Retry-After seconds before retry [OK]

Quick Trick: Respect Retry-After time before retrying requests [OK]

Common Mistakes:

MISTAKES

Master "Error Handling" in Rest API

9 interactive learning modes - each teaches the same concept differently

More Rest API Quizzes

Given this HTTP response: