(later referred to simply as "Open Edition") for compiling.
So here are all the details on how to get Apache and how to get it where it needs to be:
<ol>
- <li><A HREF="http://www.apache.org/dist/">Download</A>
+ <li><A HREF="http://www.apache.org/dist/httpd/">Download</A>
the gzipped Apache files (the "tarball") to your PC.
The file name on the web site will be something like <i>apache_1.3.x.tar.gz</i>.
<br><font color=red size=4>TIP: </font>Be sure to keep the <i>.tar.gz</i> extension
group. Additional modules contributed by members or third parties with specific
needs or functions are available at
<A
-HREF="http://www.apache.org/dist/contrib/modules/">http://www.apache.org/dist/contrib/modules/</A>.
+HREF="http://www.apache.org/dist/httpd/contrib/modules/">http://www.apache.org/dist/httpd/contrib/modules/</A>.
There are instructions on that page for linking these modules into the core Apache
code.
<BR><BR>
tested and are used regularly by various members of the Apache
development group. Additional modules contributed by members or third
parties with specific needs or functions are available at
-<<A HREF="http://www.apache.org/dist/contrib/modules/"
- >http://www.apache.org/dist/contrib/modules/</A>>.
+<<A HREF="http://www.apache.org/dist/httpd/contrib/modules/"
+ >http://www.apache.org/dist/httpd/contrib/modules/</A>>.
There are instructions on that page for linking these modules into the
core Apache code.
tested and are used regularly by various members of the Apache
development group. Additional modules contributed by members or third
parties with specific needs or functions are available at
-<<A HREF="http://www.apache.org/dist/contrib/modules/"
- >http://www.apache.org/dist/contrib/modules/</A>>.
+<<A HREF="http://www.apache.org/dist/httpd/contrib/modules/"
+ >http://www.apache.org/dist/httpd/contrib/modules/</A>>.
There are instructions on that page for linking these modules into the
core Apache code.
<!--#include virtual="header.html" -->
<H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
<P>
- $Revision: 1.6 $ ($Date: 2001/02/28 03:35:59 $)
+ $Revision: 1.7 $ ($Date: 2001/03/28 21:26:29 $)
</P>
<P>
The latest version of this FAQ is always available from the main
<p>
If you don't see a kit for your platform listed in the
binary distribution area
- (<URL:<a href="http://httpd.apache.org/dist/binaries/"
- >http://httpd.apache.org/dist/binaries/</a>>),
+ (<URL:<a href="http://httpd.apache.org/dist/httpd/binaries/"
+ >http://httpd.apache.org/dist/httpd/binaries/</a>>),
it means either that the platform isn't available to any of
the developers, or that they just haven't gotten around to
preparing a binary for it. As this is a voluntary project,
</UL>
<P>
There is a
-<A HREF="http://www.apache.org/dist/contrib/patches/1.2/fin_wait_2.patch"
+<A HREF="http://www.apache.org/dist/httpd/contrib/patches/1.2/fin_wait_2.patch"
>patch available</A> for adding a timeout to the FIN_WAIT_2 state; it
was originally intended for BSD/OS, but should be adaptable to most
systems using BSD networking code. You need kernel source code to be
responses. Unfortunately Apache's <CODE>nokeepalive</CODE> code
prior to 1.2.2 would not work with HTTP/1.1 clients. You must apply
<A
-HREF="http://www.apache.org/dist/patches/apply_to_1.2.1/msie_4_0b2_fixes.patch"
+HREF="http://www.apache.org/dist/httpd/patches/apply_to_1.2.1/msie_4_0b2_fixes.patch"
>this patch</A> to version 1.2.1. Then add this to your config:
<BLOCKQUOTE><CODE>
BrowserMatch "MSIE 4\.0b2;" nokeepalive
</CODE></BLOCKQUOTE>
This workaround is available in 1.2.2, and in a
<A
-HREF="http://www.apache.org/dist/patches/apply_to_1.2.1/msie_4_0b2_fixes.patch"
+HREF="http://www.apache.org/dist/httpd/patches/apply_to_1.2.1/msie_4_0b2_fixes.patch"
>patch</A> against 1.2.1.
<H3><A NAME="257th-byte">Boundary problems with header parsing</A></H3>