Closed withsmilo closed 3 years ago
I think that's the expected behavior for the gRPC endpoints right now. Did you run into a use-case that you want to have the prefix for the gRPC endpoints?
@yubozhao Yes. I'd like to run the YataiService behind a reverse proxy server. Is it impossible?
It is definitely possible. That PR only added the support for the prefix on web UI. We will need to add the prefix support for the gRPC endpoints.
Is this a blocking issue for you right now?
@yubozhao It is not a blocking issue for me, but I think it is a necessary function for security.
Yes, that makes sense. I will add this to the roadmap and we will try to get this address in the next few releases
Thanks, @yubozhao !
@withsmilo I thought the URL prefix was only meant for the browser when deploying a web server behind a proxy, gRPC should just work behind a reverse proxy without problem.
@parano You're right. It works without any problem, but there is a security problem that exposes gRPC server's port to users.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug
When I run YataiService with
--web-prefix-path
option, the YataiService gRPC server doesn't have a prefix path. I think https://github.com/bentoml/BentoML/issues/1063 missed this bug.To Reproduce
Expected behavior
The YataiService gRPC server should be executed on
127.0.0.1:50051/test_prefix
.Screenshots/Logs
Environment:
Additional context