- Http1Config (webserver.http1) Configuration
Type: io.helidon.webserver.http1.Http1Config
This type provides the following service implementations:
io.helidon.webserver.spi.ProtocolConfig
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. @return if `true` answer with 100 continue immediately after expect continue |
max-headers-size | int | 16384 | Maximal size of received headers in bytes. @return maximal header size |
max-prologue-length | int | 2048 | Maximal size of received HTTP prologue (GET /path HTTP/1.1). @return maximal size in bytes |
recv-log | boolean | true | Logging of received packets. Uses trace and debug levels on logger of Http1LoggingConnectionListener with suffix of @return `true` if logging should be enabled for received packets, `false` if no logging should be done |
requested-uri-discovery | Requested URI discovery settings. @return settings for computing the requested URI | ||
send-log | boolean | true | Logging of sent packets. Uses trace and debug levels on logger of Http1LoggingConnectionListener with suffix of @return `true` if logging should be enabled for sent packets, `false` if no logging should be done |
validate-path | boolean | true | If set to false, any path is accepted (even containing illegal characters). @return whether to validate path |
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`. @return whether to validate headers |
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. @return whether to validate headers |