NGINX Reverse Proxy : Is it possible to proxy cache ONLY 404 (or other) html status codes

cachenginxreverse-proxy

With nginx, latest, is it possible to proxy cache ONLY specific html status code responses?

We use 410 status codes for some responses.

These are checked against our database.

When the said content is flagged as removed for ever (410), a 410 status code is sent.

This content is gone forever.

We would like to proxy cache ONLY these results.

Is this possible?

Best Answer

Use proxy_cache_valid directive, e.g.:

proxy_cache_valid 410      1m;
proxy_cache_valid any      0;

http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cache_valid

Related Solutions

Nginx Stale Cache and proxy_cache_path

Turns out that this is not currently possible with Nginx. I ended up setting up Varnish with a long TTL (7 days) as well as a long grace setting (2 days). I then have a script hit each URL every few days and force a warming of the cache.

Given the amount of content that I need to cache, and how infrequently each item is accessed, I was at first concerned that the cost of running Varnish would be prohibitive (all that RAM!) -- which is why I was looking at Nginx's file based caching. However, Varnish does indeed have a file backed caching option that has been working very well for me. So far my cache is about 80GB and performing very nicely!

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 Stale Cache and proxy_cache_path

NGINX Reverse Proxy – URL Rewrite

Related Topic