HTTP 429, 502, 503, 504 get mapped to UNAVAILABLE, for the retry policy to observe.
https://github.com/grpc/grpc/blob/master/doc/http-grpc-status-mapping.md On Fri, Jul 11, 2025 at 8:55 AM Leon Lindeberg <[email protected]> wrote: > Hi! Should gRPC clients implement an HTTP-level resilience handler to > retry HTTP 5xx/429? Or should those responses make sure to return a gRPC > status code so that the gRPC RetryPolicy handles it instead? > > -- > You received this message because you are subscribed to the Google Groups " > grpc.io" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/grpc-io/1559e628-c678-40d4-888b-bfdce3ac0f74n%40googlegroups.com > <https://groups.google.com/d/msgid/grpc-io/1559e628-c678-40d4-888b-bfdce3ac0f74n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/grpc-io/CA%2B4M1oP5QqrzKP9P4VspVTNSxJuO0i4cFGxxsuPM72hFDBPDLg%40mail.gmail.com.
smime.p7s
Description: S/MIME Cryptographic Signature
