Skip to content

Commit 1c05ad2

Browse files
Polish "Clarify conventions for custom error pages in WebFlux"
See gh-34534
1 parent f285364 commit 1c05ad2

File tree

1 file changed

+3
-3
lines changed
  • spring-boot-project/spring-boot-docs/src/docs/asciidoc/web

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -141,10 +141,10 @@ include::code:MyExceptionHandlingController[]
141141

142142
[[web.reactive.webflux.error-handling.error-pages]]
143143
===== Custom Error Pages
144-
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.
144+
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.
145145
Error pages can either be static HTML (that is, added under any of the static resource directories) or built with templates.
146-
The name of the file should be the exact status code or a series mask, or "error" for a fallback if nothing else matches.
147-
Note the difference with MVC where "error" is the name of the default error `View`, whereas here it is "error/error".
146+
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.
147+
Note that the path to the default error view is `error/error`, whereas with Spring MVC the default error view is `error`.
148148

149149
For example, to map `404` to a static HTML file, your directory structure would be as follows:
150150

0 commit comments

Comments
 (0)