"http://www.apache.org".
The second option is to set up a <CODE>ScriptAlias</CODE> pointing to
-a <STRONG>cgi script</STRONG> which outputs a 301 or 302 status and the
+a <STRONG>CGI script</STRONG> which outputs a 301 or 302 status and the
location
of the other server.</P>
-<P>By using a <STRONG>cgi-script</STRONG> you can intercept various requests
+<P>By using a <STRONG>CGI script</STRONG> you can intercept various requests
and
-treat them specially, <EM>e.g.</EM>, you might want to intercept <STRONG>POST</STRONG>
+treat them specially, <EM>e.g.</EM>, you might want to intercept
+<STRONG>POST</STRONG>
requests, so that the client isn't redirected to a script on the other
server which expects POST information (a redirect will lose the POST
information.) You might also want to use a CGI script if you don't
<P>The correct procedure is to move the logfile, then signal Apache to tell
it to reopen the logfiles.</P>
-<P>Apache is signaled using the <STRONG>SIGHUP</STRONG> (-1) signal. <EM>e.g.</EM>
+<P>Apache is signaled using the <STRONG>SIGHUP</STRONG> (-1) signal.
+<EM>e.g.</EM>
<BLOCKQUOTE><CODE>
mv access_log access_log.old<BR>
kill -1 `cat httpd.pid`
<P ALIGN="LEFT">
If your installation requires location of the wrapper program in a different
-directory, either add <CODE>-DSUEXEC_BIN=\"<EM></your/path/to/suexec></EM>\"</CODE>
+directory, either add
+<CODE>-DSUEXEC_BIN=\"<EM></your/path/to/suexec></EM>\"</CODE>
to your CFLAGS (or edit src/include/httpd.h) and recompile your Apache server.
See <A HREF="install.html">Compiling and Installing Apache</A>
(and the <SAMP>INSTALL</SAMP> file in the source distribution)
<P ALIGN="LEFT">
If your installation requires location of the wrapper program in a different
-directory, either add <CODE>-DSUEXEC_BIN=\"<EM></your/path/to/suexec></EM>\"</CODE>
+directory, either add
+<CODE>-DSUEXEC_BIN=\"<EM></your/path/to/suexec></EM>\"</CODE>
to your CFLAGS (or edit src/include/httpd.h) and recompile your Apache server.
See <A HREF="install.html">Compiling and Installing Apache</A>
(and the <SAMP>INSTALL</SAMP> file in the source distribution)
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 (<EM>i.e.</EM>
+ by default. A wildcard port can be specified (<EM>i.e.</EM>,
<CODE>_default_:*</CODE>) to catch requests to any available port.
<P>
<LI>A <CODE>_default_</CODE> vhost or the main_server is <EM>never</EM>
matched for a request with an unknown or missing <CODE>Host:</CODE> header
field if the client connected to an address (and port) which is used
- for name-based vhosts, <EM>e.g.</EM>, in a <CODE>NameVirtualHost</CODE> directive.
+ for name-based vhosts, <EM>e.g.</EM>, in a <CODE>NameVirtualHost</CODE>
+ directive.
<P>
<LI>You should never specify DNS names in <CODE>VirtualHost</CODE>
private.foo.com</CODE> header. It is important to note that this
condition exists only if you only implement this policy at the IP
layer - all security controls used by Apache (<EM>i.e.</EM>, <A
-HREF="../mod/mod_access.html">allow, deny from,</A> <EM>etc.</EM>) are consistently
-respected.
+HREF="../mod/mod_access.html">allow, deny from,</A> <EM>etc.</EM>) are
+consistently respected.
<H2>Compatibility with Older Browsers</H2>
Use multiple daemons when:
<UL>
<LI>The different virtual hosts need very different httpd configurations, such
- as different values for: <A HREF="../mod/core.html#servertype">ServerType</A>,
+ as different values for:
+ <A HREF="../mod/core.html#servertype">ServerType</A>,
<A HREF="../mod/core.html#user">User</A>,
<A HREF="../mod/core.html#group">Group</A>,
<A HREF="../mod/mod_mime.html#typesconfig">TypesConfig</A> or
The latter will probably manifest itself in a later version of Apache.
<!--#include virtual="footer.html" -->
-</BODY></HTML>
-
+</BODY>
+</HTML>