Re: [grpc-io] Rational behind mapping HTTP 429 to gRPC UNAVAILABLE

2024-10-16 Thread 'Ravi Kodippili' via grpc.io
> gRPC (currently) always uses 200 for RPC errors I wanted to confirm that servers should return a 200 HTTP status code regardless of gRPC status. I believe this is the case but I didn't find https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-HTTP2.md to be explicit about it. On Monday, Oct

Re: [grpc-io] Rational behind mapping HTTP 429 to gRPC UNAVAILABLE

2024-10-16 Thread 'Michael Lumish' via grpc.io
In the responses section of that protocol doc ( https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-HTTP2.md#responses), the "HTTP-Status" production is exactly the string ":status 200". This explicitly means that gRPC servers must always return a HTTP status code of 200 in any gRPC response. On