Replies: 1 comment 1 reply
-
There's some previous discussion of this in #584. The current solution is to provide your own implementation of the Can you share a little more about why you consider this sensitive? The service name is already in the URL - that's part of both the gRPC and Connect protocols. In most cases, the server also distributes schemas and/or generated client code, so the name of the request message isn't sensitive either. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When the client sends a request that does not conform to the Protobuf schema, internal service names and other details are exposed in the error message.
Example
For instance, when making an invalid JSON request in Connect RPC, the error message is as follows:
Question
Is there a way to prevent internal information like
*foov1.BarServiceLoginRequest
from being exposed in error messages?Beta Was this translation helpful? Give feedback.
All reactions