AWS cli documentation change
Summary
Updated CLI version references from 2.31.13 to 2.31.16 and expanded documentation for HTTP/2 attribute to clarify client connection behavior and header validation requirements
Security assessment
The change adds documentation about HTTP/2's stricter header validation requirements when enabled, which helps users understand security implications of header handling. However, there's no evidence this addresses a specific vulnerability.
Diff
diff --git a/cli/latest/reference/elbv2/describe-load-balancer-attributes.md b/cli/latest/reference/elbv2/describe-load-balancer-attributes.md index ecbd06048..aec068034 100644 --- a//cli/latest/reference/elbv2/describe-load-balancer-attributes.md +++ b//cli/latest/reference/elbv2/describe-load-balancer-attributes.md @@ -15 +15 @@ - * [AWS CLI 2.31.13 Command Reference](../../index.html) » + * [AWS CLI 2.31.16 Command Reference](../../index.html) » @@ -334 +334 @@ Attributes -> (list) ->>> * `routing.http2.enabled` \- Indicates whether HTTP/2 is enabled. The possible values are `true` and `false` . The default is `true` . Elastic Load Balancing requires that message header names contain only alphanumeric characters and hyphens. +>>> * `routing.http2.enabled` \- Indicates whether clients can connect to the load balancer using HTTP/2. If `true` , clients can connect using HTTP/2 or HTTP/1.1. However, all client requests are subject to the stricter HTTP/2 header validation rules. For example, message header names must contain only alphanumeric characters and hyphens. If `false` , clients must connect using HTTP/1.1. The default is `true` . @@ -373 +373 @@ Attributes -> (list) - * [AWS CLI 2.31.13 Command Reference](../../index.html) » + * [AWS CLI 2.31.16 Command Reference](../../index.html) »