Configuring Gateway gRPC Options
In order to serve gRPC-Web clients, the server must first transcode the message into a format that the web client can understand details. Gloo Edge configures Envoy to do this by default. If you would like to disable this behavior, you can do so by editing the gateway Custom Resource for the Gateway you would like to alter.
The relevant section of the gateway CR is highlighted below.
apiVersion: gateway.solo.io/v1 kind: Gateway metadata: # collapsed for brevity spec: bindAddress: '::' bindPort: 8080 httpGateway: options: grpcWeb: disable: true useProxyProto: false status: # collapsed for brevity
For more information on how to edit the gateway CR, take a look at the listener configuration guide. You may also want to take a look at the Envoy docs regarding the use of gRPC with Envoy.