Nginx: Would Cache Background On Ensure Every Item is Always Served from Cache

JM John

3/24/24, 9:53 PM

I don't want anything served directly from the application. If an item is expired, Nginx should serve stale and update it in the background. I have set inactive duration to 7 days.

Would this configuration work?

    ## For 200 and 301 make the cache valid for 1s seconds.
fastcgi_cache_valid 200 10m;
fastcgi_cache_valid 301 1s;
## For 302 make it valid for 1 minute.
fastcgi_cache_valid 302 1m;
## For 404 make it valid 1 second.
fastcgi_cache_valid 404 1d; 

## If there are any upstream errors or the item has expired use
## whatever it is available.
fastcgi_cache_lock on;
fastcgi_cache_use_stale error timeout updating invalid_header http_500;
fastcgi_cache_background_update on;

0 + 0

nginx

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Nginx: Would Cache Background On Ensure Every Item is Always Served from Cache

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.