public interface Http1ProtocolOptionsOrBuilder
extends com.google.protobuf.MessageOrBuilder
Modifier and Type | Method and Description |
---|---|
boolean |
getAcceptHttp10()
Handle incoming HTTP/1.0 and HTTP 0.9 requests.
|
com.google.protobuf.BoolValue |
getAllowAbsoluteUrl()
Handle HTTP requests with absolute URLs in the requests.
|
com.google.protobuf.BoolValueOrBuilder |
getAllowAbsoluteUrlOrBuilder()
Handle HTTP requests with absolute URLs in the requests.
|
boolean |
getAllowChunkedLength()
Allows Envoy to process requests/responses with both `Content-Length` and `Transfer-Encoding`
headers set.
|
String |
getDefaultHostForHttp10()
A default host for HTTP/1.0 requests.
|
com.google.protobuf.ByteString |
getDefaultHostForHttp10Bytes()
A default host for HTTP/1.0 requests.
|
boolean |
getEnableTrailers()
Enables trailers for HTTP/1.
|
Http1ProtocolOptions.HeaderKeyFormat |
getHeaderKeyFormat()
Describes how the keys for response headers should be formatted.
|
Http1ProtocolOptions.HeaderKeyFormatOrBuilder |
getHeaderKeyFormatOrBuilder()
Describes how the keys for response headers should be formatted.
|
com.google.protobuf.BoolValue |
getOverrideStreamErrorOnInvalidHttpMessage()
Allows invalid HTTP messaging.
|
com.google.protobuf.BoolValueOrBuilder |
getOverrideStreamErrorOnInvalidHttpMessageOrBuilder()
Allows invalid HTTP messaging.
|
boolean |
hasAllowAbsoluteUrl()
Handle HTTP requests with absolute URLs in the requests.
|
boolean |
hasHeaderKeyFormat()
Describes how the keys for response headers should be formatted.
|
boolean |
hasOverrideStreamErrorOnInvalidHttpMessage()
Allows invalid HTTP messaging.
|
findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
boolean hasAllowAbsoluteUrl()
Handle HTTP requests with absolute URLs in the requests. These requests are generally sent by clients to forward/explicit proxies. This allows clients to configure envoy as their HTTP proxy. In Unix, for example, this is typically done by setting the *http_proxy* environment variable.
.google.protobuf.BoolValue allow_absolute_url = 1;
com.google.protobuf.BoolValue getAllowAbsoluteUrl()
Handle HTTP requests with absolute URLs in the requests. These requests are generally sent by clients to forward/explicit proxies. This allows clients to configure envoy as their HTTP proxy. In Unix, for example, this is typically done by setting the *http_proxy* environment variable.
.google.protobuf.BoolValue allow_absolute_url = 1;
com.google.protobuf.BoolValueOrBuilder getAllowAbsoluteUrlOrBuilder()
Handle HTTP requests with absolute URLs in the requests. These requests are generally sent by clients to forward/explicit proxies. This allows clients to configure envoy as their HTTP proxy. In Unix, for example, this is typically done by setting the *http_proxy* environment variable.
.google.protobuf.BoolValue allow_absolute_url = 1;
boolean getAcceptHttp10()
Handle incoming HTTP/1.0 and HTTP 0.9 requests. This is off by default, and not fully standards compliant. There is support for pre-HTTP/1.1 style connect logic, dechunking, and handling lack of client host iff *default_host_for_http_10* is configured.
bool accept_http_10 = 2;
String getDefaultHostForHttp10()
A default host for HTTP/1.0 requests. This is highly suggested if *accept_http_10* is true as Envoy does not otherwise support HTTP/1.0 without a Host header. This is a no-op if *accept_http_10* is not true.
string default_host_for_http_10 = 3;
com.google.protobuf.ByteString getDefaultHostForHttp10Bytes()
A default host for HTTP/1.0 requests. This is highly suggested if *accept_http_10* is true as Envoy does not otherwise support HTTP/1.0 without a Host header. This is a no-op if *accept_http_10* is not true.
string default_host_for_http_10 = 3;
boolean hasHeaderKeyFormat()
Describes how the keys for response headers should be formatted. By default, all header keys are lower cased.
.envoy.config.core.v3.Http1ProtocolOptions.HeaderKeyFormat header_key_format = 4;
Http1ProtocolOptions.HeaderKeyFormat getHeaderKeyFormat()
Describes how the keys for response headers should be formatted. By default, all header keys are lower cased.
.envoy.config.core.v3.Http1ProtocolOptions.HeaderKeyFormat header_key_format = 4;
Http1ProtocolOptions.HeaderKeyFormatOrBuilder getHeaderKeyFormatOrBuilder()
Describes how the keys for response headers should be formatted. By default, all header keys are lower cased.
.envoy.config.core.v3.Http1ProtocolOptions.HeaderKeyFormat header_key_format = 4;
boolean getEnableTrailers()
Enables trailers for HTTP/1. By default the HTTP/1 codec drops proxied trailers. .. attention:: Note that this only happens when Envoy is chunk encoding which occurs when: - The request is HTTP/1.1. - Is neither a HEAD only request nor a HTTP Upgrade. - Not a response to a HEAD request. - The content length header is not present.
bool enable_trailers = 5;
boolean getAllowChunkedLength()
Allows Envoy to process requests/responses with both `Content-Length` and `Transfer-Encoding` headers set. By default such messages are rejected, but if option is enabled - Envoy will remove Content-Length header and process message. See `RFC7230, sec. 3.3.3 <https://tools.ietf.org/html/rfc7230#section-3.3.3>` for details. .. attention:: Enabling this option might lead to request smuggling vulnerability, especially if traffic is proxied via multiple layers of proxies.
bool allow_chunked_length = 6;
boolean hasOverrideStreamErrorOnInvalidHttpMessage()
Allows invalid HTTP messaging. When this option is false, then Envoy will terminate HTTP/1.1 connections upon receiving an invalid HTTP message. However, when this option is true, then Envoy will leave the HTTP/1.1 connection open where possible. If set, this overrides any HCM :ref:`stream_error_on_invalid_http_messaging <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_error_on_invalid_http_message>`.
.google.protobuf.BoolValue override_stream_error_on_invalid_http_message = 7;
com.google.protobuf.BoolValue getOverrideStreamErrorOnInvalidHttpMessage()
Allows invalid HTTP messaging. When this option is false, then Envoy will terminate HTTP/1.1 connections upon receiving an invalid HTTP message. However, when this option is true, then Envoy will leave the HTTP/1.1 connection open where possible. If set, this overrides any HCM :ref:`stream_error_on_invalid_http_messaging <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_error_on_invalid_http_message>`.
.google.protobuf.BoolValue override_stream_error_on_invalid_http_message = 7;
com.google.protobuf.BoolValueOrBuilder getOverrideStreamErrorOnInvalidHttpMessageOrBuilder()
Allows invalid HTTP messaging. When this option is false, then Envoy will terminate HTTP/1.1 connections upon receiving an invalid HTTP message. However, when this option is true, then Envoy will leave the HTTP/1.1 connection open where possible. If set, this overrides any HCM :ref:`stream_error_on_invalid_http_messaging <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.stream_error_on_invalid_http_message>`.
.google.protobuf.BoolValue override_stream_error_on_invalid_http_message = 7;
Copyright © 2018–2021 The Envoy Project. All rights reserved.