<strong>Compatibility:</strong> Available in Apache 1.3 and later
</P>
-<p>This directive is equiv
ilent to <a href="#alias">Alias</a>, but
+<p>This directive is equiv
alent to <a href="#alias">Alias</a>, but
makes use of standard regular expressions, instead of simple prefix
matching. The supplied regular expression is matched against the URL,
and if it matches, the server will substitute any parenthesized
<strong>Compatibility:</strong> Available in Apache 1.3 and later
</P>
-<p>This directive is equiv
ilent to <a href="#alias">Redirect</a>, but
+<p>This directive is equiv
alent to <a href="#alias">Redirect</a>, but
makes use of standard regular expressions, instead of simple prefix
matching. The supplied regular expression is matched against the URL,
and if it matches, the server will substitute any parenthesized
<strong>Compatibility:</strong> Available in Apache 1.3 and later
</P>
-<p>This directive is equiv
ilent to <a href="#scriptalias">ScriptAlias</a>, but
+<p>This directive is equiv
alent to <a href="#scriptalias">ScriptAlias</a>, but
makes use of standard regular expressions, instead of simple prefix
matching. The supplied regular expression is matched against the URL,
and if it matches, the server will substitute any parenthesized
</P>
<P>
The main file is <CODE>mod_example.c</CODE>, which illustrates all
- the different callback mechanisms and call syntaces. By no means does
+ the different callback mechanisms and call syntaxes. By no means does
an add-on module need to include routines for all of the callbacks -
quite the contrary!
</P>
<h2>Referencing your mapfile</h2>
<blockquote><code>
-<A HREF="/maps/imagmap1.map"> <br>
+<A HREF="/maps/imagemap1.map"> <br>
<IMG ISMAP SRC="/images/imagemap1.gif"> <br>
</A>
</code></blockquote><p>
<p>Apache's ISAPI implementation conforms to all of the ISAPI 2.0
specification, except for the "Microsoft-specific" extensions dealing
- with ascynchronous I/O. Apache's I/O model does not allow asynchronous
+ with asynchronous I/O. Apache's I/O model does not allow asynchronous
reading and writing in a manner that the ISAPI could access. If an ISA
tries to access async I/O, a message will be place in the error log,
to help with debugging.
<P>
This module is contained in the <code>mod_speling.c</code> file,
and is <strong>not</strong> compiled in by default.
- It attemps to correct misspellings of
+ It attempts to correct misspellings of
URLs that users might have entered, by ignoring capitalization
and by allowing up to one misspelling.<br>
This catches the majority of misspelled requests. An automatic
correction will have an impact on the server's performance
when many spelling corrections have to be performed at the same time.
<LI>the document trees should not contain sensitive files which could
- be matched inadvertedly, by a spelling "correction".
+ be matched inadvertently, by a spelling "correction".
<LI>the module is unable to correct misspelled user names
(as in <code>http://my.host/~apahce/</code>), just file names or
directory names.
If folks are running Apache on a PA-8000 based system, they should
consider "chatr'ing" the Apache executable to have a large page size.
This would be "chatr +pi L <binary>." The GID of the running executable
-must have MLOCK priviledges. Setprivgrp(1m) should be consulted for
+must have MLOCK privileges. Setprivgrp(1m) should be consulted for
assigning MLOCK. The change can be validated by running Glance and
examining the memory regions of the server(s) to make sure that they
show a non-trivial fraction of the text segment being locked.
</ul>
Note also that modifying .htaccess parsing during Location doesn't do
-anything because .htaccess parsing has already occured.
+anything because .htaccess parsing has already occurred.
<p>
</ul>
Note also that modifying .htaccess parsing during Location doesn't do
-anything because .htaccess parsing has already occured.
+anything because .htaccess parsing has already occurred.
<p>
<li>A <code>_default_</code> vhost catches a request only if there is no
other vhost with a matching IP address <em>and</em> a matching port
- number for the request. The request is only catched if the port number
+ number for the request. The request is only caught if the port number
to which the client sent the request matches the port number of your
<code>_default_</code> vhost which is your standard <code>Port</code>
by default. A wildcard port can be specified (i.e.
...
</VirtualHost>
</pre>
- The main server can never catch a request, because all IP address
+ The main server can never catch a request, because all IP addresses
of our machine are in use for IP-based virtual hosts
(only <samp>localhost</samp> requests can hit the main server).
</blockquote>
</Directory>
</VirtualHost>
</pre>
- The main server can never catch a request, because all IP addresss
+ The main server can never catch a request, because all IP addresses
(apart from <samp>localhost</samp>) of our machine are in use for IP-based
virtual hosts. The web server can only be reached on the first address
through port 80 and the proxy only on the second address through port 8080.
projects / thirdparty / apache / httpd.git / commitdiff
