Nginx – How to check Cookie header line and custom cache on Nginx

nginx

I am trying cache for my website use Nginx Proxy module and has following requirements:

If request has cookie (in request header)

The response will use cache of Nginx
Hide Set-Cookie header line

If request has no cookie (in request header)

Foward request to backend
Don't hide h Set-Cookie header line

I use If (of rewrite module) and any directive:

if (!-e $http_cookie) 
{
  set $not_cache_rq 0;
  set $not_cache_rp 0;
}
if ($http_cookie) {
  set $not_cache_rq 1;
  set $not_cache_rp 1;
}
proxy_cache_bypass $not_cache_rq;
proxy_no_cache $not_cache_rp;
proxy_hide_header  Set-Cookie;

I do not know how to call cookie proxy_hide_header option when has cookie and no cookie on header line.

Please help me. Many thanks.

====

Hi poige

I manage a customer's website. If cookies are set, all request and response contain the Cookie header line.

If a response is cached. The cache will be Nginx returns for all clients and Set-Cookie header line will make all users share a cookie value (this value is the session, it must be different for each user).

I want if the user do not has a session (ie no cookie exists – request header line will not have the Cookie line), the request will be pushed into the backend (apache) for processing and returns the cookie to the user.

If the user already has session (ie a cookie in the request line) then Nginx will return the cache and the cache has no Set-Cookie line)

Many thanks!

Best Answer

If you set your proxy_cache_key to some string that contains cookie variable, than all users with different cookies will have its own cached version of page.

Like this

  proxy_cache_key  "$host$request_uri$cookie_auth_id";

This will allow both caching and distinctive pages for different users.

Related Solutions

Nginx – How to Set Up as a Caching Reverse Proxy

I don't think that there is a way to explicitly invalidate cached items, but here is an example of how to do the rest. Update: As mentioned by Piotr in another answer, there is a cache purge module that you can use. You can also force a refresh of a cached item using nginx's proxy_cache_bypass - see Cherian's answer for more information.

In this configuration, items that aren't cached will be retrieved from example.net and stored. The cached versions will be served up to future clients until they are no longer valid (60 minutes).

Your Cache-Control and Expires HTTP headers will be honored, so if you want to explicitly set an expiration date, you can do that by setting the correct headers in whatever you are proxying to.

There are lots of parameters that you can tune - see the nginx Proxy module documentation for more information about all of this including details on the meaning of the different settings/parameters: http://nginx.org/r/proxy_cache_path

http {
  proxy_cache_path  /var/www/cache levels=1:2 keys_zone=my-cache:8m max_size=1000m inactive=600m;
  proxy_temp_path /var/www/cache/tmp; 


  server {
    location / {
      proxy_pass http://example.net;
      proxy_cache my-cache;
      proxy_cache_valid  200 302  60m;
      proxy_cache_valid  404      1m;
    }
  }
}

Nginx: using X-Accel-Expires with Cache-Control

Then,

Modify the upstream to send X-Accel-Expires header everytime or add it with add_header directive (using for instance $http_cache_control in a if statement).
Ignore Cache-Control header for caching everytime.
Use an upstream block.

map $upstream_http_cache_control $cache_control_value {
    "~^max-age=(?<duration>\d+)$" "$duration";
}

server {

   listen 127.0.0.1:80;

    upstream nodes {
        server foo;
    }

    location / {

        if ($upstream_http_x_accel_expires = '') {
            add_header "X-Accel-Expires" $cache_control_value;
        }

        proxy_set_header "Host" $host;
        proxy_pass http://nodes;
    }

}

server {

   server_name mydomain.com;

   listen X.X.X.X:80;

   upstream intermediate {
       server 127.0.0.1;
   }

   location / {
       proxy_set_header "Host" $host;
       proxy_pass http://intermediate;
       proxy_ignore_headers 'Cache-Control';
       proxy_cache mycache;
   }

}

For the last case refer to the first point or use proxy_cache_valid, but with this last paremeter you can't make the timeout dynamic. You need some coherent workflow at one point.

Best Answer

Related Solutions

Nginx – How to Set Up as a Caching Reverse Proxy

Nginx: using X-Accel-Expires with Cache-Control

Related Topic