From 5ff7ce03cfc45d2ef5cb0dee1e2c8cd74a13996a Mon Sep 17 00:00:00 2001 From: Zipeng WU Date: Fri, 8 Jul 2022 11:04:02 +0200 Subject: [PATCH] SONAR-16567 Add documentation about the expiration date header in the response --- server/sonar-docs/src/pages/setup/operate-server.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/server/sonar-docs/src/pages/setup/operate-server.md b/server/sonar-docs/src/pages/setup/operate-server.md index b951c7427c2..b2e79ffdcc2 100644 --- a/server/sonar-docs/src/pages/setup/operate-server.md +++ b/server/sonar-docs/src/pages/setup/operate-server.md @@ -199,6 +199,9 @@ server { } ``` +### Forward SonarQube custom headers +SonarQube adds custom HTTP headers in order for some features to function properly. The reverse proxy should be configured to forward the following header: `sq-authentication-token-expiration`. + ## Secure your Network To further lock down the communication in between the reverse proxy and SonarQube, you can define the following network rules: @@ -214,4 +217,4 @@ you can further segrement your network configuration if you specify a frontend n Network | Parameter | Description | default ---|---|---|--- Frontend | `sonar.web.host` | Frontend HTTP Network | 0.0.0.0 -Elasticsearch | `sonar.search.host` | Elasticsearch Network | 127.0.0.1 \ No newline at end of file +Elasticsearch | `sonar.search.host` | Elasticsearch Network | 127.0.0.1 -- 2.39.5