Hi, Currently, looks like rpc urls are generated in the form of /<package name>/<rpc name>. Is there a way to prefix the urls such that grpc client could call <fixed prefix>/<package name>/<rpc name>? The receiver can chop off the prefix and call the correct rpc.
Use case: We'd like to have a proxy sitting between our client and grpc server. The proxy will serve multiple clients. So a client could call ourdomain.com/<something specific to client>/<package name>/<rpc name>. The proxy will chop off <something specific to client> and reroute the rpc to correct handling instance. One option to do it would be via custom header but was wondering if url prefixing has been thought of/brought up before? Thanks. -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/65e47a3f-c51e-4d34-b6a0-601badd8091f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
