From 98f76698c87594cd07c2e0074b31ee75dd8d3824 Mon Sep 17 00:00:00 2001 From: Mahatma_Fatal_Error Date: Tue, 25 Jul 2023 14:12:15 +0200 Subject: [PATCH] Fix server.forward-headers-strategy documentation See gh-36564 --- .../spring-boot-docs/src/docs/asciidoc/howto/webserver.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/howto/webserver.adoc b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/howto/webserver.adoc index 11f53e384dd..a971511cc60 100644 --- a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/howto/webserver.adoc +++ b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/howto/webserver.adoc @@ -445,7 +445,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 Kubernetes, the configprop:server.forward-headers-strategy[] property defaults to `NATIVE`. In all other instances, it defaults to `NONE`.