Mercurial > hg > nginx-site
comparison xml/en/docs/http/server_names.xml @ 593:130fad6dc1b4
Replaced the uses of "url" element with "literal".
author | Ruslan Ermilov <ru@nginx.com> |
---|---|
date | Thu, 19 Jul 2012 05:17:45 +0000 |
parents | 764fbac1b8b4 |
children | 2300e4c1a231 |
comparison
equal
deleted
inserted
replaced
592:d40371689c1c | 593:130fad6dc1b4 |
---|---|
56 <listitem> | 56 <listitem> |
57 exact names; | 57 exact names; |
58 </listitem> | 58 </listitem> |
59 | 59 |
60 <listitem> | 60 <listitem> |
61 wildcard names starting with an asterisk: <url>*.example.org</url> | 61 wildcard names starting with an asterisk: <literal>*.example.org</literal> |
62 (longest first); | 62 (longest first); |
63 </listitem> | 63 </listitem> |
64 | 64 |
65 <listitem> | 65 <listitem> |
66 wildcard names ending with an asterisk: <url>mail.*</url> | 66 wildcard names ending with an asterisk: <literal>mail.*</literal> |
67 (longest first); | 67 (longest first); |
68 </listitem> | 68 </listitem> |
69 | 69 |
70 <listitem> | 70 <listitem> |
71 and regular expressions in the order listed in the configuration file. | 71 and regular expressions in the order listed in the configuration file. |
88 However, these names can be specified using regular expressions, | 88 However, these names can be specified using regular expressions, |
89 for example, “<literal>~^www\..+\.example\.org$</literal>” and | 89 for example, “<literal>~^www\..+\.example\.org$</literal>” and |
90 “<literal>~^w.*\.example\.org$</literal>”. | 90 “<literal>~^w.*\.example\.org$</literal>”. |
91 An asterisk can match several name parts. | 91 An asterisk can match several name parts. |
92 The name “<literal>*.example.org</literal>” matches not only | 92 The name “<literal>*.example.org</literal>” matches not only |
93 <url>www.example.org</url> but <url>www.sub.example.org</url> as well. | 93 <literal>www.example.org</literal> but <literal>www.sub.example.org</literal> as well. |
94 </para> | 94 </para> |
95 | 95 |
96 <para> | 96 <para> |
97 A special wildcard in the form “<literal>.example.org</literal>” can be used | 97 A special wildcard in the form “<literal>.example.org</literal>” can be used |
98 to match both the exact name “<literal>example.org</literal>” | 98 to match both the exact name “<literal>example.org</literal>” |
327 </para> | 327 </para> |
328 | 328 |
329 <para> | 329 <para> |
330 For these reasons, it is better to use exact names where possible. | 330 For these reasons, it is better to use exact names where possible. |
331 For example, if the most frequently requested names of a server | 331 For example, if the most frequently requested names of a server |
332 are <url>example.org</url> and <url>www.example.org</url>, | 332 are <literal>example.org</literal> and <literal>www.example.org</literal>, |
333 it is more efficient to define them explicitly: | 333 it is more efficient to define them explicitly: |
334 | 334 |
335 <programlisting> | 335 <programlisting> |
336 server { | 336 server { |
337 listen 80; | 337 listen 80; |
439 <listitem> | 439 <listitem> |
440 Regular expression server names have been supported since 0.6.7. | 440 Regular expression server names have been supported since 0.6.7. |
441 </listitem> | 441 </listitem> |
442 | 442 |
443 <listitem> | 443 <listitem> |
444 Wildcard form <url>example.*</url> has been supported since 0.6.0. | 444 Wildcard form <literal>example.*</literal> has been supported since 0.6.0. |
445 </listitem> | 445 </listitem> |
446 | 446 |
447 <listitem> | 447 <listitem> |
448 The special form <url>.example.org</url> has been supported since 0.3.18. | 448 The special form <literal>.example.org</literal> has been supported since 0.3.18. |
449 </listitem> | 449 </listitem> |
450 | 450 |
451 <listitem> | 451 <listitem> |
452 Wildcard form <url>*.example.org</url> has been supported since 0.1.13. | 452 Wildcard form <literal>*.example.org</literal> has been supported since 0.1.13. |
453 </listitem> | 453 </listitem> |
454 | 454 |
455 </list> | 455 </list> |
456 </para> | 456 </para> |
457 | 457 |