mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-10 19:31:55 +00:00
gcloud: Wed May 1 09:26:55 UTC 2024
This commit is contained in:
parent
3740758467
commit
48fac7efd4
454 changed files with 11765 additions and 12790 deletions
|
|
@ -8,6 +8,7 @@ SYNOPSIS
|
|||
[--http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC]
|
||||
[--proxy-bind] [--quic-override=QUIC_OVERRIDE; default="NONE"]
|
||||
[--server-tls-policy=SERVER_TLS_POLICY] [--ssl-policy=SSL_POLICY]
|
||||
[--tls-early-data=TLS_EARLY_DATA]
|
||||
[--certificate-manager-certificates=[CERTIFICATE_MANAGER_CERTIFICATES,
|
||||
...] | --ssl-certificates=SSL_CERTIFICATE,[...]]
|
||||
[--global | --region=REGION]
|
||||
|
|
@ -134,6 +135,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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue