Current Behavior
Currently, whether we configure conf.auth_header or not, APISIX HTTP logger will add the authorization header.

Log server will reject such requests since they violate the HTTP syntax.

Expected Behavior
Avoid adding this header if conf.auth_header is empty.
Error Logs
No response
Steps to Reproduce
Environment
- APISIX version (run
apisix version): latest
- Operating system (run
uname -a):
- OpenResty / Nginx version (run
openresty -V or nginx -V):
- etcd version, if relevant (run
curl http://127.0.0.1:9090/v1/server_info):
- APISIX Dashboard version, if relevant:
- Plugin runner version, for issues related to plugin runners:
- LuaRocks version, for installation issues (run
luarocks --version):
Current Behavior
Currently, whether we configure
conf.auth_headeror not, APISIX HTTP logger will add theauthorizationheader.Log server will reject such requests since they violate the HTTP syntax.
Expected Behavior
Avoid adding this header if
conf.auth_headeris empty.Error Logs
No response
Steps to Reproduce
Environment
apisix version): latestuname -a):openresty -Vornginx -V):curl http://127.0.0.1:9090/v1/server_info):luarocks --version):