Mercurial > hg > nginx-site
view xml/en/docs/faq/variables_in_config.xml @ 504:695f83494c19
Emphasized on what the "updating" parameter of the "proxy_cache_use_stale"
directive achieves. Referenced the "proxy_cache_lock" directive from there,
which has similar effect when populating a new cache element.
author | Ruslan Ermilov <ru@nginx.com> |
---|---|
date | Tue, 24 Apr 2012 06:54:47 +0000 |
parents | ec4626d04879 |
children | be54c443235a |
line wrap: on
line source
<!DOCTYPE article SYSTEM "../../../../dtd/article.dtd"> <article name="Is there a proper way to use nginx variables to make sections of the configuration shorter, using them as macros for making parts of configuration work as templates?" link="/en/docs/faq/variables_in_config.html" lang="en"> <section> <para> <initial>Q:</initial> Is there a proper way to use nginx variables to make sections of the configuration shorter, using them as macros for making parts of configuration work as templates? </para> <para> </para> <para> <initial>A:</initial> Variables should not be used as template macros. Variables are evaluated in the run-time during the processing of each request, so they are rather costly compared to plain static configuration. Using variables to store static strings is also a bad idea. Instead, a macro expansion and "include" directives should be used to generate configs more easily and it can be done with the external tools, e.g. sed + make or any other common template mechanism. </para> </section> </article>