HTTP 205 Reset Content vs 429 Too Many Requests
HTTP 205 (Reset Content) is a 2xx Success response, while 429 (Too Many Requests) is a 4xx Client Error response. 205 indicates that the server fulfilled the request and the client should reset the document view (e.g., clear a form). In contrast, 429 means that the user has sent too many requests in a given time (rate limiting). The response should include a Retry-After header.
Descrição
The server fulfilled the request and the client should reset the document view (e.g., clear a form).
Quando você o vê
After form submissions where the server wants the client to reset the form for new input.
Como corrigir
The client should clear the form or reset the view. Rarely used in practice.
Descrição
The user has sent too many requests in a given time (rate limiting). The response should include a Retry-After header.
Quando você o vê
When hitting API rate limits or making too many requests too quickly.
Como corrigir
Check the Retry-After header. Implement exponential backoff. Consider caching responses.
Diferenças principais
205 is a 2xx Success response, while 429 is a 4xx Client Error response.
HTTP 205: The server fulfilled the request and the client should reset the document view (e.g., clear a form).
HTTP 429: The user has sent too many requests in a given time (rate limiting). The response should include a Retry-After header.
You encounter 205 when after form submissions where the server wants the client to reset the form for new input.
You encounter 429 when when hitting API rate limits or making too many requests too quickly.
Quando usar qual
For 205 (Reset Content): The client should clear the form or reset the view. Rarely used in practice. For 429 (Too Many Requests): Check the Retry-After header. Implement exponential backoff. Consider caching responses.