Nginx – Inject cookie with Nginx reverse proxy

nginxreverse-proxy

With Nginx as a reverse proxy I'd like to inject a cookie for backend systems to consume.

location /delegate {
  proxy_pass                        <some-url>;
  proxy_set_header Host             $host;
  proxy_set_header X-Forwarded-For  $remote_addr;
  proxy_set_header X-Request-ID     $request_id;
  # some more
  # here: inject a new cookie into `cookie` request header
}

As I want the cookie to be consumed by downstream systems this isn't about the add_header Set-Cookie instruction (which is for the response going back to the client).

Best Answer

You can provide server with cookies via

proxy_set_header Cookie "name=john; age=30; male=1";

Related Solutions

NGINX – Proxy HTTPS Requests to an HTTP Backend

The type of proxy you are trying to set up is called a reverse proxy. A quick search for reverse proxy nginx got me this page:

http://intranation.com/entries/2008/09/using-nginx-reverse-proxy/

In addition to adding some useful features like an X-Forwarded-For header (which will give your app visibility into the actual source IP), it specifically does:

proxy_redirect off

Good luck! :)

NGINX Reverse Proxy – URL Rewrite

Any redirect to localhost doesn't make sense from a remote system (e.g. client's Web browser). So the rewrite flags permanent (301) or redirect (302) are not usable in your case.

Please try following setup using a transparent rewrite rule:

location  /foo {
  rewrite /foo/(.*) /$1  break;
  proxy_pass         http://localhost:3200;
  proxy_redirect     off;
  proxy_set_header   Host $host;
}

Use curl -i to test your rewrites. A very subtle change to the rule can cause nginx to perform a redirect.

Best Answer

Related Solutions

NGINX – Proxy HTTPS Requests to an HTTP Backend

NGINX Reverse Proxy – URL Rewrite

Related Topic