You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Handle non-200 status codes more gracefully (#1613)
Motivation:
Accepted RPCs should have a 200 HTTP response status code. gRPC knows
how to handle some non-200 status codes and can synthesize a gRPC status
from them. At the moment they are treated as errors and later converted
to a gRPC status. However this means that only the gRPC status sees the
error as a status: other response parts (e.g. the response stream) see
an error relating to invalid HTTP response codes rather than the
synthesized status.
Modifications:
- Handle non-200 HTTP status codes more gracefully by turning them into
a gRPC status where possible.
Results:
- Non-200 status codes are more readily converted to a gRPC status.
0 commit comments