diff --git a/content/en/docs/reference/config/istio.mesh.v1alpha1/index.html b/content/en/docs/reference/config/istio.mesh.v1alpha1/index.html index 20b619f57e..307bb0ae1a 100644 --- a/content/en/docs/reference/config/istio.mesh.v1alpha1/index.html +++ b/content/en/docs/reference/config/istio.mesh.v1alpha1/index.html @@ -3672,6 +3672,10 @@ Note: currently all headers are enabled by default.

attemptCount: disabled: true +

Below shows an example of preserving the header case for HTTP 1.x requests

+
proxyHeaders:
+  perserveHttp1HeaderCase: true
+

Some headers are enabled by default, and require explicitly disabling. See below for an example of disabling all default-enabled headers:

proxyHeaders:
   forwardedClientCert: SANITIZE
@@ -4134,6 +4138,25 @@ No
 By default, the behavior is unspecified.
 If IN_MESH, these headers will not be appended to outbound requests from sidecars to services not in-mesh.

 
+
+
+No
+
+
+
+preserveHttp1HeaderCase
+BoolValue
+
+
When true, the original case of HTTP/1.x headers will be preserved
+as they pass through the proxy, rather than normalizing them to lowercase.
+This field is particularly useful for applications that require case-sensitive
+headers for interoperability with downstream systems or APIs that expect specific
+casing.
+The preserve_http1_header_case option only applies to HTTP/1.x traffic, as HTTP/2 requires all headers
+to be lowercase per the protocol specification. Envoy will ignore this field for HTTP/2
+requests and automatically normalize headers to lowercase, ensuring compliance with HTTP/2
+standards.

+
 
 
 No
diff --git a/content/en/docs/reference/config/networking/workload-group/index.html b/content/en/docs/reference/config/networking/workload-group/index.html
index ca1d52da35..81d9632636 100644
--- a/content/en/docs/reference/config/networking/workload-group/index.html
+++ b/content/en/docs/reference/config/networking/workload-group/index.html
@@ -8,7 +8,7 @@ layout: protoc-gen-docs
 generator: protoc-gen-docs
 schema: istio.networking.v1alpha3.WorkloadGroup
 aliases: [/docs/reference/config/networking/v1alpha3/workload-group]
-number_of_entries: 7
+number_of_entries: 8
 ---
 
WorkloadGroup describes a collection of workload instances.
 It provides a specification that the workload instances can use to bootstrap
@@ -213,6 +213,17 @@ No
 
 
Health is determined by how the command that is executed exited.

 
+
+
+No
+
+
+
+grpc
+GrpcHealthCheckConfig (oneof)
+
+
GRPC call is made and response/error is used to determine health.

+
 
 
 No
@@ -285,6 +296,43 @@ No
 
Headers the proxy will pass on to make the request.
 Allows repeated headers.

 
+
+
+No
+
+
+
+
+
+
GrpcHealthCheckConfig

+

+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
FieldTypeDescriptionRequired
portuint32
+
Port on which the endpoint lives.

+
+		
+No
+
servicestring
+
Service is the fully qualified name of the service to send the grpc health check request

+
 		
 
 No
diff --git a/content/zh/docs/reference/config/istio.mesh.v1alpha1/index.html b/content/zh/docs/reference/config/istio.mesh.v1alpha1/index.html
index a1a3d0bd94..c03414e901 100644
--- a/content/zh/docs/reference/config/istio.mesh.v1alpha1/index.html
+++ b/content/zh/docs/reference/config/istio.mesh.v1alpha1/index.html
@@ -3672,6 +3672,10 @@ Note: currently all headers are enabled by default.

   attemptCount:
     disabled: true
 
+
Below shows an example of preserving the header case for HTTP 1.x requests

+
proxyHeaders:
+  perserveHttp1HeaderCase: true
+

 
Some headers are enabled by default, and require explicitly disabling. See below for an example of disabling all default-enabled headers:

 
proxyHeaders:
   forwardedClientCert: SANITIZE
@@ -4134,6 +4138,25 @@ No
 By default, the behavior is unspecified.
 If IN_MESH, these headers will not be appended to outbound requests from sidecars to services not in-mesh.

 
+

+No
+
preserveHttp1HeaderCaseBoolValue
+
When true, the original case of HTTP/1.x headers will be preserved
+as they pass through the proxy, rather than normalizing them to lowercase.
+This field is particularly useful for applications that require case-sensitive
+headers for interoperability with downstream systems or APIs that expect specific
+casing.
+The preserve_http1_header_case option only applies to HTTP/1.x traffic, as HTTP/2 requires all headers
+to be lowercase per the protocol specification. Envoy will ignore this field for HTTP/2
+requests and automatically normalize headers to lowercase, ensuring compliance with HTTP/2
+standards.

+
 		
 
 No
diff --git a/content/zh/docs/reference/config/networking/workload-group/index.html b/content/zh/docs/reference/config/networking/workload-group/index.html
index 363e5e9874..7ee800d682 100644
--- a/content/zh/docs/reference/config/networking/workload-group/index.html
+++ b/content/zh/docs/reference/config/networking/workload-group/index.html
@@ -8,7 +8,7 @@ layout: protoc-gen-docs
 generator: protoc-gen-docs
 schema: istio.networking.v1alpha3.WorkloadGroup
 aliases: [/zh/docs/reference/config/networking/v1alpha3/workload-group]
-number_of_entries: 7
+number_of_entries: 8
 ---
 
WorkloadGroup describes a collection of workload instances.
 It provides a specification that the workload instances can use to bootstrap
@@ -213,6 +213,17 @@ No
 

 
Health is determined by how the command that is executed exited.

 
+		
+No
+
grpcGrpcHealthCheckConfig (oneof)
+
GRPC call is made and response/error is used to determine health.

+
 		
 
 No
@@ -285,6 +296,43 @@ No
 
Headers the proxy will pass on to make the request.
 Allows repeated headers.

 
+		
+No
+

+

+
GrpcHealthCheckConfig

+

+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
FieldTypeDescriptionRequired
portuint32
+
Port on which the endpoint lives.

+
+		
+No
+
servicestring
+
Service is the fully qualified name of the service to send the grpc health check request

+
 		
 
 No