Retry policy that triggers when both status code and response header conditions are satisfied
- Dominant language
- C++
- Stars
- 28.9k
- Forks
- 5.6k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 437
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?
Contributor guide
Assessment
This issue has not been assessed yet.