Solution to the problem of information loss with "_" in header when using Nginx proxy

Preface

When developing a gateway project, the signature sign_key information is put into the request header when making a request, and then taken out of the header when receiving the request. This works when debugging locally, but after going online, it is found that it cannot be obtained through the Nginx proxy.

location / {
 proxy_set_header X-Real-IP $remote_addr;
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 proxy_set_header Host $http_host;
 proxy_set_header X-Nginx-Proxy true;

 add_header Proxy-Node $upstream_addr;
 add_header Proxy-Status $upstream_status; 
 
 proxy_http_version 1.1;
 proxy_pass http://tianusa;
 }

Later I found out that the reason was that Nginx had some restrictions on headers, and underscores (_) were not supported.

Solution:

1. No underscores

Change the underscore _ to something else, such as sign_key to sign-key

2. Remove the limitations of Nginx from the root

By default, Nginx will automatically ignore any '_' in the request header.

The solution is to add the following configuration to the http section of the nginx.conf configuration file in nginx:

underscores_in_headers on; (default underscores_in_headers is off)

Summarize

The above is the full content of this article. I hope that the content of this article will have certain reference learning value for your study or work. If you have any questions, you can leave a message to communicate. Thank you for your support for 123WORDPRESS.COM.