mechanisms to modify the way Apache behaves when talking to particular
clients. To make these mechanisms as flexible as possible, they
are invoked by defining environment variables, typically with
-<A HREF="mod/mod_browser.html#browsermatch">BrowserMatch</A>, though
+<A HREF="mod/mod_setenvif.html#browsermatch">BrowserMatch</A>, though
<A HREF="mod/mod_env.html#setenv">SetEnv</A> and
<A HREF="mod/mod_env.html#passenv">PassEnv</A> could also be used, for
example.
mechanisms to modify the way Apache behaves when talking to particular
clients. To make these mechanisms as flexible as possible, they
are invoked by defining environment variables, typically with
-<A HREF="mod/mod_browser.html#browsermatch">BrowserMatch</A>, though
+<A HREF="mod/mod_setenvif.html#browsermatch">BrowserMatch</A>, though
<A HREF="mod/mod_env.html#setenv">SetEnv</A> and
<A HREF="mod/mod_env.html#passenv">PassEnv</A> could also be used, for
example.
This document covers compilation and installation of Apache on Unix
systems only. For compiling and installation on Windows, see <A
-HREF="windows.html">Using Apache with Microsoft Windows</A> and for
-TPF see <A HREF="install-tpf.html">Installing the Apache 1.3 HTTP
+HREF="platform/windows.html">Using Apache with Microsoft Windows</A> and for
+TPF see <A HREF="platform/install-tpf.html">Installing the Apache 1.3 HTTP
Server on TPF</A>.
<P>
-UnixWare users will want to consult <A HREF="unixware.html">build notes</A>
+UnixWare users will want to consult <A HREF="platform/unixware.html">build notes</A>
for various UnixWare versions before compiling.
<H2>Downloading Apache</H2>
This document covers compilation and installation of Apache on Unix
systems only. For compiling and installation on Windows, see <A
-HREF="windows.html">Using Apache with Microsoft Windows</A> and for
-TPF see <A HREF="install-tpf.html">Installing the Apache 1.3 HTTP
+HREF="platform/windows.html">Using Apache with Microsoft Windows</A> and for
+TPF see <A HREF="platform/install-tpf.html">Installing the Apache 1.3 HTTP
Server on TPF</A>.
<P>
-UnixWare users will want to consult <A HREF="unixware.html">build notes</A>
+UnixWare users will want to consult <A HREF="platform/unixware.html">build notes</A>
for various UnixWare versions before compiling.
<H2>Downloading Apache</H2>
On Windows, Apache is normally run as a service on Windows NT, or as a
console application on Windows 95. See also <A
-HREF="windows.html#run">running Apache for Windows</A>.
+HREF="platform/windows.html#run">running Apache for Windows</A>.
<H2>Command line options</H2>
The following options are recognized on the httpd command line:
On Windows, Apache is normally run as a service on Windows NT, or as a
console application on Windows 95. See also <A
-HREF="windows.html#run">running Apache for Windows</A>.
+HREF="platform/windows.html#run">running Apache for Windows</A>.
<H2>Command line options</H2>
The following options are recognized on the httpd command line:
>Getting, Installing, and Running Apache (on Unix)</A> (O'Reilly
Network Apache DevCenter)
-<LI><A HREF="../windows.html">Using Apache With Microsoft Windows</A>
-
-<LI><A HREF="../netware.html">Using Apache With Novell Netware 5</A>
-
<LI><A HREF="http://www.builder.com/Servers/Apache/ss01.html">Maximum
Apache: Getting Started</A> (CNET Builder.com)
So the "process"-management directives are different:
<P><A
- HREF="mod/core.html#maxrequestsperchild">MaxRequestsPerChild</A>
+ HREF="../mod/mpm_common.html#maxrequestsperchild">MaxRequestsPerChild</A>
- Like the Unix directive, this controls how many requests a
process will serve before exiting. However, unlike Unix, a
process serves all the requests at once, not just one, so if
this is set, it is recommended that a very high number is
used. The recommended default, <CODE>MaxRequestsPerChild
0</CODE>, does not cause the process to ever exit.
- <P><A HREF="mod/core.html#threadsperchild">ThreadsPerChild</A> -
+ <P><A HREF="../mod/mpm_common.html#threadsperchild">ThreadsPerChild</A> -
This directive is new, and tells the server how many threads it
should use. This is the maximum number of connections the server
can handle at once; be sure and set this number high enough for
your site if you get a lot of hits. The recommended default is
<CODE>ThreadsPerChild 50</CODE>.
- </P><A HREF="mod/core.html#threadstacksize">ThreadStackSize</A> -
+ </P><A HREF="../mod/core.html#threadstacksize">ThreadStackSize</A> -
This directive tells the server what size of stack to use for
the individual threads. The recommended default is
<CODE>ThreadStackSize 65536</CODE>.
So the "process"-management directives are different:
<P><A
- HREF="mod/core.html#maxrequestsperchild">MaxRequestsPerChild</A>
+ HREF="../mod/mpm_common.html#maxrequestsperchild">MaxRequestsPerChild</A>
- Like the Unix directive, this controls how many requests a
process will serve before exiting. However, unlike Unix, a
process serves all the requests at once, not just one, so if
new child process is started. If you have modified httpd.conf,
the new child may not start or you may receive unexpected results.
</STRONG>
- <P><A HREF="mod/core.html#threadsperchild">ThreadsPerChild</A> -
+ <P><A HREF="../mod/mpm_common.html#threadsperchild">ThreadsPerChild</A> -
This directive is new, and tells the server how many threads it
should use. This is the maximum number of connections the server
can handle at once; be sure and set this number high enough for
without recompiling the server. If Apache is compiled normally, it
will install a number of optional modules in the
<CODE>\Apache\modules</CODE> directory. To activate these, or other
- modules, the new <A HREF="mod/mod_so.html#loadmodule">LoadModule</A>
+ modules, the new <A HREF="../mod/mod_so.html#loadmodule">LoadModule</A>
directive must be used. For example, to active the status module,
use the following (in addition to the status-activating directives
in <CODE>access.conf</CODE>):</P>
<PRE>
LoadModule status_module modules/ApacheModuleStatus.dll
</PRE>
- <P>Information on <A HREF="mod/mod_so.html#creating">creating loadable
+ <P>Information on <A HREF="../mod/mod_so.html#creating">creating loadable
modules</A> is also available.</P>
<LI><P>Apache can also load ISAPI Extensions (<EM>i.e.</EM>, Internet Server
Applications), such as those used by Microsoft's IIS, and other
- Windows servers. <A HREF="mod/mod_isapi.html">More information
+ Windows servers. <A HREF="../mod/mod_isapi.html">More information
is available.</A> Note that Apache <EMP>CANNOT</EMP> load ISAPI
Filters.
</UL>
<H1 ALIGN="CENTER">Stopping and Restarting Apache</H1>
<P>This document covers stopping and restarting Apache on Unix
-only. Windows users should see <A HREF="windows.html#signal">Signalling
+only. Windows users should see <A HREF="platform/windows.html#signal">Signalling
Apache when running</A>.</P>
<P>You will notice many <CODE>httpd</CODE> executables running on your system,
<H1 ALIGN="CENTER">Stopping and Restarting Apache</H1>
<P>This document covers stopping and restarting Apache on Unix
-only. Windows users should see <A HREF="windows.html#signal">Signalling
+only. Windows users should see <A HREF="platform/windows.html#signal">Signalling
Apache when running</A>.</P>
<P>You will notice many <CODE>httpd</CODE> executables running on your system,
Here's where we begin the fun. If you use Apache 1.2 or prefer to configure
Apache 1.3 with the "<CODE>src/Configure</CODE>" script you have to edit
the suEXEC header file and install the binary in its proper location
-manually. This procedure is described in an
-<A HREF="suexec_1_2.html">extra document</A>.
-The following sections describe the configuration and installation
+manually. The following sections describe the configuration and installation
for Apache 1.3 with the AutoConf-style interface (APACI).
</P>
Here's where we begin the fun. If you use Apache 1.2 or prefer to configure
Apache 1.3 with the "<CODE>src/Configure</CODE>" script you have to edit
the suEXEC header file and install the binary in its proper location
-manually. This procedure is described in an
-<A HREF="suexec_1_2.html">extra document</A>.
-The following sections describe the configuration and installation
+manually. The following sections describe the configuration and installation
for Apache 1.3 with the AutoConf-style interface (APACI).
</P>
projects / apache / commitdiff