diff --git a/mesh/v1alpha1/istio.mesh.v1alpha1.pb.html b/mesh/v1alpha1/istio.mesh.v1alpha1.pb.html index ca06252b2d..0b7685cebb 100644 --- a/mesh/v1alpha1/istio.mesh.v1alpha1.pb.html +++ b/mesh/v1alpha1/istio.mesh.v1alpha1.pb.html @@ -5,7 +5,7 @@ layout: protoc-gen-docs generator: protoc-gen-docs weight: 20 -number_of_entries: 85 +number_of_entries: 89 ---
Configuration affecting the service mesh as a whole.
@@ -4145,6 +4145,17 @@Connection handling settings for this proxy, including buffer limits, timeouts,
+HTTP/2 tuning, header/path normalization, and connection limits.
+Use profile within this message to apply a recommended set of defaults.
Only append the istio metadata exchange headers for services considered in-mesh.
Traffic is considered in-mesh if it is secured with Istio mutual TLS. This means that MESH_EXTERNAL services, unmatched passthrough traffic, and requests to workloads without Istio enabled will be considered out of mesh.
Settings that control proxy connection handling, buffering, timeouts, +HTTP/2 tuning, header/path normalization, and connection limits.
+The profile field selects a set of recommended defaults for these settings.
+Any field explicitly set always takes precedence over profile defaults.
These settings primarily configure the downstream side of the proxy —
+listeners and the HTTP Connection Manager. The exception is
+cluster_per_connection_buffer_limit_bytes, which applies at the
+cluster level.
Where DestinationRule configures behavior at the upstream cluster level
+(notably connectionPoolSettings.tcp.idleTimeout), both apply
+independently at different hops rather than one overriding the other:
+DestinationRule governs Envoy → upstream connections, while these
+settings govern downstream → Envoy connections. For per-destination
+connection pool configuration, use DestinationRule’s
+connectionPoolSettings.
ProxyConfigProfile selects a default value set for the fields in this message. +Explicitly setting any field always takes precedence over profile defaults.
+ +| Name | +Description | +
|---|---|
SIDECAR |
+
+ SIDECAR profile preserves existing Istio behavior. +This is the default profile. No additional defaults are applied. + + |
+
EDGE |
+
+ EDGE profile applies Envoy’s recommended defaults for edge gateway deployments. +See https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/edge +Explicitly setting any field overrides the corresponding profile default. + + |
+
Action to take when Envoy receives client request with header names containing underscore characters.
+ +| Name | +Description | +
|---|---|
HEADERS_WITH_UNDERSCORES_ALLOW |
+
+ Allow headers with underscores. + + |
+
HEADERS_WITH_UNDERSCORES_REJECT_REQUEST |
+
+ Reject client request with 400 status. HTTP/1 requests are rejected with the “underscore_in_headers” response code. + + |
+
HEADERS_WITH_UNDERSCORES_DROP_HEADER |
+
+ Drop the header with name containing underscores. The header is dropped before the filter chain is invoked +and as such filters will not see the header. + + |
+
Determines the action for request paths that contain escaped slashes (%2F, %2f, %5C, %5c).
+ +| Name | +Description | +
|---|---|
KEEP_UNCHANGED |
+
+ Keep escaped slashes as they are. + + |
+
REJECT_REQUEST |
+
+ Reject client request with 400 status. + + |
+
UNESCAPE_AND_REDIRECT |
+
+ Unescape %2F and %5C sequences and redirect the request to the new path if the result path is different. + + |
+
UNESCAPE_AND_FORWARD |
+
+ Unescape %2F and %5C sequences and forward the request. Note that this option may introduce path confusion +vulnerabilities if the backend service does not expect unescaped slashes. + |