Skip to content

Document that server.forward-headers-strategy property defaults to native when running on Kubernetes #36564

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Document that server.forward-headers-strategy property defaults to native when running on Kubernetes #36564

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3894d5a
Docs: server.forward-headers-strategy property defaults to NATIVE als…
MahatmaFatalError Jul 25, 2023
dc4d216
Update webserver.adoc
MahatmaFatalError Jul 25, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion spring-boot-project/spring-boot-docs/src/docs/asciidoc/howto/webserver.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -443,7 +443,7 @@ You can register it as a servlet filter in your application by setting `server.f
TIP: If you are using Tomcat and terminating SSL at the proxy, configprop:server.tomcat.redirect-context-root[] should be set to `false`.
This allows the `X-Forwarded-Proto` header to be honored before any redirects are performed.

NOTE: If your application runs in Cloud Foundry or Heroku, the configprop:server.forward-headers-strategy[] property defaults to `NATIVE`.
NOTE: If your application runs in Cloud Foundry, Heroku or K8s, the configprop:server.forward-headers-strategy[] property defaults to `NATIVE`.
In all other instances, it defaults to `NONE`.


Expand Down