Http1Config (webserver.http1) Configuration

Http1Config (webserver.http1) Configuration

Type: io.helidon.webserver.http1.Http1Config

Config key

http_1_1

Copied

This type provides the following service implementations:

io.helidon.webserver.spi.ProtocolConfigProvider

Configuration options

Optional configuration options

key	type	default value	description
`continue-immediately`	boolean	`false`	When true WebServer answers to expect continue with 100 continue immediately, not waiting for user to actually request the data.
`max-headers-size`	int	`16384`	Maximal size of received headers in bytes.
`max-prologue-length`	int	`4096`	Maximal size of received HTTP prologue (GET /path HTTP/1.1).
`recv-log`	boolean	`true`	Logging of received packets. Uses trace and debug levels on logger of Http1LoggingConnectionListener with suffix of .recv`.
`requested-uri-discovery`	RequestedUriDiscoveryContext		Requested URI discovery settings.
`send-log`	boolean	`true`	Logging of sent packets. Uses trace and debug levels on logger of Http1LoggingConnectionListener with suffix of .send`.
`validate-path`	boolean	`true`	If set to false, any path is accepted (even containing illegal characters).
`validate-prologue`	boolean	`true`	If set to false, any query and fragment is accepted (even containing illegal characters). Validation of path is controlled by validatePath().
`validate-request-headers`	boolean	`true`	Whether to validate headers. If set to false, any value is accepted, otherwise validates headers + known headers are validated by format (content length is always validated as it is part of protocol processing (other headers may be validated if features use them)). Defaults to `true`.
~~`validate-request-host-header`~~	boolean	`true`	Deprecated Request host header validation. When host header is invalid, we return io.helidon.http.Status.BAD_REQUEST_400. The validation is done according to RFC-3986 (see io.helidon.common.uri.UriValidator). This is a requirement of the HTTP specification. This option allows you to disable the "full-blown" validation ("simple" validation is still in - the port must be parseable to integer). @deprecated this switch exists for temporary backward compatible behavior, and will be removed in a future Helidon version
`validate-response-headers`	boolean	`false`	Whether to validate headers. If set to false, any value is accepted, otherwise validates headers + known headers are validated by format (content length is always validated as it is part of protocol processing (other headers may be validated if features use them)). Defaults to `false` as user has control on the header creation.