@ -16,11 +16,10 @@ If you have more than one implementation, Spring Boot uses the following order f
@@ -16,11 +16,10 @@ If you have more than one implementation, Spring Boot uses the following order f
. Redis
. JDBC
. If neither Redis or JDBC are available, we do not configure a javadoc:org.springframework.session.SessionRepository[].
. If neither Redis nor JDBC are available, we do not configure a javadoc:org.springframework.session.SessionRepository[].
When building a reactive web application, the Redis store can be auto-configured.
The reactive auto-configuration replaces the need to use `@Enable*WebSession`.
This replaces the need to use `@EnableRedisWebSession`.
Each store has specific additional settings.
For instance, it is possible to customize the name of the table for the JDBC store, as shown in the following example:
For setting the timeout of the session you can use the configprop:spring.session.timeout[] property.
If that property is not set with a servlet web application, the auto-configuration falls back to the value of configprop:server.servlet.session.timeout[].
You can take control over Spring Session's configuration using `@Enable*HttpSession` (servlet) or `@Enable*WebSession` (reactive).
You can take control over Spring Session's configuration using `@Enable*HttpSession` (servlet) or `@EnableRedisWebSession` (reactive).
This will cause the auto-configuration to back off.
Spring Session can then be configured using the annotation's attributes rather than the previously described configuration properties.