[Solved] A REST API returns this response when rate limit is exceeded: HTTP/1.1 429 Too Many Requests Content-Type: application/json {"error": "Too many requests"} What is missing to improve client handling? | Rest API

Rest API - Error Handling

A REST API returns this response when rate limit is exceeded:

HTTP/1.1 429 Too Many Requests
Content-Type: application/json

{"error": "Too many requests"}

What is missing to improve client handling?

AA Retry-After header indicating when to retry

BChanging status code to 500

CAdding Authorization header

DRemoving the error message

Step-by-Step Solution

Solution:

Step 1: Identify missing headers for rate limit response
The response lacks the Retry-After header, which helps clients know when to retry.
Step 2: Understand why Retry-After is important
Without Retry-After, clients may retry too soon, causing more errors or confusion.
Final Answer:
A Retry-After header indicating when to retry -> Option A
Quick Check:
Retry-After header missing = add it [OK]

Quick Trick: Add Retry-After header to guide client retry timing [OK]

Common Mistakes:

MISTAKES

Master "Error Handling" in Rest API

9 interactive learning modes - each teaches the same concept differently

More Rest API Quizzes

A REST API returns this response when rate limit is exceeded: