FlyTOmeLight commented on issue #9240:
URL: https://github.com/apache/apisix/issues/9240#issuecomment-1500527726

   > > > rewriting the url of grpc request in proxy-rewrite pluing is not 
supported yet.
   > > > And do you set a correct grpc port of the upstream?
   > > 
   > > 
   > > @kingluo When will it be supported? Do you have any plan to support it? 
Also, do you have any recommended ways to proxy gRPC services?
   > 
   > Yes, we will handle it soon later.
   > 
   > But IMO, changing the URI is not a good practice for grpc requests and 
seems unnecessary. The format of grpc URI is `/package.service/method`, almost 
all official libraries from main programming langs, e.g. golang, will generate 
such URI automatically and disallow changing. So it's less possible to generate 
a non-standard URI like prefixing. So I am wondering why we need to change it.
   
   I feel like you may have misunderstood my meaning. What we need is to use 
Apisix to proxy the gRPC service endpoint, for example, our original endpoint 
is 127.0.0.1:8100 and the http/2 port of Apisix is 127.0.0.1:8002. We want to 
use 127.0.0.1:8002/xxx/grpc to proxy out the endpoint 127.0.0.1:8100, and it is 
not necessary to rewrite the gRPC method. The above bug is a problem 
encountered during the proxy, Apisix often reports the upstream error, it is 
unstable, sometimes successful and sometimes failed. I guess it may be a bug, 
can you understand my meaning?  @kingluo 
   <img width="806" alt="image" 
src="https://user-images.githubusercontent.com/41530068/230658763-8ebee428-03fd-4d1b-8bbb-e700278dc664.png";>
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to