<section id="rebackref">
<title>Regular expression backreferences</title>
<p>The strings <code>$0</code> ... <code>$9</code> allow to reference
- the capture groups form a previously executed, successfully
+ the capture groups from a previously executed, successfully
matching regular expressions. They can normally only be used in the
same expression as the matching regex, but some modules allow special
uses.</p>
</example>
<p>Specifying <code>connection</code> or <code>request</code> as first
- paramter allows to specify additional formats, causing additional
+ parameter allows to specify additional formats, causing additional
information to be logged when the first message is logged for a specific
connection or request, respectivly. This additional information is only
logged once per connection/request. If a connection or request is processed
<p>When a request is received, the server first maps it to the best matching
<directive type="section">VirtualHost</directive> based on the local
IP address and port combination only. Non-wildcards have a higher
- precedence. if no match based on IP and port occurs at all, the
+ precedence. If no match based on IP and port occurs at all, the
"main" server configuration is used.</p>
<p>If multiple virtual hosts contain the best matching IP address and port,
the server selects from these virtual hosts the best match based on the
requested hostname. If no matching name-based virtual host is found,
then the first listed virtual host that matched the IP address will be
- used. As a consequence, the first listed virtual for a given IP address
+ used. As a consequence, the first listed virtual host for a given IP address
and port combination is default virtual host for that IP and port
combination.</p>
will have to read on for further complications.</p>
<p> The default value of <code>onsuccess</code> may need to be changed to
- <code>always</code> under the circumstances similar to those listed below
+ <code>always</code> under the circumstances similar to those listed below.
Note also that repeating this directive with both conditions makes sense in
some scenarios because <code>always</code> is not a superset of
<code>onsuccess</code> with respect to existing headers:</p>
</Location>
</example>
- <p>Backreferences can be used in the comparison and in the substituion,
+ <p>Backreferences can be used in the comparison and in the substitution,
when regular expressions are used, as illustrated in the following example: </p>
<example><title>Example of using backreferences and captures</title>
<Location />
of adjustment should only be made in a test environment which allows
the full set of web server processing can be exercised, as there
may be infrequent requests which require more stack to process.
- The minumum required stack size strongly depends on the modules
+ The minimum required stack size strongly depends on the modules
used, but any change in the web server configuration can invalidate
the current <directive>ThreadStackSize</directive> setting.</li>
</ul>
<section id="ipbased"><title>IP-based vhost</title>
<p>If there is exactly one <code>VirtualHost</code> directive
- listing the IP address and port combibation that was determined
+ listing the IP address and port combination that was determined
to be the best match, no further actions are performed and
the request is served from the matching vhost.</p>
<section id="namebased"><title>Name-based vhost</title>
- <p>If there are multiple <code>VirtalHost</code> directives listing
+ <p>If there are multiple <code>VirtualHost</code> directives listing
the IP address and port combination that was determined to be the
best match, the "list" in the remaining steps refers to the list of vhosts
that matched, in the order they were in the configuration file.</p>
</ul>
<p> Name-based virtual hosting builds off of the IP-based virtual host
- selection algoirthm, meaning that searches for the proper server name
+ selection algorithm, meaning that searches for the proper server name
occur only between virtual hosts that have the best IP-based address.</p>
<p>When a request arrives, the server will find the best (most specific) matching
<directive type="section" module="core">VirtualHost</directive> argument based on
the IP address and port used by the request. If there is more than one virtual host
- contanin this best-match address and port combination, Apache will further
+ containing this best-match address and port combination, Apache will further
compare the <directive module="core" >ServerName</directive> and <directive
module="core">ServerAlias</directive> directives to the server name
present in the request.</p>
<p> If no matching ServerName or ServerAlias is found in the set of
virtual hosts containing the most specific matching IP address and port
combination, then <strong>the first listed virtual host</strong> that
- matches the will be used.</p></section>
+ matches that will be used.</p></section>
</section>
<section id="using"><title>Using Name-based Virtual Hosts</title>
projects / apache / commitdiff