comparison xml/en/docs/http/ngx_http_upstream_module.xml @ 2831:4add6ae1296f

Updated links to datatracker.ietf.org.
author Sergey Kandaurov <pluknet@nginx.com>
date Wed, 26 Jan 2022 16:26:47 +0300
parents e642fe346261
children 3a2d342533fb
comparison
equal deleted inserted replaced
2830:419b081fd2fa 2831:4add6ae1296f
272 <tag-name id="service"> 272 <tag-name id="service">
273 <literal>service</literal>=<value>name</value> 273 <literal>service</literal>=<value>name</value>
274 </tag-name> 274 </tag-name>
275 <tag-desc> 275 <tag-desc>
276 enables resolving of DNS 276 enables resolving of DNS
277 <link url="https://tools.ietf.org/html/rfc2782">SRV</link> 277 <link url="https://datatracker.ietf.org/doc/html/rfc2782">SRV</link>
278 records and sets the service <value>name</value> (1.9.13). 278 records and sets the service <value>name</value> (1.9.13).
279 In order for this parameter to work, it is necessary to specify 279 In order for this parameter to work, it is necessary to specify
280 the <link id="resolve"/> parameter for the server 280 the <link id="resolve"/> parameter for the server
281 and specify a hostname without a port number. 281 and specify a hostname without a port number.
282 <para> 282 <para>
283 If the service name does not contain a dot (“<literal>.</literal>”), then 283 If the service name does not contain a dot (“<literal>.</literal>”), then
284 the <link url="https://tools.ietf.org/html/rfc2782">RFC</link>-compliant name 284 the <link url="https://datatracker.ietf.org/doc/html/rfc2782">RFC</link>-compliant name
285 is constructed 285 is constructed
286 and the TCP protocol is added to the service prefix. 286 and the TCP protocol is added to the service prefix.
287 For example, to look up the 287 For example, to look up the
288 <literal>_http._tcp.backend.example.com</literal> SRV record, 288 <literal>_http._tcp.backend.example.com</literal> SRV record,
289 it is necessary to specify the directive: 289 it is necessary to specify the directive: