HTTP 207 Multi-Status vs 429 Too Many Requests
HTTP 207 (Multi-Status) is a 2xx Success response, while 429 (Too Many Requests) is a 4xx Client Error response. 207 indicates that the response body contains status information for multiple resources, in situations where multiple status codes might be appropriate (WebDAV). 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.
Beschreibung
The response body contains status information for multiple resources, in situations where multiple status codes might be appropriate (WebDAV).
Wann Sie es sehen
In WebDAV operations that affect multiple resources simultaneously.
Wie man es behebt
Parse the XML body to check the status of each individual resource.
Beschreibung
The user has sent too many requests in a given time (rate limiting). The response should include a Retry-After header.
Wann Sie es sehen
When hitting API rate limits or making too many requests too quickly.
Wie man es behebt
Check the Retry-After header. Implement exponential backoff. Consider caching responses.
Wesentliche Unterschiede
207 is a 2xx Success response, while 429 is a 4xx Client Error response.
HTTP 207: The response body contains status information for multiple resources, in situations where multiple status codes might be appropriate (WebDAV).
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 207 when in WebDAV operations that affect multiple resources simultaneously.
You encounter 429 when when hitting API rate limits or making too many requests too quickly.
Wann welchen verwenden
For 207 (Multi-Status): Parse the XML body to check the status of each individual resource. For 429 (Too Many Requests): Check the Retry-After header. Implement exponential backoff. Consider caching responses.