-
Notifications
You must be signed in to change notification settings - Fork 0
Spring Boot 1.3.0 RC1 Release Notes
|
Note
|
Work in progress. Spring Boot 1.3.0.RC1 has not been released yet. |
For changes in earlier milestones, please refer to:
The spring.hateoas.apply-to-primary-object-mapper property has been removed as the Spring HATEOAS auto-configuration has been reworked such that it no longer affects the context’s primary ObjectMapper. It has been replaced with a property named spring.hateoas.use-hal-as-default-json-media-type which controls whether or not
the Spring HATEOAS HTTP message converter will handle requests for application/json in addition to requests for
application/hal+json.
See the instructions in the M1 release notes for upgrade from 1.2.x.
X-Forwarded-For header support is now provided for Jetty and Undertow. Tomcat support has also been refreshed so that a single server.proxy-peer-address property can be set to true if X-Forwarded-For headers should be respected. Spring Boot will detect deployments to Cloud Foundry or Heroku and automatically enable support.
-
Error controller trace param change
-
the x-forwarded-for support
-
logs profile on startup
-
DevTools proxy configuration
-
Auto-configuration of WebSocket message converter
-
Auto-configuration of Jackson’s parameter names module
-
Banner Mode
-
Spring Security header defaults
-
TraceWebFilter inclue options
-
Revert stacktrace order
-
https://github.com/spring-projects/spring-boot/issues/4227#issuecomment-149562276
-
war command
-
initOptions on fully exec jars
-
Maven addResources
-
Maven activeProfiles
-
Session store dir
-
DelegatingFilterProxy
-
Session not saved with Tomcat anymore
-
DB2 driver detection
-
Eclipse Oomph
-
Template warning not exception
-
Log patterns
-
error properties now renamed server.error
-
Banner to log
-
X-Forward header support for all containers + server.proxy-peer-address=true
-
Active profiles logged on startup