root
/
spring-boot
mirror of https://github.com/spring-projects/spring-boot.git
1
0
Fork 0
Code Issues Actions 13 Packages Projects Releases Wiki Activity

Polish "Clarify conventions for custom error pages in WebFlux" 

See gh-34534
This commit is contained in:
Scott Frederick 2023-03-21 14:45:20 -05:00
parent f285364f22
commit 1c05ad2852
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
spring-boot-project/spring-boot-docs/src/docs/asciidoc/web/reactive.adoc
View File

@ -141,10 +141,10 @@ include::code:MyExceptionHandlingController[]
[[web.reactive.webflux.error-handling.error-pages]]
===== Custom Error Pages
If you want to display a custom HTML error page for a given status code, you can add views that resolve from "error/*", for example by adding files to an `/error` directory.
If you want to display a custom HTML error page for a given status code, you can add views that resolve from `error/*`, for example by adding files to a `/error` directory.
Error pages can either be static HTML (that is, added under any of the static resource directories) or built with templates.
The name of the file should be the exact status code or a series mask, or "error" for a fallback if nothing else matches.
Note the difference with MVC where "error" is the name of the default error `View`, whereas here it is "error/error".
The name of the file should be the exact status code, a status code series mask, or `error` for a default if nothing else matches.
Note that the path to the default error view is `error/error`, whereas with Spring MVC the default error view is `error`.
For example, to map `404` to a static HTML file, your directory structure would be as follows: