comparison xml/en/docs/stream/ngx_stream_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 504536999408
children 3a2d342533fb
comparison
equal deleted inserted replaced
2830:419b081fd2fa 2831:4add6ae1296f
245 <tag-name id="service"> 245 <tag-name id="service">
246 <literal>service</literal>=<value>name</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://datatracker.ietf.org/doc/html/rfc2782">SRV</link>
251 records and sets the service <value>name</value> (1.9.13). 251 records and sets the service <value>name</value> (1.9.13).
252 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
253 the <link id="resolve"/> parameter for the server 253 the <link id="resolve"/> parameter for the server
254 and specify a hostname without a port number. 254 and specify a hostname without a port number.
255 <para> 255 <para>
256 If the service name does not contain a dot (“<literal>.</literal>”), then 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 257 the <link url="https://datatracker.ietf.org/doc/html/rfc2782">RFC</link>-compliant name
258 is constructed 258 is constructed
259 and the TCP protocol is added to the service prefix. 259 and the TCP protocol is added to the service prefix.
260 For example, to look up the 260 For example, to look up the
261 <literal>_http._tcp.backend.example.com</literal> SRV record, 261 <literal>_http._tcp.backend.example.com</literal> SRV record,
262 it is necessary to specify the directive: 262 it is necessary to specify the directive: