- 
                Notifications
    You must be signed in to change notification settings 
- Fork 41.6k
Spring Boot 2.4.0 RC1 Configuration Changelog
Configuration properties change between 2.4.0-M4 and 2.4.0-RC1
| Key | Replacement | Reason | 
| 
 | 
 | |
| 
 | ||
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | 
| Key | Default value | Description | 
| 
 | Charset to use for console output. | |
| 
 | Charset to use for file output. | |
| 
 | 
 | Whether to clean the archive log files on startup. | 
| 
 | 
 | Pattern for rolled-over log file names. | 
| 
 | 
 | Maximum log file size. | 
| 
 | 
 | Maximum number of days archive log files are kept. | 
| 
 | 
 | Total size of log backups to be kept. | 
| 
 | `` | Management endpoint base path (for instance,  | 
| 
 | 
 | Maximum number of retries when trying to obtain a lock. | 
| 
 | Fully qualified name of the JDBC driver. | |
| 
 | 
 | Whether the container should present batched messages as discrete messages or call the listener with the batch. | 
| 
 | 
 | Whether the container creates a batch of messages based on the 'receive-timeout' and 'batch-size'. | 
| 
 | 
 | Whether the container should present batched messages as discrete messages or call the listener with the batch. | 
| 
 | Locale to use. | |
| 
 | Define how the locale should be resolved. | |
| 
 | 
 | Whether to enable default resource handling. | 
| 
 | Indicate that the response message is intended for a single user and must not be stored by a shared cache. | |
| 
 | Indicate that any cache may store the response. | |
| 
 | Maximum time the response should be cached, in seconds if no duration suffix is not specified. | |
| 
 | Indicate that once it has become stale, a cache must not use the response without re-validating it with the server. | |
| 
 | Indicate that the cached response can be reused only if re-validated with the server. | |
| 
 | Indicate to not cache the response in any case. | |
| 
 | Indicate intermediaries (caches and others) that they should not transform the response content. | |
| 
 | Same meaning as the "must-revalidate" directive, except that it does not apply to private caches. | |
| 
 | Maximum time the response should be cached by shared caches, in seconds if no duration suffix is not specified. | |
| 
 | Maximum time the response may be used when errors are encountered, in seconds if no duration suffix is not specified. | |
| 
 | Maximum time the response can be served after it becomes stale, in seconds if no duration suffix is not specified. | |
| 
 | Cache period for the resources served by the resource handler. | |
| 
 | 
 | Whether to enable caching in the Resource chain. | 
| 
 | 
 | Whether to enable resolution of already compressed resources (gzip, brotli). | 
| 
 | Whether to enable the Spring Resource Handling chain. | |
| 
 | 
 | Whether to enable the content Version Strategy. | 
| 
 | 
 | Comma-separated list of patterns to apply to the content Version Strategy. | 
| 
 | 
 | Whether to enable the fixed Version Strategy. | 
| 
 | 
 | Comma-separated list of patterns to apply to the fixed Version Strategy. | 
| 
 | Version string to use for the fixed Version Strategy. | |
| 
 | 
 | Locations of static resources. | 
| Key | Replacement | Reason | 
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 | |
| 
 | 
 |