Mercurial > hg > nginx-site
view xml/en/docs/faq/variables_in_config.xml @ 1826:da6a3e401b26
Slightly reformatted the error_page description.
Information about directives inheritance was moved to the end.
Blocks describing various syntaxes of the "uri" argument were
put in the following order:
- internal redirect to the specified /uri;
- internal redirect to a named location;
- URL redirection.
author | Ruslan Ermilov <ru@nginx.com> |
---|---|
date | Mon, 24 Oct 2016 11:57:46 +0300 |
parents | 764fbac1b8b4 |
children |
line wrap: on
line source
<!-- Copyright (C) Nginx, Inc. --> <!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" rev="1"> <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>