@angular/ssr 22.0.4 → 22.1.0-next.1

package/types/_app-engine-chunk.d.ts

@@ -68,12 +68,12 @@ interface AngularAppEngineOptions {
      */
     allowedHosts?: readonly string[];
     /**
-     * Extends the scope of trusted proxy headers (`X-Forwarded-*`).
+     * Extends the scope of trusted proxy headers (`Forwarded` or `X-Forwarded-*`).
      *
      * @remarks
      * **This is a security-sensitive option!**
      *
-     * When `trustProxyHeaders` is enabled, request headers such as `X-Forwarded-Host` and
+     * When `trustProxyHeaders` is enabled, request headers such as `Forwarded`, `X-Forwarded-Host`, and
      * `X-Forwarded-Prefix` are trusted by the server and used for routing. These
      * headers must be strictly validated and provided by a trusted client (e.g., at a reverse proxy, load
      * balancer, or API gateway) and must *not* be provided by untrusted end users.

package/types/node.d.ts

@@ -195,7 +195,7 @@ declare function writeResponseToNodeResponse(source: Response, destination: Serv
  * @param trustProxyHeaders - A boolean or an array of proxy headers to trust when constructing the request URL.
  *
  * @remarks
- * When `trustProxyHeaders` is enabled, headers such as `X-Forwarded-Host` and
+ * When `trustProxyHeaders` is enabled, headers such as `Forwarded`, `X-Forwarded-Host`, and
  * `X-Forwarded-Prefix` should ideally be strictly validated at a higher infrastructure
  * level (e.g., at the reverse proxy or API gateway) before reaching the application.
  *