gaobo0202 opened a new issue #5858: URL: https://github.com/apache/apisix/issues/5858
### Issue description Our upstream service relies on the parameter of x-forwarded-proto and uses the proxy rewrite plug-in to rewrite the parameter. The upstream service does not get the correct rewritten value 1. When APISIX configures the route, use proxy rewrite to rewrite the x-forwarded-proto parameter to http 2. After calling the domain name, it is found that the x-forwarded-proto obtained upstream is still HTTPS After reading the code and the previous issue about the parameter rewriting, it is found that the proxy rewrite plug-in modification of the parameter will not take effect. I modified the code of APISIX myself to make the proxy rewrite configuration x-forwarded-proto effective. Is this another good repair method?   ### Environment - apisix version (cmd: `apisix version`):2.10.0 - OS (cmd: `uname -a`): - OpenResty / Nginx version (cmd: `nginx -V` or `openresty -V`): - etcd version, if have (cmd: run `curl http://127.0.0.1:9090/v1/server_info` to get the info from server-info API): - apisix-dashboard version, if have: - the plugin runner version, if the issue is about a plugin runner (cmd: depended on the kind of runner): - luarocks version, if the issue is about installation (cmd: `luarocks --version`): ### Steps to reproduce Use proxy-rewrite to overwrite x-forwarded-proto ### Actual result Override does not take effect ### Error log no error log ### Expected result No response -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
