fullstorydev / fullstorydev/grpcui
Asking for path prefix option to support grpc services behind reverse-proxies
- Dominant language
- JavaScript
- Stars
- 5.9k
- Forks
- 427
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 7
Description
Is it possible to add the capability to specify a service call path prefix? Since current address field seems to not support paths as part of host, port string. This would be useful in cases where the actual service is served behind a reverse proxy, YARP, for instance, and the routing is done by service call contract's path prefix. This would also allow the grpcui to access reflection serving there. I'm aware of a base-path option already which seems to address the same issue with the GUI itself.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing how the address field is parsed and how the existing base-path option is handled. Determine how a service call path prefix should be represented for gRPC services behind a reverse proxy, including reflection access, and define completion by successful proxied service and reflection requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100