OrTransientHttpError should also consider HTTP 429 (too many requests)?
opened this issue · comments
There is a rationale behind the fact that OrTransientHttpError is not considering HTTP 429 as a transient error?
HTTP 429 (too many requests) is the correct error reply in case of throttling. I think it's a good case where we want to retry a request a little bit later (maybe with an exponential backoff).
I'd also add that it would be good to adhere to the Retry-After
header, if present on a 429
response.