VladPolskiy/apache-http-server
1
0
Fork 0
mirror of https://github.com/apache/httpd.git synced 2025-08-15 23:27:39 +00:00
Code Issues Packages Projects Releases Wiki Activity

Change the links to point to the new distribution directory.

Browse Source 
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@88609 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Ken Coar
2001-03-28 21:26:29 +00:00
parent 0da977423c
commit 382c21439a
6 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/manual/install-tpf.html
View File

@ -41,7 +41,7 @@ Additionally the source code from the tarball will need to be copied onto an MVS
(later referred to simply as "Open Edition") for compiling. (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: So here are all the details on how to get Apache and how to get it where it needs to be:
<ol> <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 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>. 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 <br><font color=red size=4>TIP: </font>Be sure to keep the <i>.tar.gz</i> extension
@ -139,7 +139,7 @@ are case sensitive, and must be made from the "src" directory.
group. Additional modules contributed by members or third parties with specific group. Additional modules contributed by members or third parties with specific
needs or functions are available at needs or functions are available at
<A <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 There are instructions on that page for linking these modules into the core Apache
code. code.
<BR><BR> <BR><BR>

4
docs/manual/install.html
View File

@ -126,8 +126,8 @@ The modules we place in the Apache distribution are the ones we have
tested and are used regularly by various members of the Apache tested and are used regularly by various members of the Apache
development group. Additional modules contributed by members or third development group. Additional modules contributed by members or third
parties with specific needs or functions are available at parties with specific needs or functions are available at
&lt;<A HREF="http://www.apache.org/dist/contrib/modules/" &lt;<A HREF="http://www.apache.org/dist/httpd/contrib/modules/"
>http://www.apache.org/dist/contrib/modules/</A>&gt;. >http://www.apache.org/dist/httpd/contrib/modules/</A>&gt;.
There are instructions on that page for linking these modules into the There are instructions on that page for linking these modules into the
core Apache code. core Apache code.

4
docs/manual/install.html.en
View File

@ -126,8 +126,8 @@ The modules we place in the Apache distribution are the ones we have
tested and are used regularly by various members of the Apache tested and are used regularly by various members of the Apache
development group. Additional modules contributed by members or third development group. Additional modules contributed by members or third
parties with specific needs or functions are available at parties with specific needs or functions are available at
&lt;<A HREF="http://www.apache.org/dist/contrib/modules/" &lt;<A HREF="http://www.apache.org/dist/httpd/contrib/modules/"
>http://www.apache.org/dist/contrib/modules/</A>&gt;. >http://www.apache.org/dist/httpd/contrib/modules/</A>&gt;.
There are instructions on that page for linking these modules into the There are instructions on that page for linking these modules into the
core Apache code. core Apache code.

6
docs/manual/misc/FAQ-B.html
View File

@ -31,7 +31,7 @@
<!--#include virtual="header.html" --> <!--#include virtual="header.html" -->
<H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1> <H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
<P> <P>
$Revision: 1.6 $ ($Date: 2001/02/28 03:35:59 $) $Revision: 1.7 $ ($Date: 2001/03/28 21:26:29 $)
</P> </P>
<P> <P>
The latest version of this FAQ is always available from the main The latest version of this FAQ is always available from the main
@ -408,8 +408,8 @@
<p> <p>
If you don't see a kit for your platform listed in the If you don't see a kit for your platform listed in the
binary distribution area binary distribution area
(&lt;URL:<a href="http://httpd.apache.org/dist/binaries/" (&lt;URL:<a href="http://httpd.apache.org/dist/httpd/binaries/"
>http://httpd.apache.org/dist/binaries/</a>&gt;), >http://httpd.apache.org/dist/httpd/binaries/</a>&gt;),
it means either that the platform isn't available to any of it means either that the platform isn't available to any of
the developers, or that they just haven't gotten around to the developers, or that they just haven't gotten around to
preparing a binary for it. As this is a voluntary project, preparing a binary for it. As this is a voluntary project,

2
docs/manual/misc/fin_wait_2.html
View File

@ -205,7 +205,7 @@ The following systems are known to not have a timeout:
</UL> </UL>
<P> <P>
There is a 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 >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 was originally intended for BSD/OS, but should be adaptable to most
systems using BSD networking code. You need kernel source code to be systems using BSD networking code. You need kernel source code to be

4
docs/manual/misc/known_client_problems.html
View File

@ -68,7 +68,7 @@ support keepalive when it is used on 301 or 302 (redirect)
responses. Unfortunately Apache's <CODE>nokeepalive</CODE> code responses. Unfortunately Apache's <CODE>nokeepalive</CODE> code
prior to 1.2.2 would not work with HTTP/1.1 clients. You must apply prior to 1.2.2 would not work with HTTP/1.1 clients. You must apply
<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"
>this patch</A> to version 1.2.1. Then add this to your config: >this patch</A> to version 1.2.1. Then add this to your config:
<BLOCKQUOTE><CODE> <BLOCKQUOTE><CODE>
BrowserMatch "MSIE 4\.0b2;" nokeepalive BrowserMatch "MSIE 4\.0b2;" nokeepalive
@ -127,7 +127,7 @@ BrowserMatch "MSIE 4\.0b2;" downgrade-1.0 force-response-1.0
</CODE></BLOCKQUOTE> </CODE></BLOCKQUOTE>
This workaround is available in 1.2.2, and in a This workaround is available in 1.2.2, and in a
<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. >patch</A> against 1.2.1.
<H3><A NAME="257th-byte">Boundary problems with header parsing</A></H3> <H3><A NAME="257th-byte">Boundary problems with header parsing</A></H3>