gRPC HTTP/1.1 Reverse Bridge¶
This documentation is for the Envoy v3 API.
As of Envoy v1.18 the v2 API has been removed and is no longer supported.
If you are upgrading from v2 API config you may wish to view the v2 API documentation:
This extension may be referenced by the qualified name
This extension is functional but has not had substantial production burn time, use only with this caveat.
This extension has an unknown security posture and should only be used in deployments where both the downstream and upstream are trusted.
This extension extends and can be used with the following extension category:
gRPC HTTP/1.1 Reverse Bridge configuration overview.
gRPC reverse bridge filter configuration
(string, REQUIRED) The content-type to pass to the upstream when the gRPC bridge filter is applied. The filter will also validate that the upstream responds with the same content type.
(bool) If true, Envoy will assume that the upstream doesn’t understand gRPC frames and strip the gRPC frame from the request, and add it back in to the response. This will hide the gRPC semantics from the upstream, allowing it to receive and respond with a simple binary encoded protobuf.
gRPC reverse bridge filter configuration per virtualhost/route/weighted-cluster level.
(bool) If true, disables gRPC reverse bridge filter for this particular vhost or route. If disabled is specified in multiple per-filter-configs, the most specific one will be used.