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

More polishing on forwarded header scenarios 

See gh-31491
This commit is contained in:
rstoyanchev 2023-10-25 16:17:27 +01:00
parent c5def4c97a
commit fe7b6ddf88
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
framework-docs/modules/ROOT/partials/web/forwarded-headers.adoc
View File

@ -95,10 +95,10 @@ have the empty prefix override server prefixes `/app1` and `/app2`.
==== ====
A common case for this deployment scenario is where licenses are paid per A common case for this deployment scenario is where licenses are paid per
production application server, and it is preferable to deploy multiple applications per production application server, and it is preferable to deploy multiple applications per
server to reduce fees. Another case is I/O bound applications, and the need to deploy server to reduce fees. Another reason is to run more applications on the same server in
multiple applications to each application server to consume less resources. order to share the resources required by the server to run.
In this scenario, applications need a non-empty context root because there are multiple In these scenarios, applications need a non-empty context root because there are multiple
applications on the same server. However, this should not be visible in URL paths of applications on the same server. However, this should not be visible in URL paths of
the public API where applications may use different subdomains that provides benefits the public API where applications may use different subdomains that provides benefits
such as: such as: