Why does rate limiting throw HTTP 500 by default instead of HTTP 429? #58768
Answered
by
gfoidl
sander1095
asked this question in
Q&A
-
|
Question is based on this context |
Beta Was this translation helpful? Give feedback.
Answered by
gfoidl
Nov 3, 2024
Replies: 1 comment
-
|
By defaults it's HTTP 503 ( )HTTP 429 is for a specific client, whilst HTTP 503 is more "general". The framework can't know if it's client specific or not (depends on configuration of the rate limiter), thus 503 is used -- and therefore it's also configurable to set HTTP 429 if one knows it's client specific. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
sander1095
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
By defaults it's HTTP 503 (
aspnetcore/src/Middleware/RateLimiting/src/RateLimiterOptions.cs
Line 41 in 4ce2db7
HTTP 429 is for a specific client, whilst HTTP 503 is more "general". The framework can't know if it's client specific or not (depends on configuration of the rate limiter), thus 503 is used -- and therefore it's also configurable to set HTTP 429 if one knows it's client specific.