Nginx not passing custom headers to hit the backend(Node js)

Question

I have used self-signed certificate in nginx. The request from UI(React js) is hitting in the backend, but NGINX is not passing the headers to the backend. My nginx configuration file is as follow:

server {
        listen 443 ssl;
        ssl on;
        server_name SERVER_NAME;
        ssl_certificate /etc/ssl/certs/nginx-selfsigned.crt;
        ssl_certificate_key /etc/ssl/private/nginx-selfsigned.key;
        #add_header Strict-Transport-Security max-age=31536000;
        add_header Cache-Control no-cache;
        location / {
                root  PATH_TO_FRONTEND;
                try_files $uri $uri/ /index.html$is_args$args;
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection 'upgrade';
                proxy_set_header Host $host;
                proxy_cache_bypass $http_upgrade;
        }
        location ~* api/(.*) {
                proxy_pass http://127.0.0.1:8080$request_uri; // BACKEND
                proxy_redirect off;
                proxy_set_header Host $host;
                add_header Cache-Control no-cache;
        } }

I get the following error in the browser:

An SSL certificate error occurred when fetching the script.

sw.js Failed to load resource: net::ERR_INSECURE_RESPONSE

login:1 Uncaught (in promise) DOMException: Failed to register a ServiceWorker: An SSL certificate error occurred when fetching the script.

Are you trying to debug the fact that "NGINX is not passing the headers to the backend" or the browser error? If you're using a self-signed certificate, it sounds natural that your browser would not accept it. — Kent Shikama
– Kent Shikama, Commented Dec 23, 2017 at 7:50
@kshikama I am a bit confused why NGINX is not passing the headers to the backend. — Dinesh Madanlal
– Dinesh Madanlal, Commented Dec 23, 2017 at 7:52

Kent Shikama · Accepted Answer · 2017-12-23 07:56:58Z

1

Try adding

proxy_pass_header Server;

to your location block. It effectively says to pass through the sender's headers to the backend.

answered Dec 23, 2017 at 7:56

Kent Shikama

4,0903 gold badges27 silver badges56 bronze badges

Sign up to request clarification or add additional context in comments.

7 Comments

Dinesh Madanlal Over a year ago

It is still not passing the headers to the backend @kshikama

Kent Shikama Over a year ago

Hmm no idea then. If you don't get any other answers, I suggest turning off SSL (switching to port 80) and commenting out the cache-control no-cache and see if that is affecting anything.

Dinesh Madanlal Over a year ago

I want SSL for one of my requirements. Anyhow, Thanks @kshikama for your effort.

Kent Shikama Over a year ago

Yeah I didn't suggest to permanently turn it off - just to debug.

Dinesh Madanlal Over a year ago

It works if SSL is off. I think there is something wrong in the NGINX configuration. The request hits the backend but NGINX prevents the headers.

|

Yashas · Accepted Answer · 2020-11-20 11:14:39Z

0

I had the same issue. Apparently nginx blocks custom headers which have underscore in them. Please look at this if you are using underscore in your headers: https://serverfault.com/a/1003572

answered Nov 20, 2020 at 11:14

Yashas

9999 silver badges18 bronze badges

Collectives™ on Stack Overflow

Nginx not passing custom headers to hit the backend(Node js)

2 Answers 2

7 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

7 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related