# HG changeset patch # User Vladimir Homutov # Date 1344846139 0 # Node ID 779a47d0acb073d6b8f823f768f84888f11f107f # Parent af23cb587b000b86c504f4104bc6f009891bfb21 Unified terminology used in the "server_name" directive and server_names.xml. diff -r af23cb587b00 -r 779a47d0acb0 xml/en/docs/http/ngx_http_core_module.xml --- a/xml/en/docs/http/ngx_http_core_module.xml Mon Aug 13 08:19:06 2012 +0000 +++ b/xml/en/docs/http/ngx_http_core_module.xml Mon Aug 13 08:22:19 2012 +0000 @@ -10,7 +10,7 @@ + rev="2">
@@ -2115,6 +2115,9 @@ The first name becomes the primary server name. + + + Server names can include an asterisk (“*”) to replace the first or last part of a name: @@ -2122,6 +2125,7 @@ server_name example.com *.example.com www.example.*; } +Such names are called wildcard names. @@ -2134,11 +2138,6 @@ -If the parameter equals “$hostname” (0.9.4), the -machine’s hostname is substituted. - - - It is also possible to use regular expressions in server names, prepending the name with a tilde (“~”): @@ -2193,6 +2192,11 @@ +If the parameter equals “$hostname” (0.9.4), the +machine’s hostname is substituted. + + + It is also possible to specify an empty server name (0.7.11): server { @@ -2210,21 +2214,21 @@ When searching for a virtual server by name, if name matches more than one of the specified variants, -e.g. both mask and regular expression match, the first matching +e.g. both wildcard name and regular expression match, the first matching variant will be chosen, in the following order of precedence: -full name +exact name -longest name with a prefix mask, +longest wildcard name starting with an asterisk, e.g. “*.example.com -longest name with a suffix mask, +longest wildcard name ending with an asterisk, e.g. “mail.* @@ -2236,6 +2240,11 @@ + +For more information, please refer to the + document. + +