Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

endpoint:80/sub is not recognized in grpcurl #489

Open
nptri opened this issue Oct 11, 2024 · 4 comments
Open

endpoint:80/sub is not recognized in grpcurl #489

nptri opened this issue Oct 11, 2024 · 4 comments

Comments

@nptri
Copy link

nptri commented Oct 11, 2024

Hi, I have a service endpoint as endpoint:80/subgrpc when I pass in whole grpcurl as this:

grpcurl -d '{body}' -H 'authorization: Bearer jwtKey'  -plaintext endpoint:80/subgrpc service/serviceName

return log as:

Failed to dial target host "endpoint:80/subgrpc": dial tcp: lookup tcp/80/serviceName: unknown port

Did I wrongly pass anything into the command ?

@gunters63
Copy link

gunters63 commented Nov 13, 2024

I have the same problem, our grpc service is reversed-proxied behind a path /grpc (port 443). How can I access that?

@gunters63
Copy link

Ah I think the reason is that we use grpc over HTTP/2 here so we can use REST paths. I guess grpcurl only support tcp.

@gunters63
Copy link

This can maybe closed as duplicate of #149

@nptri
Copy link
Author

nptri commented Nov 14, 2024

@gunters63 that I'm not sure since I'm a QA,
but in some script automation, I got some option to bypass by
Node.js: DefaultAuthority
Java: OverrideAuthority

Hope this help~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants