Hi, This problem was resolved with the help of the cloud provider. Turns out I need to set the Host header proxy_set_header Host upstreamhostname; It wasn't exactly clear any any docs (on their end) this was necessary but glad it's solved and makes some sense as well I suppose. Thanks for all your suggestions Francis. Francis Daly Wrote: --------------------------------------------by Sesshomurai - Nginx Mailing List - English
Here is what NGINX is trying to pass upstream. I set up a local mini HTTP server to print the requests. curl -i -H "x-api-key:APIKEY" -H "userAccount:USER1" https://localhost/test --insecure 127.0.0.1 - - [02/Jan/2019 12:13:51] "GET / HTTP/1.0" 200 - ERROR:root:Host: localhost X-Real-IP: 127.0.0.1 Connection: close User-Agent: curl/7.61.0 Accept: */* x-aby Sesshomurai - Nginx Mailing List - English
Hi Francis, Yeah, there might be more going on here that meets the eye. But here are the curl commands that are producing different results. I am looking into the upstream server as well, but the difference would imply something about NGINX is not the same as running curl from command line. Here are the details. 1. RETURNING THE REQUEST HEADERS FROM NGINX. OK ==========================by Sesshomurai - Nginx Mailing List - English
Actually, had the wrong variable name in location for x-api-key, so now I get the correct request header printed back to me $ curl -i -H "x-api-key:somekey" -H "userAccount:someaccount" https://localhost/ --insecure HTTP/1.1 200 OK Server: nginx/1.10.3 (Ubuntu) Date: Tue, 01 Jan 2019 17:30:28 GMT Content-Type: application/octet-stream Content-Length: 127 Connection: kby Sesshomurai - Nginx Mailing List - English
If I run the curl using the proxy URL directly it works just fine.by Sesshomurai - Nginx Mailing List - English
HI Francis, Turns out it's not passing the other header I need, "x-api-key". $ curl -i -H "x-api-key:somevalue" -H "userAccount:someaccount" https://localhost/somepath --insecure HTTP/1.1 200 OK Server: nginx/1.10.3 (Ubuntu) Date: Tue, 01 Jan 2019 16:47:15 GMT Content-Type: application/octet-stream Content-Length: 91 Connection: keep-alive request: GETby Sesshomurai - Nginx Mailing List - English
Hi, I am having a problem with NGINX not forwarding a request header to my proxy. Here is the location: location /xyz { proxy_pass_request_headers on; proxy_pass https://someserver/; } I make the call passing "userAccount" header and it never gets sent to the proxy, but if I declare it in the location, it does get passed. Other headers aby Sesshomurai - Nginx Mailing List - English