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
I had searched in the issues and found no similar feature requirement.
Description
We use grpc-gateway to expose HTTP service. Currently, for any errors, it returns HTTP 500 code and user may need to unpack the error message and parse .code to understand the detail problem. This brings challenges to system integration, we would like to keep our self-define code there. At the same time, it's better for us to expose common used codes like 401, 404, 405 directly for upstream system to interact with.
Should be 404
Should be 401
Use case
Use for system integration
Related issues
No response
Are you willing to submit a PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered:
Search before asking
Description
We use grpc-gateway to expose HTTP service. Currently, for any errors, it returns HTTP 500 code and user may need to unpack the error message and parse
.code
to understand the detail problem. This brings challenges to system integration, we would like to keep our self-define code there. At the same time, it's better for us to expose common used codes like 401, 404, 405 directly for upstream system to interact with.Should be 404
Should be 401
Use case
Use for system integration
Related issues
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: