gRPC HTTP/1.1 Reverse Bridge

This extension may be referenced by the qualified name envoy.filters.http.grpc_http1_reverse_bridge

Note

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.

Tip

This extension extends and can be used with the following extension categories:

gRPC HTTP/1.1 Reverse Bridge configuration overview.

config.filter.http.grpc_http1_reverse_bridge.v2alpha1.FilterConfig

[config.filter.http.grpc_http1_reverse_bridge.v2alpha1.FilterConfig proto]

gRPC reverse bridge filter configuration

{
  "content_type": "...",
  "withhold_grpc_frames": "..."
}
content_type

(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.

withhold_grpc_frames

(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.

config.filter.http.grpc_http1_reverse_bridge.v2alpha1.FilterConfigPerRoute

[config.filter.http.grpc_http1_reverse_bridge.v2alpha1.FilterConfigPerRoute proto]

gRPC reverse bridge filter configuration per virtualhost/route/weighted-cluster level.

{
  "disabled": "..."
}
disabled

(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.