The LoadFile directive links in the named object files or libraries
when the server is started or restarted; this is used to load
additional code which may be required for some module to
-work. <EM>Filename</EM> is either and absolute path or relative to <A
+work. <EM>Filename</EM> is either an absolute path or relative to <A
HREF="core.html#serverroot">ServerRoot</A>.<P><HR>
<H2><A NAME="loadmodule">LoadModule</A> directive</H2>
repeated itself). This is not a perfect defense.
<P>
-How good a defense is it? Well suppose that one of your machines serves
+How good a defense is it? We'll suppose that one of your machines serves
at most 500 requests per second (which is a very reasonable upper bound
at this writing, because systems generally do more than just shovel out
static files). To do that it will require a number of children which
<P>
The <CODE>UNIQUE_ID</CODE> environment variable is constructed by
encoding the 112-bit (32-bit IP address, 32 bit pid, 32 bit time stamp,
-16 bit counter) quadruple using the alphabet <CODE>[A-Za-z0-9@-]</CODE>
+16 bit counter quadruple) using the alphabet <CODE>[A-Za-z0-9@-]</CODE>
in a manner similar to MIME base64 encoding, producing 19 characters.
The MIME base64 alphabet is actually <CODE>[A-Za-z0-9+/]</CODE> however
<CODE>+</CODE> and <CODE>/</CODE> need to be specially encoded in URLs,