-
Notifications
You must be signed in to change notification settings - Fork 42.1k
Spring Boot 4.2.0 M1 Configuration Changelog
Configuration property changes between 4.1.1 and 4.2.0-M1
| Key | Replacement | Reason |
|---|---|---|
|
Path matching is no longer configurable |
|
|
Hostname verification is always enabled |
| Key | Default value | Description |
|---|---|---|
|
|
Whether payload should be compressed. |
|
Timeout to use when starting a connection for the health check. |
|
|
|
Format of the forwarded headers to support. |
|
|
Format of the forwarded headers to support. |
|
|
Maximum time to wait for request operations to complete. |
|
Default destination address for send operations when none is specified. |
|
|
|
AMQP broker host. |
|
|
Whether to start the container automatically on startup. |
|
|
Number of consumers. |
|
|
Whether to requeue messages in case of error. |
|
|
How long to wait for all consumers to shut down successfully. |
|
|
Initial number of credits to grant to the AMQP receiver. |
|
|
Timeout for receive operations. |
|
Password used to authenticate to the broker. |
|
|
|
AMQP broker port. |
|
The address to which the client should connect. |
|
|
|
RabbitMQ host. |
|
|
Timeout for gathering batch messages. |
|
Batch size, expressed as the number of physical messages, to be used by the container. |
|
|
|
Whether to enable observation. |
|
|
Login to authenticate against the broker. |
|
RabbitMQ port. |
|
|
SSL bundle name. |
|
|
Name of the default queue to receive messages from when none is specified explicitly. |
|
|
`` |
Name of the default exchange to use for send operations. |
|
`` |
Value of a default routing key to use for send operations. |
|
|
Login user to authenticate to the broker. |
|
Virtual host to use when connecting to the broker. |
|
|
Login user to authenticate to the broker. |
|
|
|
Whether the consumer should leave the group when stopping Kafka Streams. |
|
|
Format of the forwarded headers to support. |
|
|
Whether to use the "X-Forwarded-Prefix" header to determine the context path. |
|
|
Format of the forwarded headers to support. |
|
|
Whether to use the "X-Forwarded-Prefix" header to determine the context path. |