Earlier quoted context omitted.
Because until 0.7 nginx lacked a caching system, and so it made sense to use both. Now it doesn't.
And even now there's no way of manually expiring a cached page without using a third party unsupported plugin (IIRC) I still love Nginx though :-)
Tell HN: Have a look at Varnish
21–24 of 24 posts
Re: Tell HN: Have a look at Varnish
#22Earlier quoted context omitted.
This is a question that interests me as a Varnish user with a several-hundred-line VCL. We exclude certain URLs from caching altogether, drop certain cookies but not others, drop certain querystring params but not others, cache separate versions of the same page for mobile and non-mobile browsers, do limited caching behind basic auth, purge certain pages from cache when a post gets published, etc. VCL isn't the most…
I haven't used nginx caching in depth, but I can make a more general point about nginx scripting: It sucks. Hard. You can get fancy[1] by writing your own modules or by building on top of helpers like ngx_devel_kit, but it gets messy very quick. Implementing complex rules inside the config file is possible to a degree - but an utter nightmare. The syntax is extremely limited and the semantics are hard to predict (ord…
[1] http://github.com/chaoslawful/lua-nginx-module/commit/26d9dc...