Mercurial > hg > nginx-site

comparison xml/en/docs/stream/ngx_stream_upstream_module.xml @ 1700:1dbef8ab47c7

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Updated description of service parameter in upstream.
author Yaroslav Zhuravlev <yar@nginx.com>
date Tue, 26 Apr 2016 19:31:57 +0300
parents 57c3f36b3b6a
children 1a16dce51bce
comparison
equal deleted inserted replaced
1699:6c96a644b0b3 1700:1dbef8ab47c7
7 <!DOCTYPE module SYSTEM "../../../../dtd/module.dtd"> 7 <!DOCTYPE module SYSTEM "../../../../dtd/module.dtd">
8 8
9 <module name="Module ngx_stream_upstream_module" 9 <module name="Module ngx_stream_upstream_module"
10 link="/en/docs/stream/ngx_stream_upstream_module.html" 10 link="/en/docs/stream/ngx_stream_upstream_module.html"
11 lang="en" 11 lang="en"
12 rev="11"> 12 rev="12">
13 13
14 <section id="summary"> 14 <section id="summary">
15 15
16 <para> 16 <para>
17 The <literal>ngx_stream_upstream_module</literal> module (1.9.0) 17 The <literal>ngx_stream_upstream_module</literal> module (1.9.0)
241 </example> 241 </example>
242 </para> 242 </para>
243 </tag-desc> 243 </tag-desc>
244 244
245 <tag-name id="service"> 245 <tag-name id="service">
246 <literal>service</literal>=<value>name</value> | <value>_name._protocol</value> 246 <literal>service</literal>=<value>name</value>
247 </tag-name> 247 </tag-name>
248 <tag-desc> 248 <tag-desc>
249 enables resolving of DNS 249 enables resolving of DNS
250 <link url="https://tools.ietf.org/html/rfc2782">SRV</link> 250 <link url="https://tools.ietf.org/html/rfc2782">SRV</link>
251 records and sets the service <value>name</value>, 251 records and sets the service <value>name</value> (1.9.13).
252 or <value>name</value> and <value>protocol</value> in the following format:
253 <value>_name._protocol</value> (1.9.13).
254 If only the <value>name</value> is specified,
255 the <literal>TCP</literal> protocol is used.
256 <para>
257 In order for this parameter to work, it is necessary to specify 252 In order for this parameter to work, it is necessary to specify
258 the <link id="resolve"/> parameter for the server 253 the <link id="resolve"/> parameter for the server
259 and specify a hostname without a port number: 254 and specify a hostname without a port number.
255 <para>
256 If the service name does not contain a dot (“<literal>.</literal>”), then
257 the <link url="https://tools.ietf.org/html/rfc2782">RFC</link>-compliant name
258 is constructed
259 and the TCP protocol is added to the service prefix.
260 For example, to look up the
261 <literal>_http._tcp.backend.example.com</literal> SRV record,
262 it is necessary to specify the directive:
260 <example> 263 <example>
261 server backend.example.com service=http resolve; 264 server backend.example.com service=http resolve;
265 </example>
266 If the service name contains one or more dots, then the name is constructed
267 by joining the service prefix and the server name.
268 For example, to look up the <literal>_http._tcp.backend.example.com</literal>
269 and <literal>server1.backend.example.com</literal> SRV records,
270 it is necessary to specify the directives:
271 <example>
262 server backend.example.com service=_http._tcp resolve; 272 server backend.example.com service=_http._tcp resolve;
273 server example.com service=server1.backend resolve;
263 </example> 274 </example>
264 Both directives specify the same SRV record:
265 <literal>_http._tcp.backend.example.com</literal>.
266 </para> 275 </para>
267 276
268 <para> 277 <para>
269 Highest-priority SRV records 278 Highest-priority SRV records
270 (records with the same lowest-number priority value) 279 (records with the same lowest-number priority value)