Mercurial > hg > nginx-site
comparison xml/en/docs/http/ngx_http_upstream_module.xml @ 1680:57c3f36b3b6a
Updated docs for the upcoming NGINX Plus release.
author | Ruslan Ermilov <ru@nginx.com> |
---|---|
date | Sun, 10 Apr 2016 00:12:49 +0300 |
parents | 44c4323144c5 |
children | 1dbef8ab47c7 |
comparison
equal
deleted
inserted
replaced
1679:e9ad1cae4401 | 1680:57c3f36b3b6a |
---|---|
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="46"> | 13 rev="47"> |
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 |
60 | 60 |
61 server backend1.example.com weight=5; | 61 server backend1.example.com weight=5; |
62 server backend2.example.com:8080 fail_timeout=5s slow_start=30s; | 62 server backend2.example.com:8080 fail_timeout=5s slow_start=30s; |
63 server 192.0.2.1 max_fails=3; | 63 server 192.0.2.1 max_fails=3; |
64 server backend3.example.com resolve; | 64 server backend3.example.com resolve; |
65 server backend4.example.com service=http resolve; | |
65 | 66 |
66 server backup1.example.com:8080 backup; | 67 server backup1.example.com:8080 backup; |
67 server backup2.example.com:8080 backup; | 68 server backup2.example.com:8080 backup; |
68 } | 69 } |
69 | 70 |
260 <tag-name id="route"> | 261 <tag-name id="route"> |
261 <literal>route</literal>=<value>string</value> | 262 <literal>route</literal>=<value>string</value> |
262 </tag-name> | 263 </tag-name> |
263 <tag-desc> | 264 <tag-desc> |
264 sets the server route name. | 265 sets the server route name. |
266 </tag-desc> | |
267 | |
268 <tag-name id="service"> | |
269 <literal>service</literal>=<value>name</value> | <value>_name._protocol</value> | |
270 </tag-name> | |
271 <tag-desc> | |
272 enables resolving of DNS | |
273 <link url="https://tools.ietf.org/html/rfc2782">SRV</link> | |
274 records and sets the service <value>name</value>, | |
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 | |
281 the <link id="resolve"/> parameter for the server | |
282 and specify a hostname without a port number: | |
283 <example> | |
284 server backend.example.com service=http resolve; | |
285 server backend.example.com service=_http._tcp resolve; | |
286 </example> | |
287 Both directives specify the same SRV record: | |
288 <literal>_http._tcp.backend.example.com</literal>. | |
289 </para> | |
290 | |
291 <para> | |
292 Highest-priority SRV records | |
293 (records with the same lowest-number priority value) | |
294 are resolved as primary servers, | |
295 the rest of SRV records are resolved as backup servers. | |
296 If the <link id="backup"/> parameter is specified for the server, | |
297 high-priority SRV records are resolved as backup servers, | |
298 the rest of SRV records are ignored. | |
299 </para> | |
265 </tag-desc> | 300 </tag-desc> |
266 | 301 |
267 <tag-name id="slow_start"> | 302 <tag-name id="slow_start"> |
268 <literal>slow_start</literal>=<value>time</value> | 303 <literal>slow_start</literal>=<value>time</value> |
269 </tag-name> | 304 </tag-name> |