Syntax: zone name [size]; Default: — Context: upstream Defines the name and size of the shared memory zone that keeps the group’s configuration and run-time state that are shared between worker processes. Several groups may share the same zone. In this case, it is enough to specify the zone size only once. Additionally, as part of our commercial subscription, such groups allow changing the group membership or modifying the settings of a particular server without the need of resta

Syntax: xslt_types mime-type ...; Default: xslt_types text/xml; Context: http, server, location Enables transformations in responses with the specified MIME types in addition to “text/xml”. The special value “*” matches any MIME type (0.8.29). If the transformation result is an HTML response, its MIME type is changed to “text/html”.

Syntax: xslt_stylesheet stylesheet [parameter=value ...]; Default: — Context: location Defines the XSLT stylesheet and its optional parameters. A stylesheet is compiled at the configuration stage. Parameters can either be specified separately, or grouped in a single line using the “:” delimiter. If a parameter includes the “:” character, it should be escaped as “%3A”. Also, libxslt requires to enclose parameters that contain non-alphanumeric characters into single or dou

Syntax: zone name [size]; Default: — Context: upstream This directive appeared in version 1.9.0. Defines the name and size of the shared memory zone that keeps the group’s configuration and run-time state that are shared between worker processes. Several groups may share the same zone. In this case, it is enough to specify the size only once. Additionally, as part of our commercial subscription, such groups allow changing the group membership or modifying the settings of a parti

Syntax: xslt_string_param parameter value; Default: — Context: http, server, location This directive appeared in version 1.1.18. Defines the string parameters for XSLT stylesheets. XPath expressions in the value are not interpreted. The value can contain variables. There could be several xslt_string_param directives. These directives are inherited from the previous level if and only if there are no xslt_param and xslt_string_param directives defined on the current level.

Syntax: xml_entities path; Default: — Context: http, server, location Specifies the DTD file that declares character entities. This file is compiled at the configuration stage. For technical reasons, the module is unable to use the external subset declared in the processed XML, so it is ignored and a specially defined file is used instead. This file should not describe the XML structure. It is enough to declare just the required character entities, for example: <!ENTITY nbsp "

Syntax: xslt_last_modified on | off; Default: xslt_last_modified off; Context: http, server, location This directive appeared in version 1.5.1. Allows preserving the “Last-Modified” header field from the original response during XSLT transformations to facilitate response caching. By default, the header field is removed as contents of the response are modified during transformations and may contain dynamically generated elements or parts that are changed independently of the ori

Syntax: xslt_param parameter value; Default: — Context: http, server, location This directive appeared in version 1.1.18. Defines the parameters for XSLT stylesheets. The value is treated as an XPath expression. The value can contain variables. To pass a string value to a stylesheet, the xslt_string_param directive can be used. There could be several xslt_param directives. These directives are inherited from the previous level if and only if there are no xslt_param and xslt_stri

Syntax: working_directory directory; Default: — Context: main Defines the current working directory for a worker process. It is primarily used when writing a core-file, in which case a worker process should have write permission for the specified directory.

Syntax: xclient on | off; Default: xclient on; Context: mail, server Enables or disables the passing of the XCLIENT command with client parameters when connecting to the SMTP backend. With XCLIENT, the MTA is able to write client information to the log and apply various limitations based on this data. If XCLIENT is enabled then nginx passes the following commands when connecting to the backend: EHLO with the server name XCLIENT EHLO or HELO, as passed by the client