Mercurial > hg > nginx-site

comparison xml/en/docs/http/ngx_http_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 61aca81458a0
comparison
equal deleted inserted replaced
1699:6c96a644b0b3 1700:1dbef8ab47c7
8 <!DOCTYPE module SYSTEM "../../../../dtd/module.dtd"> 8 <!DOCTYPE module SYSTEM "../../../../dtd/module.dtd">
9 9
10 <module name="Module ngx_http_upstream_module" 10 <module name="Module ngx_http_upstream_module"
11 link="/en/docs/http/ngx_http_upstream_module.html" 11 link="/en/docs/http/ngx_http_upstream_module.html"
12 lang="en" 12 lang="en"
13 rev="47"> 13 rev="48">
14 14
15 <section id="summary"> 15 <section id="summary">
16 16
17 <para> 17 <para>
18 The <literal>ngx_http_upstream_module</literal> module 18 The <literal>ngx_http_upstream_module</literal> module
264 <tag-desc> 264 <tag-desc>
265 sets the server route name. 265 sets the server route name.
266 </tag-desc> 266 </tag-desc>
267 267
268 <tag-name id="service"> 268 <tag-name id="service">
269 <literal>service</literal>=<value>name</value> | <value>_name._protocol</value> 269 <literal>service</literal>=<value>name</value>
270 </tag-name> 270 </tag-name>
271 <tag-desc> 271 <tag-desc>
272 enables resolving of DNS 272 enables resolving of DNS
273 <link url="https://tools.ietf.org/html/rfc2782">SRV</link> 273 <link url="https://tools.ietf.org/html/rfc2782">SRV</link>
274 records and sets the service <value>name</value>, 274 records and sets the service <value>name</value> (1.9.13).
275 or <value>name</value> and <value>protocol</value> in the following format:
276 <value>_name._protocol</value> (1.9.13).
277 If only the <value>name</value> is specified,
278 the <literal>TCP</literal> protocol is used.
279 <para>
280 In order for this parameter to work, it is necessary to specify 275 In order for this parameter to work, it is necessary to specify
281 the <link id="resolve"/> parameter for the server 276 the <link id="resolve"/> parameter for the server
282 and specify a hostname without a port number: 277 and specify a hostname without a port number.
278 <para>
279 If the service name does not contain a dot (“<literal>.</literal>”), then
280 the <link url="https://tools.ietf.org/html/rfc2782">RFC</link>-compliant name
281 is constructed
282 and the TCP protocol is added to the service prefix.
283 For example, to look up the
284 <literal>_http._tcp.backend.example.com</literal> SRV record,
285 it is necessary to specify the directive:
283 <example> 286 <example>
284 server backend.example.com service=http resolve; 287 server backend.example.com service=http resolve;
288 </example>
289 If the service name contains one or more dots, then the name is constructed
290 by joining the service prefix and the server name.
291 For example, to look up the <literal>_http._tcp.backend.example.com</literal>
292 and <literal>server1.backend.example.com</literal> SRV records,
293 it is necessary to specify the directives:
294 <example>
285 server backend.example.com service=_http._tcp resolve; 295 server backend.example.com service=_http._tcp resolve;
286 </example> 296 server example.com service=server1.backend resolve;
287 Both directives specify the same SRV record: 297 </example>
288 <literal>_http._tcp.backend.example.com</literal>.
289 </para> 298 </para>
290 299
291 <para> 300 <para>
292 Highest-priority SRV records 301 Highest-priority SRV records
293 (records with the same lowest-number priority value) 302 (records with the same lowest-number priority value)