/
config.proto
62 lines (52 loc) · 3.37 KB
/
config.proto
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
syntax = "proto3";
package envoy.extensions.filters.http.grpc_http1_reverse_bridge.v3;
import "udpa/annotations/status.proto";
import "udpa/annotations/versioning.proto";
import "validate/validate.proto";
option java_package = "io.envoyproxy.envoy.extensions.filters.http.grpc_http1_reverse_bridge.v3";
option java_outer_classname = "ConfigProto";
option java_multiple_files = true;
option go_package = "github.com/envoyproxy/go-control-plane/envoy/extensions/filters/http/grpc_http1_reverse_bridge/v3;grpc_http1_reverse_bridgev3";
option (udpa.annotations.file_status).package_version_status = ACTIVE;
// [#protodoc-title: gRPC HTTP/1.1 Reverse Bridge]
// gRPC HTTP/1.1 Reverse Bridge :ref:`configuration overview
// <config_http_filters_grpc_http1_reverse_bridge>`.
// [#extension: envoy.filters.http.grpc_http1_reverse_bridge]
// gRPC reverse bridge filter configuration
message FilterConfig {
option (udpa.annotations.versioning).previous_message_type =
"envoy.config.filter.http.grpc_http1_reverse_bridge.v2alpha1.FilterConfig";
// 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.
string content_type = 1 [(validate.rules).string = {min_len: 1}];
// 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. In order to calculate the ``Content-Length`` header value, Envoy
// will buffer the upstream response unless :ref:`response_size_header
// <envoy_v3_api_field_extensions.filters.http.grpc_http1_reverse_bridge.v3.FilterConfig.response_size_header>`
// is set, in which case Envoy will use the value of an upstream header to calculate the content
// length.
bool withhold_grpc_frames = 2;
// When :ref:`withhold_grpc_frames
// <envoy_v3_api_field_extensions.filters.http.grpc_http1_reverse_bridge.v3.FilterConfig.withhold_grpc_frames>`
// is true, this option controls how Envoy calculates the ``Content-Length``. When
// ``response_size_header`` is empty, Envoy will buffer the upstream response to calculate its
// size. When ``response_size_header`` is set to a non-empty string, Envoy will stream the response
// to the downstream and it will use the value of the response header with this name to set the
// ``Content-Length`` header and gRPC frame size. If the header with this name is repeated, only
// the first value will be used.
//
// Envoy will treat the upstream response as an error if this option is specified and the header
// is missing or if the value does not match the actual response body size.
string response_size_header = 3
[(validate.rules).string = {well_known_regex: HTTP_HEADER_NAME strict: false}];
}
// gRPC reverse bridge filter configuration per virtualhost/route/weighted-cluster level.
message FilterConfigPerRoute {
option (udpa.annotations.versioning).previous_message_type =
"envoy.config.filter.http.grpc_http1_reverse_bridge.v2alpha1.FilterConfigPerRoute";
// 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.
bool disabled = 1;
}