Retry policy that triggers when both status code and response header conditions are satisfied
#25,542 opened on Feb 14, 2023
Repository metrics
- Stars
- (27,997 stars)
- PR merge metrics
- (Avg merge 8d) (378 merged PRs in 30d)
Description
Current documentation highlights several ways to set up retries in the retry policy. Still, I can't seem to find an approach based on specific response headers AND specific status codes as a compound condition. retriable-status-codes and retriable-headers can be used together, in which case the retry would happen if either of these is satisfied.
I am looking for a way to retry the request only if a conjunction of response headers and status codes is true. I believe a response header counterpart to retriable_request_headers would work, as the documentation says that the headers there MUST be present for a retry to occur. For response headers though, I found only retriable-headers that trigger a retry whenever a header is matched, regardless of other conditions (in my case status codes). Did I miss something and there is a solution?