Rename error.* properties to server.error.*

Closes gh-4050
This commit is contained in:
Stephane Nicoll
2015-10-01 09:56:10 +02:00
parent 4b1389179d
commit b2c3e7e2ed
11 changed files with 42 additions and 29 deletions

View File

@@ -139,8 +139,9 @@ content into your application; rather pick only the properties that you need.
server.undertow.worker-threads= # number of worker threads
# ERROR HANDLING ({sc-spring-boot-autoconfigure}/web/ErrorProperties.{sc-ext}[ErrorProperties])
error.path=/error # the error path
error.include-stacktrace=never # when to include a stacktrace attribute (never/alway/on-trace-param)
server.error.path=/error # the error path
server.error.include-stacktrace=never # when to include a stacktrace attribute (never/alway/on-trace-param)
server.error.whitelabel.enabled=true # enable the default error page displayed in browsers in case of a server error
# SPRING MVC ({sc-spring-boot-autoconfigure}/web/WebMvcProperties.{sc-ext}[WebMvcProperties])
spring.mvc.locale= # set fixed locale, e.g. en_UK

View File

@@ -1744,7 +1744,7 @@ in the '`Production-ready features`' section.
Spring Boot installs a '`whitelabel`' error page that you will see in browser client if
you encounter a server error (machine clients consuming JSON and other media types should
see a sensible response with the right error code). To switch it off you can set
`error.whitelabel.enabled=false`, but normally in addition or alternatively to that you
`server.error.whitelabel.enabled=false`, but normally in addition or alternatively to that you
will want to add your own error page replacing the whitelabel one. Exactly how you do this
depends on the templating technology that you are using. For example, if you are using
Thymeleaf you would add an `error.html` template and if you are using FreeMarker you would