pepper 00/11/22 12:48:01
Modified: htdocs/manual content-negotiation.html dns-caveats.html
dso.html ebcdic.html invoking.html
Log:
Typo & entity fixes.
</p> fixes.
Tags reordered and values quoted in ebcdic.html.
Revision Changes Path
1.24 +1 -1 httpd-docs-1.3/htdocs/manual/content-negotiation.html
Index: content-negotiation.html
===================================================================
RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/content-negotiation.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- content-negotiation.html 2000/04/29 14:18:44 1.23
+++ content-negotiation.html 2000/11/22 20:47:56 1.24
@@ -339,7 +339,7 @@
<LI>Select the variants with the best language match, using either the
order of languages in the Accept-Language header (if present), or else
- else the order of languages in the <CODE>LanguagePriority</CODE>
+ the order of languages in the <CODE>LanguagePriority</CODE>
directive (if present).
<LI>Select the variants with the highest 'level' media parameter
1.12 +1 -1 httpd-docs-1.3/htdocs/manual/dns-caveats.html
Index: dns-caveats.html
===================================================================
RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/dns-caveats.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- dns-caveats.html 2000/11/13 02:01:35 1.11
+++ dns-caveats.html 2000/11/22 20:47:56 1.12
@@ -144,7 +144,7 @@
<H3><A NAME="tips">Tips to Avoid these problems</A></H3>
<UL>
-<LI> use IP addresses in <CODE><VirtualHost></CODE>
+<LI> use IP addresses in <CODE><VirtualHost></CODE>
<LI> use IP addresses in <CODE>Listen</CODE>
<LI> use IP addresses in <CODE>BindAddress</CODE>
<LI> ensure all virtual hosts have an explicit <CODE>ServerName</CODE>
1.17 +2 -2 httpd-docs-1.3/htdocs/manual/dso.html
Index: dso.html
===================================================================
RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/dso.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- dso.html 2000/06/04 03:49:52 1.16
+++ dso.html 2000/11/22 20:47:57 1.17
@@ -23,7 +23,7 @@
</H1>
<ADDRESS>Originally written by<BR>
-Ralf S. Engelschall <[EMAIL PROTECTED]>, April 1998</ADDRESS>
+Ralf S. Engelschall <[EMAIL PROTECTED]>, April 1998</ADDRESS>
</DIV>
@@ -329,7 +329,7 @@
</OL>
-<H3>Advantages & Disadvantages</H3>
+<H3>Advantages & Disadvantages</H3>
<P>The above DSO based features of Apache 1.3 have the following advantages:
1.9 +23 -14 httpd-docs-1.3/htdocs/manual/ebcdic.html
Index: ebcdic.html
===================================================================
RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/ebcdic.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- ebcdic.html 1998/10/01 18:25:12 1.8
+++ ebcdic.html 2000/11/22 20:47:59 1.9
@@ -27,6 +27,8 @@
<P>
The port was started initially to
+ </P>
+
<UL>
<LI> prove the feasibility of porting
<A HREF="http://dev.apache.org/";>the Apache HTTP server</A>
@@ -38,7 +40,6 @@
easily outperform the accept-fork-serve model used by CERN by a
factor of 5 or more.
</UL>
- </P>
<P>
This document serves as a rationale to describe some of the design
@@ -69,6 +70,8 @@
time, so a BUFF flag was added which defines whether a BUFF object
has currently enabled conversion or not. This flag is modified at
several points in the HTTP protocol:
+ </P>
+
<UL>
<LI><STRONG>set</STRONG> before a request is received (because the
request and the request header lines are always in ASCII
@@ -85,10 +88,9 @@
sent - depending on the content type of the response body
(because the response body may contain text or a binary file)
</UL>
- </P>
<H2 ALIGN=CENTER>Porting Notes</H2>
- <P>
+
<OL>
<LI>
The relevant changes in the source are #ifdef'ed into two
@@ -105,8 +107,9 @@
mainframe platform only. This deals with include file
differences and socket implementation topics which are
only required on the BS2000/OSD platform.
+ <BR>
</DL>
- </LI><BR>
+ </LI>
<LI>
The possibility to translate between ASCII and EBCDIC at the
@@ -125,7 +128,8 @@
therefore be inadequate.<BR>
(In the case of text files of course, provisions must be made so
that EBCDIC documents are always served in ASCII)
- </LI><BR>
+ <BR>
+ </LI>
<LI>
This port therefore features a built-in protocol level conversion
@@ -137,7 +141,8 @@
not be converted to ASCII a second time. This exception is
only relevant for server-generated strings; and <EM>external</EM>
EBCDIC documents are not expected to contain ASCII newline characters.
- </LI><BR>
+ <BR>
+ </LI>
<LI>
By examining the call hierarchy for the BUFF management
@@ -157,7 +162,8 @@
based on the type of document being served, whether the
document body (except for the chunking information, of
course) is in ASCII already or must be converted from EBCDIC.
- </LI><BR>
+ <BR>
+ </LI>
<LI>
For Text documents (MIME types text/plain, text/html <EM>etc.</EM>),
@@ -175,20 +181,23 @@
</PRE></BLOCKQUOTE>
Similarly, any text/XXXX MIME type can be served as "raw ASCII" by
configuring a MIME type "text/x-ascii-XXXX" for it using AddType.
- </LI><BR>
+ <BR>
+ </LI>
<LI>
Non-text documents are always served "binary" without conversion.
This seems to be the most sensible choice for, .<EM>e.g.</EM>, GIF/ZIP/AU
file types. This of course requires the user to copy them to the
mainframe host using the "rcp -b" binary switch.
- </LI><BR>
+ <BR>
+ </LI>
<LI>
Server parsed files are always assumed to be in native (<EM>i.e.</EM>,
EBCDIC) format as used on the machine, and are converted after
processing.
- </LI><BR>
+ <BR>
+ </LI>
<LI>
For CGI output, the CGI script determines whether a conversion is
@@ -196,9 +205,9 @@
can be converted, or GIF output can be passed through unmodified.
An example for the latter case is the wwwcount program which we ported
as well.
- </LI><BR>
+ <BR>
+ </LI>
</OL>
- </P>
<H2 ALIGN=CENTER>Document Storage Notes</H2>
<H3 ALIGN=CENTER>Binary Files</H3>
@@ -232,7 +241,7 @@
</P>
<H2 ALIGN=CENTER>Apache Modules' Status</H2>
- <TABLE BORDER ALIGN=middle>
+ <TABLE BORDER="1" ALIGN="middle">
<TR>
<TH>Module
<TH>Status
@@ -457,7 +466,7 @@
</TABLE>
<H2 ALIGN=CENTER>Third Party Modules' Status</H2>
- <TABLE BORDER ALIGN=middle>
+ <TABLE BORDER="1" ALIGN="middle">
<TR>
<TH>Module
<TH>Status
1.29 +1 -1 httpd-docs-1.3/htdocs/manual/invoking.html
Index: invoking.html
===================================================================
RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/invoking.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- invoking.html 2000/09/12 16:24:57 1.28
+++ invoking.html 2000/11/22 20:47:59 1.29
@@ -42,7 +42,7 @@
Windows and <CODE>/os2httpd</CODE> on OS/2.
<DT><CODE>-D</CODE> <EM>name</EM>
-<DD>Define a name for use in in
+<DD>Define a name for use in
<A HREF="mod/core.html#ifdefine">IfDefine</A> directives.
This option can be used to optionally enable certain functionality in the
configuration file, or to use a common configuration for
