Clarify the role of views with Spring MVC
This commit adds a section to the reference docs that explains views live within the trust boundary of the application, and the security implications thereof. Closes gh-24777
This commit is contained in:
parent
c42a0eeb38
commit
9fb614a5c6
|
@ -7,8 +7,11 @@ Thymeleaf, Groovy Markup Templates, JSPs, or other technologies, is primarily a
|
|||
of a configuration change. This chapter covers view technologies integrated with
|
||||
Spring MVC. We assume you are already familiar with <<mvc-viewresolver>>.
|
||||
|
||||
|
||||
|
||||
WARNING: The views of a Spring MVC application live within the internal trust boundaries of that
|
||||
application.
|
||||
Views have access to all the beans of your application context.
|
||||
As such, it is not recommended to use Spring MVC's template support in applications where the
|
||||
templates are editable by external sources, since this can have security implications.
|
||||
|
||||
[[mvc-view-thymeleaf]]
|
||||
== Thymeleaf
|
||||
|
|
Loading…
Reference in New Issue