You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is common that is users are exposing something over HTTP that they want to expose it using the same HTTP listener as everything else i.e. Undertow.
At the core gRPC is well defined messages making use of HTTP/2 - could these be intercepted and passed over the the gRPC server?
The path information sounds like it is /service name/method name so unless we deployed and used the service name to register with Undertow we may need to consider should be on the root context (like our HTTP upgrade support) - however the content-type would be application/grpc which maybe we could detect early in the request handling flow.
The text was updated successfully, but these errors were encountered:
It is common that is users are exposing something over HTTP that they want to expose it using the same HTTP listener as everything else i.e. Undertow.
At the core gRPC is well defined messages making use of HTTP/2 - could these be intercepted and passed over the the gRPC server?
The path information sounds like it is /service name/method name so unless we deployed and used the service name to register with Undertow we may need to consider should be on the root context (like our HTTP upgrade support) - however the content-type would be application/grpc which maybe we could detect early in the request handling flow.
The text was updated successfully, but these errors were encountered: