paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 34 Packages Projects Releases Wiki Activity

Proxying doc changed

Browse Source 
Signed-off-by: deepthi-28 <deepthi.ajith@infosys.com>
This commit is contained in:
deepthi-28
2025-03-06 11:11:17 +05:30
parent 753c1a1c78
commit b229f0d9de
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/plugins/proxying.md
+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.