File tree 1 file changed +6
-1
lines changed
framework-docs/modules/ROOT/pages/web/webflux
1 file changed +6
-1
lines changed Original file line number Diff line number Diff line change @@ -184,9 +184,11 @@ xref:web/webflux/reactive-spring.adoc#webflux-exception-handler[Exceptions] in t
184
184
View resolution enables rendering to a browser with an HTML template and a model without
185
185
tying you to a specific view technology. In Spring WebFlux, view resolution is
186
186
supported through a dedicated xref:web/webflux/dispatcher-handler.adoc#webflux-resulthandling[HandlerResultHandler] that uses
187
- `ViewResolver` instances to map a String (representing a logical view name) to a `View`
187
+ `ViewResolver` instances to map a String (representing a logical view name) to a `View`
188
188
instance. The `View` is then used to render the response.
189
189
190
+ Web applications need to use a xref:web/webflux-view.adoc[View rendering library] to support this use case.
191
+
190
192
191
193
[[webflux-viewresolution-handling]]
192
194
=== Handling
@@ -238,6 +240,9 @@ operate in terms of logical view names. A view name such as
238
240
`redirect:/some/resource` is relative to the current application, while a view name such as
239
241
`redirect:https://example.com/arbitrary/path` redirects to an absolute URL.
240
242
243
+ NOTE: xref:web/webmvc/mvc-servlet/viewresolver.adoc#mvc-redirecting-forward-prefix[Unlike the Servlet stack],
244
+ Spring WebFlux does not support "FORWARD" dispatches, so `forward:` prefixes are not supported as a result.
245
+
241
246
242
247
[[webflux-multiple-representations]]
243
248
=== Content Negotiation
You can’t perform that action at this time.
0 commit comments