shreemaan-abhishek opened a new pull request, #13978: URL: https://github.com/apache/apisix/pull/13978
### Description The `X-Forwarded-*` headers that `forward-auth` sends to the authorization service describe the request as the client sent it: the client's scheme, method, host, URI and source IP. When `proxy-rewrite` is configured on the same route, the upstream receives the rewritten scheme, method, host and URI, while these headers keep carrying the client values. The docs listed the headers as bare names (`X-Forwarded-Uri`: URI), which makes that easy to miss when writing an authorization policy against upstream paths. This clarifies the behaviour in both the English and Chinese docs, and documents how to forward the URI the upstream actually receives using `extra_headers` with `$upstream_uri`. Docs only, no behaviour change. #### Which issue(s) this PR fixes: N/A ### Checklist - [x] I have explained the need for this PR and the problem it solves - [x] I have explained the changes or the new features added to this PR - [ ] I have added tests corresponding to this change - [x] I have updated the documentation to reflect this change - [x] I have verified that this change is backward compatible (If not, please discuss on the [APISIX mailing list](https://github.com/apache/apisix/tree/master#community) first) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
