Package io.envoyproxy.envoy.config.core.v3

Class AlternateProtocolsCacheOptions.AlternateProtocolsCacheEntry

java.lang.Object
com.google.protobuf.AbstractMessageLite
com.google.protobuf.AbstractMessage
com.google.protobuf.GeneratedMessage
io.envoyproxy.envoy.config.core.v3.AlternateProtocolsCacheOptions.AlternateProtocolsCacheEntry
All Implemented Interfaces:
com.google.protobuf.Message, com.google.protobuf.MessageLite, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, AlternateProtocolsCacheOptions.AlternateProtocolsCacheEntryOrBuilder, Serializable
Enclosing class:
AlternateProtocolsCacheOptions
public static final class AlternateProtocolsCacheOptions.AlternateProtocolsCacheEntry extends com.google.protobuf.GeneratedMessage implements AlternateProtocolsCacheOptions.AlternateProtocolsCacheEntryOrBuilder
 Allows pre-populating the cache with HTTP/3 alternate protocols entries with a 7 day lifetime.
 This will cause Envoy to attempt HTTP/3 to those upstreams, even if the upstreams have not
 advertised HTTP/3 support. These entries will be overwritten by alt-svc
 response headers or cached values.
 As with regular cached entries, if the origin response would result in clearing an existing
 alternate protocol cache entry, pre-populated entries will also be cleared.
 Adding a cache entry with hostname=foo.com port=123 is the equivalent of getting
 response headers
 alt-svc: h3=:"123"; ma=86400" in a response to a request to foo.com:123
Protobuf type envoy.config.core.v3.AlternateProtocolsCacheOptions.AlternateProtocolsCacheEntry
See Also: