Merge pull request #29027 from deepthi-28/doc-proxying

Proxying doc changed
This commit is contained in:
Fredrik Adelöw
2025-03-11 12:14:31 +01:00
committed by GitHub
+3 -3
View File
@@ -110,13 +110,13 @@ There are also additional settings:
from the target.
By default, the proxy will only forward safe HTTP request headers to the target.
Those are based on the headers that are considered safe for CORS and includes
These are based on the headers that are considered safe for CORS and include
headers like `content-type` or `last-modified`, as well as all headers that are
set by the proxy. If the proxy should forward other headers like
set by the proxy. If the proxy should forward other headers, like
`authorization`, this must be enabled by the `allowedHeaders` config, for
example `allowedHeaders: ['Authorization']`. This should help to not
accidentally forward confidential headers (`cookie`, `X-Auth-Request-User`) to
third-parties.
third parties.
The same logic applies to headers that are sent from the target back to the
frontend.