Mercurial > hg > nginx-site
view xml/en/docs/faq/variables_in_config.xml @ 1978:8f1a568a8bbf
Documented "TLSv1.3" parameter of the "ssl_protocols" directive.
While here, cleaned up a note about using OpenSSL on older nginx versions.
author | Sergey Kandaurov <pluknet@nginx.com> |
---|---|
date | Tue, 25 Apr 2017 18:17:41 +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>