NGINX is not forwarding a header value when using proxy_pass

Question

I have the following setup and configured to send all /api requests to a different server:

location /api {
    proxy_pass              https://myapp.herokuapp.com;
    rewrite                 ^/api/(.*)              /$1     break;
}

My app sends a header (USER_CUSTOMER), when communicating directly with myapp.herokuapp.com from the app it works, but when requesting through the proxy server, the value appears NULL on the API Server.

The following works in NGINX, but I need the App to be able to set the value of USER_CUSTOMER.

location /api {
    proxy_pass              https://app.herokuapp.com;
    proxy_set_header        USER_CUSTOMER           ABC;
    rewrite                 ^/api/(.*)              /$1     break;
}

I may have additional headers to send in the future, so I'm hoping there is a flag to pass all headers from the proxy to the API Server.

Ubuntu
nginx/1.1.19

score 35 · Answer 1 · answered Apr 06 '14 at 06:57

35

The header attribute USER_CUSTOMER is invalid syntax. Underscores are not valid in header attributes.

There is a workaround but best solution is to rewrite the attribute to valid syntax.

Workaround is to set the following where you specify the server name in config:

underscores_in_headers on;

answered Apr 06 '14 at 06:57

dallasclark

771
2
7
17

1

Not work in my case, the error log shows: nginx: [emerg] "underscores_in_headers" directive is not allowed here in nginx.conf:55 – thinkhy Apr 17 '16 at 13:21
1

thx this worked! – Magico Dec 12 '16 at 13:00
Worked!! But when request is called from the android app it shows me undefined. – Vishnu S Babu Nov 30 '17 at 07:04

score 9 · Answer 2 · answered Apr 05 '14 at 22:49

9

I think you are looking for proxy_pass_request_headers option. Set it to on:

location /api {
    proxy_pass_request_headers      on;
    proxy_pass                      https://app.herokuapp.com;
    proxy_set_header                USER_CUSTOMER              ABC;
    rewrite                         ^/api/(.*)                 /$1     break;
}

answered Apr 05 '14 at 22:49

ek9

2,093
4
19
23

Unfortunately, this has made no affect. – dallasclark Apr 06 '14 at 06:08
3

@dallasclark: Makes sense, because the default is that it is on... http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_pass_request_headers – OmarOthman Feb 23 '17 at 19:40
5 years later, this works :) – Miroslav Trninic Sep 12 '19 at 20:43

score 0 · Answer 3 · answered Jul 15 '22 at 15:04

I faced this issue today (jul 2022), and it was fixed adding a final / to the location route.

I mean, this wasn't working properly for me

location /api {
    proxy_pass              https://myapp.herokuapp.com;
    rewrite                 ^/api/(.*)              /$1     break;
}

but when I defined it as:

location /api/ {
    proxy_pass              https://myapp.herokuapp.com;
    rewrite                 ^/api/(.*)              /$1     break;
}

it worked. Not sure about what the final slash is doing, but maybe this could help to someone.

NGINX is not forwarding a header value when using proxy_pass

3 Answers3