imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-08 10:35:03 +00:00
Code Activity

gcloud: Wed Jun 12 09:25:04 UTC 2024

Browse source
This commit is contained in:
Automated 2024-06-12 09:25:04 +00:00
parent 40ba53d37f
commit 04a1e3ce77
205 changed files with 8281 additions and 231 deletions
Download patch file Download diff file Expand all files Collapse all files

25
gcloud/compute/target-https-proxies/create
View file

@ -6,7 +6,7 @@ SYNOPSIS
[--certificate-map=CERTIFICATE_MAP] [--description=DESCRIPTION]
[--http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC]
[--quic-override=QUIC_OVERRIDE; default="NONE"]
[--ssl-policy=SSL_POLICY]
[--ssl-policy=SSL_POLICY] [--tls-early-data=TLS_EARLY_DATA]
[--certificate-manager-certificates=[CERTIFICATE_MANAGER_CERTIFICATES,
...] | --ssl-certificates=SSL_CERTIFICATE,[...]]
[--global | --region=REGION]
@ -103,6 +103,29 @@ OPTIONAL FLAGS
and load balancers that are using the HTTPS proxy. The SSL policy must
exist and cannot be deleted while referenced by a target HTTPS proxy.
--tls-early-data=TLS_EARLY_DATA
TLS 1.3 Early Data ("0-RTT" or "zero round trip") allows clients to
include HTTP request data alongside a TLS handshake. This can improve
application performance, especially on networks where connection
interruptions may be common, such as on mobile. This applies to both
HTTP over TCP (ie: HTTP/1.1 and HTTP/2) and HTTP/3 over QUIC.
TLS_EARLY_DATA must be one of:
DISABLED
TLS 1.3 Early Data is not advertised, and any (invalid) attempts to
send Early Data will be rejected.
PERMISSIVE
Enables TLS 1.3 Early Data for requests with safe HTTP methods
(GET, HEAD, OPTIONS, TRACE). This mode does not enforce any other
limitations for requests with Early Data. The application owner
should validate that Early Data is acceptable for a given request
path.
STRICT
Enables TLS 1.3 Early Data for requests with safe HTTP methods, and
HTTP requests that do not have query parameters. Requests that send
Early Data containing non-idempotent HTTP methods or with query
parameters will be rejected with a HTTP 425.
At most one of these can be specified:
Certificate resource - certificate-manager-certificates to attach. This

26
gcloud/compute/target-https-proxies/update
View file

@ -3,7 +3,8 @@ NAME
SYNOPSIS
gcloud compute target-https-proxies update NAME
[--quic-override=QUIC_OVERRIDE] [--url-map=URL_MAP]
[--quic-override=QUIC_OVERRIDE] [--tls-early-data=TLS_EARLY_DATA]
[--url-map=URL_MAP]
[--certificate-manager-certificates=[CERTIFICATE_MANAGER_CERTIFICATES,
...] | --clear-ssl-certificates
| --ssl-certificates=SSL_CERTIFICATE,[...] --global-ssl-certificates
@ -66,6 +67,29 @@ FLAGS
NONE
Allows Google to control when QUIC is rolled out.
--tls-early-data=TLS_EARLY_DATA
TLS 1.3 Early Data ("0-RTT" or "zero round trip") allows clients to
include HTTP request data alongside a TLS handshake. This can improve
application performance, especially on networks where connection
interruptions may be common, such as on mobile. This applies to both
HTTP over TCP (ie: HTTP/1.1 and HTTP/2) and HTTP/3 over QUIC.
TLS_EARLY_DATA must be one of:
DISABLED
TLS 1.3 Early Data is not advertised, and any (invalid) attempts to
send Early Data will be rejected.
PERMISSIVE
Enables TLS 1.3 Early Data for requests with safe HTTP methods
(GET, HEAD, OPTIONS, TRACE). This mode does not enforce any other
limitations for requests with Early Data. The application owner
should validate that Early Data is acceptable for a given request
path.
STRICT
Enables TLS 1.3 Early Data for requests with safe HTTP methods, and
HTTP requests that do not have query parameters. Requests that send
Early Data containing non-idempotent HTTP methods or with query
parameters will be rejected with a HTTP 425.
--url-map=URL_MAP
A reference to a URL map resource. A URL map defines the mapping of
URLs to backend services. Before you can refer to a URL map, you must