Class HttpProtocolOptions.UseDownstreamHttpConfig.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderT>
com.google.protobuf.GeneratedMessageV3.Builder<HttpProtocolOptions.UseDownstreamHttpConfig.Builder>
io.envoyproxy.envoy.extensions.upstreams.http.v3.HttpProtocolOptions.UseDownstreamHttpConfig.Builder
All Implemented Interfaces:
com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, HttpProtocolOptions.UseDownstreamHttpConfigOrBuilder, Cloneable
Enclosing class:
HttpProtocolOptions.UseDownstreamHttpConfig

public static final class HttpProtocolOptions.UseDownstreamHttpConfig.Builder extends com.google.protobuf.GeneratedMessageV3.Builder<HttpProtocolOptions.UseDownstreamHttpConfig.Builder> implements HttpProtocolOptions.UseDownstreamHttpConfigOrBuilder
 If this is used, the cluster can use either of the configured protocols, and
 will use whichever protocol was used by the downstream connection.

 If HTTP/3 is configured for downstream and not configured for upstream,
 HTTP/3 requests will fail over to HTTP/2.
 
Protobuf type envoy.extensions.upstreams.http.v3.HttpProtocolOptions.UseDownstreamHttpConfig