describe the new APIFW_SERVER_REQUEST_HOST_HEADER env var (#105)

docs/installation-guides/docker-container.md

@@ -98,6 +98,7 @@ Pass API Firewall configuration in **docker-compose.yml** → `services.api-fire
 | `APIFW_SHADOW_API_UNKNOWN_PARAMETERS_DETECTION` | This specifies whether requests are identified as non-matching the specification if their parameters do not align with those defined in the OpenAPI specification. The default value is `true`.<br><br>If running API Firewall in the [`API` mode](api-mode.md), this variable takes on a different name `APIFW_API_MODE_UNKNOWN_PARAMETERS_DETECTION`. | No |
 | `APIFW_MODSEC_CONF_FILES` | Allows to set the list of [ModSecurity](../migrating/modseс-to-apif.md) configuration files. The delimiter is ;. The default value is [] (empty). Example: `APIFW_MODSEC_CONF_FILES=modsec.conf;crs-setup.conf.example`. | No |
 | `APIFW_MODSEC_RULES_DIR` | Allows to set the [ModSecurity](../migrating/modseс-to-apif.md) directory with the rules that should be loaded. The files with the `*.conf` wildcard will be loaded from the directory. The default value is `""`. | No |
+| `APIFW_SERVER_REQUEST_HOST_HEADER` | Sets a custom `Host` header for requests forwarded to your backend after API Firewall validation. | No |
 
 **With `services.api-firewall.ports` and `services.api-firewall.networks`**, set the API Firewall container port and connect the container to the created network. The provided **docker-compose.yml** instructs Docker to start API Firewall connected to the `api-firewall-network` [network](https://docs.docker.com/network/) on the port 8088.
 

docs/installation-guides/graphql/docker-container.md

@@ -103,6 +103,7 @@ Pass API Firewall configuration in **docker-compose.yml** → `services.api-fire
 | `APIFW_LOG_LEVEL` | API Firewall logging level. Possible values:<ul><li>`DEBUG` to log events of any type (INFO, ERROR, WARNING, and DEBUG).</li><li>`INFO` to log events of the INFO, WARNING, and ERROR types.</li><li>`WARNING` to log events of the WARNING and ERROR types.</li><li>`ERROR` to log events of only the ERROR type.</li><li>`TRACE` to log incoming requests and API Firewall responses, including their content.</li></ul> The default value is `DEBUG`. Logs on requests and responses that do not match the provided schema have the ERROR type. | No |
 | `APIFW_SERVER_DELETE_ACCEPT_ENCODING` | If it is set to `true`, the `Accept-Encoding` header is deleted from proxied requests. The default value is `false`. | No |
 | `APIFW_LOG_FORMAT` | The format of API Firewall logs. The value can be `TEXT` or `JSON`. The default value is `TEXT`. | No |
+| `APIFW_SERVER_REQUEST_HOST_HEADER` | Sets a custom `Host` header for requests forwarded to your backend after API Firewall validation. | No |
 
 **With `services.api-firewall.ports` and `services.api-firewall.networks`**, set the API Firewall container port and connect the container to the created network.
 

docs/release-notes.md

@@ -6,7 +6,9 @@ This page describes new releases of Wallarm API Firewall.
 
 * Dependency upgrade
 * Supported new interface for the `api` mode usage, only for internal use
-* Added the APIFW_SERVER_REQUEST_HOST_HEADER env variable to set the custom host value for proxied requests
+* Added the `APIFW_SERVER_REQUEST_HOST_HEADER` environment variable to set a custom `Host` header for requests forwarded to your backend after API Firewall validation
+
+    This variable is supported in the [`PROXY`](installation-guides/docker-container.md) and [`graphql`](installation-guides/graphql/docker-container.md) API Firewall modes.
 
 ## v0.7.2 (2024-04-16)