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
Is there some difference between how headers are passed in grpcui compared to grpcurl?
Using grpcurl:
% grpcurl -plaintext -H "my-token:$MY_TOKEN" <ip>:30080 list
gateway.Gateway
grpc.reflection.v1alpha.ServerReflection
Using grpcui:
% grpcui -plaintext -H "my-token:$MY_TOKEN" <ip>:30080
Failed to compute set of methods to expose: rpc error: code = Unauthenticated desc = No auth token present
The text was updated successfully, but these errors were encountered:
Not sure why it's needed though. The docs for -H say: "These headers will also be included in reflection requests to a server." /shrug
Will leave this issue open for clarification.
Is there some difference between how headers are passed in grpcui compared to grpcurl?
Using grpcurl:
Using grpcui:
The text was updated successfully, but these errors were encountered: