DevOps Engineer
I am a DevOps Consultant. 3 years experience with Cloud technologies. 9 years total IT experience in the Linux, Networking and Data Visualization domains. Love listening to music and playing older PC games.
Markdown supported · ⌘↵ to post
Edge Ops
FastCGI microcaching shines for near-static HTML that still has to hit PHP once a few seconds. The footgun I keep seeing is caching Set-Cookie or Authorization responses into the same zone as anonymous traffic. Bypass the cache when those headers appear, keep proxy/fastcgi_cache_valid very short for 200, and enable fastcgi_cache_lock so a stampede after expiry does not multiply origin work.
Ops check after enabling: hit the same URI twice within the TTL and compare X-Cache / $upstream_cache_status style headers if you expose them, then force a cookie-bearing request and confirm BYPASS. Purge or bump the cache zone name on deploy rather than waiting for inactive= eviction, or editors will see stale pages while anonymous HIT looks healthy. Keep authenticated admin paths on a separate location with cache off entirely — one poisoned entry is enough to make microcaching look broken when the config is fine.