Class ManagementInterfaceConfiguration
ManagementInterfaceBuildTimeConfig.enabled build-time property.-
Field Summary
FieldsModifier and TypeFieldDescriptionintThe accept backlog, this is how many connections can be waiting to be accepted before connections start being rejectedAuthentication configurationRequest body related settingsPath to a unix domain socketbooleanEnable listening to host:portAdditional HTTP configuration per pathbooleanWhen set totrue, the HTTP server automatically sends `100 CONTINUE` response when the request expects it (with the `Expect: 100-Continue` header).Additional HTTP Headers always sent in the responseThe HTTP hostbooleanEnable listening to host:portHttp connection idle timeoutServer limits configurationintThe HTTP portThe SSL configintThe HTTP portThe name of the TLS configuration to use. -
Constructor Summary
Constructors -
Method Summary
-
Field Details
-
auth
Authentication configuration -
port
The HTTP port -
testPort
The HTTP port -
host
The HTTP hostIn dev/test mode this defaults to localhost, in prod mode this defaults to 0.0.0.0
Defaulting to 0.0.0.0 makes it easier to deploy Quarkus to container, however it is not suitable for dev/test mode as other people on the network can connect to your development machine.
As an exception, when running in Windows Subsystem for Linux (WSL), the HTTP host defaults to 0.0.0.0 even in dev/test mode since using localhost makes the application inaccessible.
-
hostEnabled
Enable listening to host:port -
ssl
The SSL config -
tlsConfigurationName
The name of the TLS configuration to use.If not set and the default TLS configuration is configured (
quarkus.tls.*) then that will be used. If a name is configured, it uses the configuration fromquarkus.tls.<name>.*If a name is configured, but no TLS configuration is found with that name then an error will be thrown.If no TLS configuration is set, and
quarkus.tls.*is not configured, then, `quarkus.management.ssl` will be used. -
handle100ContinueAutomatically
@ConfigItem(defaultValue="false", name="handle-100-continue-automatically") public boolean handle100ContinueAutomaticallyWhen set totrue, the HTTP server automatically sends `100 CONTINUE` response when the request expects it (with the `Expect: 100-Continue` header). -
limits
Server limits configuration -
idleTimeout
Http connection idle timeout -
body
Request body related settings -
acceptBacklog
The accept backlog, this is how many connections can be waiting to be accepted before connections start being rejected -
domainSocket
Path to a unix domain socket -
domainSocketEnabled
Enable listening to host:port -
header
Additional HTTP Headers always sent in the response -
filter
Additional HTTP configuration per path -
proxy
-
-
Constructor Details
-
ManagementInterfaceConfiguration
public ManagementInterfaceConfiguration()
-
-
Method Details
-
determinePort
-