httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@hyperreal.org
Subject cvs commit: apache-1.3/htdocs/manual/mod mod_mime.html
Date Fri, 08 Jan 1999 23:13:31 GMT
coar        99/01/08 15:13:30

  Modified:    htdocs/manual install-tpf.html readme-tpf.html suexec.html
                        suexec_1_2.html
               htdocs/manual/mod mod_mime.html
  Log:
  	The semi-occasional partial cleaning-up of the HTML..
  
  Revision  Changes    Path
  1.4       +157 -148  apache-1.3/htdocs/manual/install-tpf.html
  
  Index: install-tpf.html
  ===================================================================
  RCS file: /home/cvs/apache-1.3/htdocs/manual/install-tpf.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- install-tpf.html	1999/01/06 21:56:57	1.3
  +++ install-tpf.html	1999/01/08 23:13:27	1.4
  @@ -1,109 +1,121 @@
   <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
  -<html>
  -<head>
  -<title>Installing Apache on TPF</title>
  -</head>
  +<HTML>
  +<HEAD>
  +<TITLE>Installing Apache on TPF</TITLE>
  +</HEAD>
   
  -<a name="top"></a>
  -<h1 align="center">Installing the Apache 1.3 HTTP Server on TPF</h1>
  -<hr>
  -<center>[&nbsp<a href="#setup">Setup</a>
  -   &nbsp|&nbsp<a href="#compilation">Compilation</a>
  -   &nbsp|&nbsp<a href="#installation">Installation</a>
  -   &nbsp|&nbsp<a href="#visualage">VisualAge</a>&nbsp]
  -</center>
  -<hr>
  -<br>
  +<BODY>
  +<H1 ALIGN="center">
  + <A NAME="top">Installing the Apache 1.3 HTTP Server on TPF</A>
  +</H1>
  +<HR>
  +<CENTER>[&nbsp;<A HREF="#setup">Setup</A>
  +   &nbsp;|&nbsp;<A HREF="#compilation">Compilation</A>
  +   &nbsp;|&nbsp;<A HREF="#installation">Installation</A>
  +   &nbsp;|&nbsp;<A HREF="#visualage">VisualAge</A>&nbsp;]
  +</CENTER>
  +<HR>
  +<BR>
   
  -<p>
  +<P>
   This document outlines the steps needed to install Apache onto a TPF system.
  -<br><br>
  -You should first read htdocs/manual/<a href="readme-tpf.html">readme-tpf.html</a>
  +</P>
  +<P>
  +You should first read
  +htdocs/manual/<A HREF="readme-tpf.html">readme-tpf.html</A>
   for basic information on the port of Apache to TPF including required PUT level
   and supported functions &amp; modules.
  -</p>
  +</P>
   
  -<a name="setup">&nbsp;</a>
  -<h2 align=center>Setup</h2>
  -<p>
  -Due to the use of EBCDIC on MVS OS/390 Open Edition (later referred to simply as
  +<H2 align=center><A NAME="setup">Setup</A></H2>
  +<P>
  +Due to the use of EBCDIC on MVS OS/390 Open Edition
  +(later referred to simply as
   "Open Edition"), we've found that the most reliable
   method for loading Apache onto your system is to unzip and tar the distribution
  -file on your PC, and then copy the extracted files to Open Edition via an NFS client
  +file on your PC, and then copy the extracted files to Open Edition
  +via an NFS client
   capable of transferring the data in EBCDIC format.
  -<br><br>
  +</P>
  +<P>
   Before moving the distribution to an
   Open Edition environment, verify that the NFS drive will transfer the
   filenames with upper/lower case preserved.
  -<br><br>
  +</P>
  +<P>
   Since Open Edition is not the ultimate destination of the files,
  -the only required files and subdirectories that need to be moved to Open Edition
  +the only required files and subdirectories that need to be moved to
  +Open Edition
   are in /src.
  -<br><br>
  -<font strong color=red>WARNING</font>:
  +</P>
  +<P>
  +<FONT COLOR=red><STRONG>WARNING</STRONG></FONT>:
   If you are using a product such as WinZip on your PC, verify that
  -the <i>"TAR File Smart CR/LF Conversion"</i> option is NOT checked.
  +the <EM>"TAR File Smart CR/LF Conversion"</EM> option is NOT checked.
   You can find this in WinZip under Options, Configuration.
   Since you had to tar and unzip the file to read this document,
   you need to re-tar and -unzip if the CR/LF option was checked.
   This will save you lots of headaches later on.
  -<br><br>
  -<font strong color=red>WARNING</font>:
  +</P>
  +<P>
  +<FONT COLOR=red><STRONG>WARNING</STRONG></FONT>:
   Editing files on a PC before moving them to Open Edition may result
  -in the loss/addition of unprintable characters.  Files of concern include shell
  -scripts and src/Configuration.  The most common problems are with tab characters
  +in the loss/addition of unprSintable characters.  Files of concern include shell
  +scripts and src/Configuration.  The most common problems are with
  +tab characters
   and CR/LF characters.  Most editors will handle the CR/LF problem correctly
   but none seem to handle tab characters.  If you need to edit files, edit them
   in a UNIX editor such as vi or emacs.
  -</p>
  +</P>
   
  -<a name="compilation">&nbsp;</a>
  -<h2 align=center>Compilation</h2>
  -<p>
  +<H2 align=center><A NAME="compilation">Compilation</A></H2>
  +<P>
   Apache supports the notion of "optional modules".  However,
   the server has to know which modules are compiled into it.  In order for
   those modules to be effective, it is necessary to generate a short bit of
   code ("modules.c") which simply has a list of them. If you are using the
   make and Configure utility, "modules.c" will be created for you.
  -<br><br>
  +</P>
  +<P>
   The provided scripts assume a c89 compiler and have only been tested on an
   Open Edition environment.  If you are using a platform other that
   Open Edition you may need to modify src/os/tpf/TPFExport and src/Configure
   to match your environment.
  -<br><br>
  +</P>
  +<P>
   Note that UNIX/Open Edition commands in this section are shown in
  -<tt><strong>bold</strong></tt>,
  +<TT><STRONG>bold</STRONG></TT>,
   are case sensitive, and must be made from the "src" directory.
  -<br><br>
  -<ol>
  -<li>Overlay src/Configuration with src/Configuration.tmpl:  
  -    <tt><strong>cp&nbsp;Configuration.tmpl&nbsp;Configuration</strong></tt>
  -    <br><br>
  -<li>Edit src/Configuration.  It contains the list and settings
  +</P>
  +<OL>
  +<LI>Overlay src/Configuration with src/Configuration.tmpl:  
  +    <TT><STRONG>cp&nbsp;Configuration.tmpl&nbsp;Configuration</STRONG></TT>
  +    <BR><BR>
  +<LI>Edit src/Configuration.  It contains the list and settings
       of various "Rules" and an additional section at the bottom that determines
       which modules to compile:
  -    <br><br>
  -    <ol type=a>
  -    <li>Adjust the Rules and <tt>EXTRA_CFLAGS|LIBS|LDFLAGS|INCLUDES</tt>
  +    <BR><BR>
  +    <OL type=a>
  +    <LI>Adjust the Rules and <TT>EXTRA_CFLAGS|LIBS|LDFLAGS|INCLUDES</TT>
           if you feel so inclined.
  -    <br><br>
  -    <li>Comment out (by preceding the line with a "#") lines corresponding
  +    <BR><BR>
  +    <LI>Comment out (by preceding the line with a "#") lines corresponding
           to those modules you DO&nbsp;NOT wish to include.
           At present the following modules MUST be commented out
           as they are not yet supported on TPF: mod_actions, mod_auth,
           mod_cgi, mod_env, mod_include, & mod_status.
  -    <br><br>
  -    <li>Uncomment (by removing the initial "#", if present) lines
  +    <BR><BR>
  +    <LI>Uncomment (by removing the initial "#", if present) lines
           corresponding to those optional modules you wish
           to include or add new lines corresponding to any custom modules
           you have written.
  -        The htdocs/manual/<a href="readme-tpf.html">readme-tpf.html</a>
  +        The htdocs/manual/<A HREF="readme-tpf.html">readme-tpf.html</A>
           document lists the modules that have been tested on TPF.
  -    </ol>
  -    <br>
  -<li>Set the TPF environment variables:
  -    <tt><strong>.&nbsp;os/tpf/TPFExport</strong></tt>
  -    <br>
  +    </OL>
  +    <BR>
  +<LI>Set the TPF environment variables:
  +    <TT><STRONG>.&nbsp;os/tpf/TPFExport</STRONG></TT>
  +    <BR>
       (The initial period and blank on the command are required to ensure
       the environment variables exist beyond the scope of the shell script.)
       This script will set the environment variables required to compile the
  @@ -111,14 +123,14 @@
       installation, in particular, the system include file directories.  The
       system include files must reside on your Open Edition system in the
       appropriate file structure similar to /usr/include and /usr/include/sys.
  -    DO&nbsp;NOT modify the <tt>TPF=YES</tt> export variable.  If this is
changed, the
  -    "Configure" script will not recognize TPF.
  -    <br><br>
  -<li>Run the "Configure" script:
  -    <tt><strong>Configure</strong></tt>
  -    <br>
  +    DO&nbsp;NOT modify the <TT>TPF=YES</TT> export variable.  If this is
  +    changed, the "Configure" script will not recognize TPF.
  +    <BR><BR>
  +<LI>Run the "Configure" script:
  +    <TT><STRONG>Configure</STRONG></TT>
  +    <BR>
       The output will look something like this...
  -      <pre>
  +      <PRE>
         Using config file: Configuration
         Creating Makefile
          + configured for TPF platform
  @@ -134,134 +146,131 @@
         Creating Makefile in modules/standard
         Creating Makefile in modules/example
         $ _
  -      </pre>
  +      </PRE>
       This generates modules.c and new versions of the Makefiles.
  -    <br><br>
  -    If you want to maintain multiple configurations, you can say, e.g.,
  -    <br>
  -    <tt><strong>Configure -file Configuration.ai</strong></tt>
  -    <br>
  -      <pre>
  +    <BR><BR>
  +    If you want to maintain multiple configurations, you can
  +    say, <EM>e.g.</EM>,
  +    <BR>
  +    <TT><STRONG>Configure -file Configuration.ai</STRONG></TT>
  +    <BR>
  +      <PRE>
         Using config file: Configuration.ai
         Creating Makefile
          + configured for &lt;whatever&gt; platform
          + setting C compiler to &lt;whatever&gt;
         et cetera
  -      </pre>
  +      </PRE>
   
  -    If you receive an error such as "<tt>Configure 146: FSUM7351 not found</tt>"
  +    If you receive an error such as "<TT>Configure 146: FSUM7351 not found</TT>"
       the most likely explanation is that one or more of the make related
       files were edited on a non-UNIX platform, corrupting the end-of-line marks.
       Verify that lines ending with "\" in the flagged file do&nbsp;not have trailing
       spaces.  Using the vi editor and the sample error above as an example...
  -    <br><br><pre>
  -            pull up the flagged file:       <strong>vi&nbsp;Configure</strong>
  -            turn on punctuation:            <strong>:set&nbsp;list</strong>
  -            go to the line in question:     <strong>146G</strong>
  -               or find a line with a "\":   <strong>/\\</strong></pre>
  -    The end of line should display as "<tt>\$</tt>".  If it is displayed as
  -    "<tt>\ $</tt>" (with a blank between \ and $) then you should revert to
the
  +    <BR><BR><PRE>
  +            pull up the flagged file:       <STRONG>vi&nbsp;Configure</STRONG>
  +            turn on punctuation:            <STRONG>:set&nbsp;list</STRONG>
  +            go to the line in question:     <STRONG>146G</STRONG>
  +               or find a line with a "\":   <STRONG>/\\</STRONG></PRE>
  +    The end of line should display as "<TT>\$</TT>".  If it is displayed as
  +    "<TT>\ $</TT>" (with a blank between \ and $) then you should revert to
the
       distributed version of the file and make the site-specific
       changes again using a UNIX compatible editor such as vi or emacs.
       Then try the Configure command again.
  -    <br><pre>            close the file:                 <strong>:q 
</strong>(or 
  +    <BR><PRE>            close the file:                 <STRONG>:q 
</STRONG>(or 
   
  -<strong>:quit!</strong>)</pre>
  -<li>Now compile the programs: <tt><strong>make</strong></tt><br>
  +<STRONG>:quit!</STRONG>)</PRE>
  +<LI>Now compile the programs: <TT><STRONG>make</STRONG></TT><BR>
       The modules placed in the Apache distribution are the ones that have been
       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/contrib/modules/">http://www.apache.org/dist/contrib/modules/</A>.
       There are instructions on that page for linking these modules into the core Apache
       code.
  -    <br><br>
  +    <BR><BR>
       If during compilation you get a warning about a missing 'regex.h', set
  -    <tt>WANTHSREGEX=yes</tt> in the src/Configuration file and start back at
the
  -    <tt><strong>Configure</strong></tt> step.
  -</ol>
  -</p>
  +    <TT>WANTHSREGEX=yes</TT> in the src/Configuration file and start back at
the
  +    <TT><STRONG>Configure</STRONG></TT> step.
  +</OL>
   
  -<a name="installation">&nbsp;</a>
  -<h2 align=center>Installation</h2>
  -<ol>
  -<li>After compilation, you will have all the object files required to build an
  +<A NAME="installation">&nbsp;</A>
  +<H2 align=center>Installation</H2>
  +<OL>
  +<LI>After compilation, you will have all the object files required to build an
     "httpd" loadset.  The next step is to link the object files and create a loadset to be
     stored in a PDS.  Sample JCL for linking and loadsets has been included in
     src/os/tpf/samples as "linkdll.jcl" and "loadset.jcl".  You can submit these jobs
     from CMS or directly from Open Edition if you have the proper authority.  After
  -  the jobs have completed, you can <tt>ZOLDR LOAD</tt> them to your TPF system.
  -  <br><br>
  -  NOTE: The <tt>mod_<i>xxx</i>.o</tt> files in the linkdll.jcl
file must correspond to the
  -  <tt>mod_<i>xxx</i>.o</tt> lines in the src/Configuration file.
  -  <br><br>
  -<li>
  +  the jobs have completed, you can <TT>ZOLDR LOAD</TT> them to your TPF system.
  +  <BR><BR>
  +  NOTE: The <TT>mod_<EM>xxx</EM>.o</TT> files in the linkdll.jcl
file must correspond to the
  +  <TT>mod_<EM>xxx</EM>.o</TT> lines in the src/Configuration file.
  +  <BR><BR>
  +<LI>
     Apache requires a configuration file to initialize itself during activation.
     (Previously three configuration files were used.)
     Copy the distribution version, /conf/httpd.conf-dist, to /conf/httpd.conf and then
     edit the /conf/httpd.conf copy with your site specific information.  This first release
     of Apache for TPF only runs under the "inetd" model so you
  -  <font strong color=red>must</font> change <tt>ServerType</tt>
from <tt>standalone</tt>
  -  to <tt>inetd</tt>.
  -  <br><br>
  +  <font color=red><STRONG>must</STRONG></FONT> change <TT>ServerType</TT>
from <TT>standalone</TT>
  +  to <TT>inetd</TT>.
  +  <BR><BR>
     General documentation for Apache is located at
  -  <a href="http://www.apache.org/docs/">http://www.apache.org/docs/</a>
  +  <A HREF="http://www.apache.org/docs/">http://www.apache.org/docs/</A>
     and in the HTML pages included with this distribution under the
     /htdocs/manual directory.
  -  <br><br>
  -<li>On TPF activate ZCLAW and update INETD using ZINET entries, the common case:
  -    <br><br>
  -    <pre>
  +  <BR><BR>
  +<LI>On TPF activate ZCLAW and update INETD using ZINET entries, the common case:
  +    <BR><BR>
  +    <PRE>
       ZINET ADD S-TFTP   PGM-CTFT PORT-69 PROTOCOL-UDP MODEL-NOWAIT
  -    ZINET ADD S-APACHE PGM-<i>pppp</i> PORT-80 PROTOCOL-TCP MODEL-NOWAIT</pre>
  -  Please refer to <i>IBM Transaction Processing Facility Transmission Control
  -  Protocol/Internet Protocol Version 4 Release 1</i> for more information
  +    ZINET ADD S-APACHE PGM-<EM>pppp</EM> PORT-80 PROTOCOL-TCP MODEL-NOWAIT</PRE>
  +  Please refer to <EM>IBM Transaction Processing Facility Transmission Control
  +  Protocol/Internet Protocol Version 4 Release 1</EM> for more information
     on ZCLAW, INETD, and TFTP.
  -  <br><br>
  -<li>Prior to sending a request to your Apache server from a browser,
  +  <BR><BR>
  +<LI>Prior to sending a request to your Apache server from a browser,
       TFTP the configuration file, log, icons and web pages to your TPF system.
       A typical directory structure for Apache is as follows:
  -<pre>     /usr/local/apache/conf
  +<PRE>     /usr/local/apache/conf
        /usr/local/apache/logs
        /usr/local/apache/icons
  -     /usr/local/apache/htdocs</pre>
  +     /usr/local/apache/htdocs</PRE>
       The logs directory must exist in order to avoid an
  -    <code>fopen</code> error while running Apache.  TFTP an empty file into
  +    <CODE>fopen</CODE> error while running Apache.  TFTP an empty file into
       the logs subdirectory to create it.  All gif, jpg, and zip files should be
       TFTP'd as binary; conf files and html pages should be TFTP'd as text.
  -</ol>
  -<a name="visualage">&nbsp;</a>
  -<h2 align=center>Compiling with VisualAge TPF</h2>
  -<p>
  +</OL>
  +<A NAME="visualage">&nbsp;</A>
  +<H2 align=center>Compiling with VisualAge TPF</H2>
  +<P>
     It is not required that "make" be used to compile Apache for TPF:
     Individual programs may be compiled using IBM's VisualAge TPF product.
     This is particularly useful when compiling selected programs for the Debug Tool.
  -  <br><br>
  +  <BR><BR>
     The following VisualAge compile settings are required:
  -  <ul>
  -  <li><i>"DEFINE - Define preprocessor macro name(s)"</i> must include
  -     <tt><strong>TPF, CHARSET_EBCDIC, _POSIX_SOURCE,</strong></tt>
and
  -     <tt><strong>USE_HSREGEX</strong></tt>
  -  <br><br>
  -  <li><i>"LSEARCH - Path for user include files"</i> must include
  -     <tt><strong>../src/include</strong></tt> and <tt><strong>../src/os/tpf</strong></tt>
  -  <br><br>
  -  <li><i>"DLL - Generate DLL code"</i> must be checked
  -  <br><br>
  -  <li><i>"LONGNAME - Support long names"</i> must be checked
  -  </ul>
  -</p>
  -<hr>
  -<center>[&nbsp<a href="#top">top</a>
  -   &nbsp|&nbsp<a href="#setup">Setup</a>
  -   &nbsp|&nbsp<a href="#compilation">Compilation</a>
  -   &nbsp|&nbsp<a href="#installation">Installation</a>
  -   &nbsp|&nbsp<a href="#visualage">VisualAge</a>&nbsp]
  -</center>
  +  <UL>
  +  <LI><EM>"DEFINE - Define preprocessor macro name(s)"</EM> must include
  +     <TT><STRONG>TPF, CHARSET_EBCDIC, _POSIX_SOURCE,</STRONG></TT>
and
  +     <TT><STRONG>USE_HSREGEX</STRONG></TT>
  +  <BR><BR>
  +  <LI><EM>"LSEARCH - Path for user include files"</EM> must include
  +     <TT><STRONG>../src/include</STRONG></TT> and <TT><STRONG>../src/os/tpf</STRONG></TT>
  +  <BR><BR>
  +  <LI><EM>"DLL - Generate DLL code"</EM> must be checked
  +  <BR><BR>
  +  <LI><EM>"LONGNAME - Support long names"</EM> must be checked
  +  </UL>
  +</P>
  +<HR>
  +<CENTER>[&nbsp;<A HREF="#top">top</A>
  +   &nbsp;|&nbsp;<A HREF="#setup">Setup</A>
  +   &nbsp;|&nbsp;<A HREF="#compilation">Compilation</A>
  +   &nbsp;|&nbsp;<A HREF="#installation">Installation</A>
  +   &nbsp;|&nbsp;<A HREF="#visualage">VisualAge</A>&nbsp;]
  +</CENTER>
   
  -</body>
  -</html>
  +</BODY>
  +</HTML>
  
  
  
  1.4       +163 -163  apache-1.3/htdocs/manual/readme-tpf.html
  
  Index: readme-tpf.html
  ===================================================================
  RCS file: /home/cvs/apache-1.3/htdocs/manual/readme-tpf.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- readme-tpf.html	1999/01/06 21:56:57	1.3
  +++ readme-tpf.html	1999/01/08 23:13:27	1.4
  @@ -1,206 +1,206 @@
   <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
  -<html>
  -<head>
  -<title>The Apache TPF Port</title>
  -</head>
  -
  -<a name="top"></a>
  -<h1 align="center">Overview of the Apache TPF Port</h1>
  -<hr>
  -<center>[&nbsp<a href="#configuration_files">Configuration Files</a>
  -   &nbsp|&nbsp<a href="#auto_generated_files">Auto Generated Files</a>
  -   &nbsp|&nbsp<a href="#whats_available">What's Available</a>
  -   &nbsp|&nbsp<a href="#porting_notes">Porting Notes</a>&nbsp]
  -</center>
  -<hr>
  -<br>
  +<HTML>
  +<HEAD>
  +<TITLE>The Apache TPF Port</TITLE>
  +</HEAD>
  +<BODY>
  +<A NAME="top"></A>
  +<H1 align="center">Overview of the Apache TPF Port</H1>
  +<HR>
  +<CENTER>[&nbsp;<A HREF="#configuration_files">Configuration Files</A>
  +   &nbsp;|&nbsp;<A HREF="#auto_generated_files">Auto Generated Files</A>
  +   &nbsp;|&nbsp;<A HREF="#whats_available">What's Available</A>
  +   &nbsp;|&nbsp;<A HREF="#porting_notes">Porting Notes</A>&nbsp;]
  +</CENTER>
  +<HR>
  +<BR>
   
  -<p>
  +<P>
      This version of Apache includes changes allowing it to run on
      IBM's EBCDIC-based
  -   <a href="http://www.s390.ibm.com/products/tpf/tpfhp.html">TPF</a>
  +   <A HREF="http://www.s390.ibm.com/products/tpf/tpfhp.html">TPF</A>
      (Transaction Processing Facility) operating system.
      Unless otherwise noted TPF version 4.1 PUT08 and APAR PJ25589 are required.
  -   <br><br>
  -   Refer to htdocs/manual/<a href="install-tpf.html">install-tpf.html</a>
  +   <BR><BR>
  +   Refer to htdocs/manual/<A HREF="install-tpf.html">install-tpf.html</A>
      for step-by-step installation instructions.
  -   <br><br>
  +   <BR><BR>
      As this is the first cut at making Apache run on TPF,
      performance tuning has not been done.
  -   <br><br>
  -   This port builds upon the <a href="ebcdic.html">EBCDIC changes</a>
  +   <BR><BR>
  +   This port builds upon the <A HREF="ebcdic.html">EBCDIC changes</A>
      previously made to Apache.
  -   <br>
  -</p>
  +   <BR>
  +</P>
   
  -<a name="configuration_files">&nbsp;</a>
  -<h2 align=center>Apache Configuration Files</h2>
  -<p>
  +<A NAME="configuration_files">&nbsp;</A>
  +<H2 align=center>Apache Configuration Files</H2>
  +<P>
      The distributed configuration files (httpd.conf-dist and
      mime.types, both located in the conf subdirectory)
      work on TPF with only a couple of operating system specific changes
  -   to httpd.conf:<br>
  -   <ul>
  -   <li>ServerType needs to be "inetd" since TPF does not yet support
  +   to httpd.conf:<BR>
  +   <UL>
  +   <LI>ServerType needs to be "inetd" since TPF does not yet support
          "standalone" mode.
  -   <li>Performance considerations may dictate setting KeepAlive to "Off"
  +   <LI>Performance considerations may dictate setting KeepAlive to "Off"
          (the default is "On") or lowering the Timeout value from the default
          300 seconds (5 minutes) in order to reduce the number of active ECBs on your system.
  -   </ul>
  -</p>
  +   </UL>
  +</P>
   
  -<a name="whats_available">&nbsp;</a>
  -<h2 align=center>What's Available in this Version</h2>
  +<A NAME="whats_available">&nbsp;</A>
  +<H2 align=center>What's Available in this Version</H2>
   
      (The Apache organization provides
  -   <a href="http://www.apache.org/docs/">online documentation</a>
  +   <A HREF="http://www.apache.org/docs/">online documentation</A>
      describing the various modules and components of the server.)
   
  -<h3>Components/modules tested on TPF:</h3>
  +<H3>Components/modules tested on TPF:</H3>
   
  -   <multicol COLS=3><ul>
  -   <li>alloc.c
  -   <li>ap_cpystrn.c
  -   <li>ap_fnmatch.c
  -   <li>ap_signal.c
  -   <li>ap_slack.c
  -   <li>ap_snprintf.c
  -   <li>buff.c
  -   <li>buildmark.c
  -   <li>ebcdic.c
  -   <li>http_config.c
  -   <li>http_core.c
  -   <li>http_log.c
  -   <li>http_main.c
  -   <li>http_protocol.c
  -   <li>http_request.c
  -   <li>http_vhost.c <a href="#note_2">*</a>
  -   <li>mod_access.c
  -   <li>mod_alias.c
  -   <li>mod_asis.c
  -   <li>mod_autoindex.c
  -   <li>mod_cern_meta.c
  -   <li>mod_dir.c
  -   <li>mod_example.c
  -   <li>mod_expires.c
  -   <li>mod_headers.c
  -   <li>mod_imap.c
  -   <li>mod_info.c
  -   <li>mod_log_agent.c
  -   <li>mod_log_config.c
  -   <li>mod_log_referer.c
  -   <li>mod_mime.c
  -   <li>mod_negotiation.c
  -   <li>mod_setenvif.c
  -   <li>mod_speling.c
  -   <li>mod_userdir.c
  -   <li>mod_usertrack.c
  -   <li>os.c
  -   <li>os-inline.c
  -   <li>regular expression parser
  -   <li>util.c
  -   <li>util_date.c
  -   <li>util_uri.c
  -   </ul></multicol>
  +   <multicol COLS=3><UL>
  +   <LI>alloc.c
  +   <LI>ap_cpystrn.c
  +   <LI>ap_fnmatch.c
  +   <LI>ap_signal.c
  +   <LI>ap_slack.c
  +   <LI>ap_snprintf.c
  +   <LI>buff.c
  +   <LI>buildmark.c
  +   <LI>ebcdic.c
  +   <LI>http_config.c
  +   <LI>http_core.c
  +   <LI>http_log.c
  +   <LI>http_main.c
  +   <LI>http_protocol.c
  +   <LI>http_request.c
  +   <LI>http_vhost.c <A HREF="#note_2">*</A>
  +   <LI>mod_access.c
  +   <LI>mod_alias.c
  +   <LI>mod_asis.c
  +   <LI>mod_autoindex.c
  +   <LI>mod_cern_meta.c
  +   <LI>mod_dir.c
  +   <LI>mod_example.c
  +   <LI>mod_expires.c
  +   <LI>mod_headers.c
  +   <LI>mod_imap.c
  +   <LI>mod_info.c
  +   <LI>mod_log_agent.c
  +   <LI>mod_log_config.c
  +   <LI>mod_log_referer.c
  +   <LI>mod_mime.c
  +   <LI>mod_negotiation.c
  +   <LI>mod_setenvif.c
  +   <LI>mod_speling.c
  +   <LI>mod_userdir.c
  +   <LI>mod_usertrack.c
  +   <LI>os.c
  +   <LI>os-inline.c
  +   <LI>regular expression parser
  +   <LI>util.c
  +   <LI>util_date.c
  +   <LI>util_uri.c
  +   </UL></MULTICOL>
      Please keep in mind that some major pieces are not yet in place including
      standalone mode, pipes, password/group files, CGI scripts, and MD5 support.
  -   <br>
  -   <a name="note_2">&nbsp;</a>
  -   <br>
  +   <BR>
  +   <A NAME="note_2">&nbsp;</A>
  +   <BR>
      * virtual hosting requires TPF version 4.1 PUT09
   
  -<h3>Components/modules not (yet?) supported on TPF:</h3>
  +<H3>Components/modules not (yet?) supported on TPF:</H3>
   
  -   <multicol COLS=3><ul>
  -   <li>htpasswd.c
  -   <li>md5c.c
  -   <li>mod_actions.c
  -   <li>mod_auth.c
  -   <li>mod_auth_anon.c
  -   <li>mod_cgi.c
  -   <li>mod_digest.c
  -   <li>mod_env.c
  -   <li>mod_include.c
  -   <li>mod_mime_magic.c
  -   <li>mod_proxy.c
  -   <li>mod_rewrite.c
  -   <li>mod_status.c
  -   <li>mod_unique_id.c
  -   <li>proxy_cache.c
  -   <li>proxy_connect.c
  -   <li>proxy_ftp.c
  -   <li>proxy_http.c
  -   <li>proxy_util.c
  -   <li>rfc1413.c
  -   <li>util_md5.c
  -   <li>util_script.c
  -   </ul></multicol>
  -
  -<h3>Components/modules that don't apply or that probably won't ever be available
on TPF:</h3>
  -
  -   <multicol COLS=3><ul>
  -   <li>gen_test.char.c
  -   <li>gen_uri_delims.c
  -   <li>mod_auth_db.c
  -   <li>mod_auth_dbm.c
  -   <li>mod_auth_db.module
  -   <li>mod_mmap_static.c
  -   <li>mod_so.c
  -   </ul></multicol>
  -
  -<a name="porting_notes">&nbsp;</a>
  -<h2 align=center>Porting Notes</h2>
  -<p>
  -   <h3>Changes made due to differences between UNIX and
  -   TPF's process models:</h3>
  -   <ul>
  -   <li><b>Signals</b>: On TPF a signal that is sent to a process
  +   <multicol COLS=3><UL>
  +   <LI>htpasswd.c
  +   <LI>md5c.c
  +   <LI>mod_actions.c
  +   <LI>mod_auth.c
  +   <LI>mod_auth_anon.c
  +   <LI>mod_cgi.c
  +   <LI>mod_digest.c
  +   <LI>mod_env.c
  +   <LI>mod_include.c
  +   <LI>mod_mime_magic.c
  +   <LI>mod_proxy.c
  +   <LI>mod_rewrite.c
  +   <LI>mod_status.c
  +   <LI>mod_unique_id.c
  +   <LI>proxy_cache.c
  +   <LI>proxy_connect.c
  +   <LI>proxy_ftp.c
  +   <LI>proxy_http.c
  +   <LI>proxy_util.c
  +   <LI>rfc1413.c
  +   <LI>util_md5.c
  +   <LI>util_script.c
  +   </UL></MULTICOL>
  +
  +<H3>Components/modules that don't apply or that probably won't ever be available
on TPF:</H3>
  +
  +   <multicol COLS=3><UL>
  +   <LI>gen_test.char.c
  +   <LI>gen_uri_delims.c
  +   <LI>mod_auth_db.c
  +   <LI>mod_auth_dbm.c
  +   <LI>mod_auth_db.module
  +   <LI>mod_mmap_static.c
  +   <LI>mod_so.c
  +   </UL></MULTICOL>
  +
  +<A NAME="porting_notes">&nbsp;</A>
  +<H2 align=center>Porting Notes</H2>
  +<P>
  +   <H3>Changes made due to differences between UNIX and
  +   TPF's process models:</H3>
  +   <UL>
  +   <LI><STRONG>Signals</STRONG>: On TPF a signal that is sent to a process
         remains unhandled until the process explicitly requests that signals
  -      be handled using the <code>tpf_process_signals()</code> function.
  +      be handled using the <CODE>tpf_process_signals()</CODE> function.
         Additionally, the default action for an alarm on TPF is to take
         an OPR-7777 dump and exit.  (On UNIX the default is the equivalent
  -      of <code>exit()</code> with no dump taken.)
  +      of <CODE>exit()</CODE> with no dump taken.)
         These differences necessitated a few modifications:
  -      <br><br>
  -      <ul>
  -      <li>bypass the use of <code>ap_block_alarms()</code> &amp;
  -         <code>ap_unblock_alarms()</code>
  -      <li>add <code>tpf_process_signals()</code> calls
  -      <li>add <code>select()</code> calls in buff.c to prevent blocking.
  -      </ul>
  -   <br>
  -   </ul>
  -
  -   <h3>Find that function...</h3>
  -   <p>Some simple functions &amp; definitions needed to be added
  -      on TPF, such as <code>FD_SET()</code>.
  +      <BR><BR>
  +      <UL>
  +      <LI>bypass the use of <CODE>ap_block_alarms()</CODE> &amp;
  +         <CODE>ap_unblock_alarms()</CODE>
  +      <LI>add <CODE>tpf_process_signals()</CODE> calls
  +      <LI>add <CODE>select()</CODE> calls in buff.c to prevent blocking.
  +      </UL>
  +   <BR>
  +   </UL>
  +
  +   <H3>Find that function...</H3>
  +   <P>Some simple functions &amp; definitions needed to be added
  +      on TPF, such as <CODE>FD_SET()</CODE>.
         We've put these in src/os/tpf/os.h for now.
  -   </p>
  +   </P>
   
  -   <h3>EBCDIC changes:</h3>
  -   <p>TPF-specific conversion tables between US-ASCII and
  +   <H3>EBCDIC changes:</H3>
  +   <P>TPF-specific conversion tables between US-ASCII and
         EBCDIC (character set IBM-1047 to be exact) were created
         and put into ebcdic.c in the src/os/tpf directory.
  -   </p>
  +   </P>
   
  -   <h3>Miscellaneous, minor changes:</h3>
  -   <p>Various minor changes (such as casting) were made due to
  +   <H3>Miscellaneous, minor changes:</H3>
  +   <P>Various minor changes (such as casting) were made due to
         differences in how some functions are implemented on TPF.
  -   </p>
  +   </P>
   
  -   <h3>Temporary changes:</h3>
  -   <p>Lastly, we needed to bypass sections of Apache processing
  +   <H3>Temporary changes:</H3>
  +   <P>Lastly, we needed to bypass sections of Apache processing
         since this first cut for TPF doesn't include
         Standalone mode, pipes, forking, et cetera.
  -   </p>
  +   </P>
   
  -<hr>
  -<center>[&nbsp<a href="#top">top</a>
  -   &nbsp|&nbsp<a href="#configuration_files">Configuration Files</a>
  -   &nbsp|&nbsp<a href="#auto_generated_files">Auto Generated Files</a>
  -   &nbsp|&nbsp<a href="#whats_available">What's Available</a>
  -   &nbsp|&nbsp<a href="#porting_notes">Porting Notes</a>&nbsp]
  -</center>
  +<HR>
  +<CENTER>[&nbsp;<A HREF="#top">top</A>
  +   &nbsp;|&nbsp;<A HREF="#configuration_files">Configuration Files</A>
  +   &nbsp;|&nbsp;<A HREF="#auto_generated_files">Auto Generated Files</A>
  +   &nbsp;|&nbsp;<A HREF="#whats_available">What's Available</A>
  +   &nbsp;|&nbsp;<A HREF="#porting_notes">Porting Notes</A>&nbsp;]
  +</CENTER>
   
  -</body>
  -</html>
  +</BODY>
  +</HTML>
  
  
  
  1.23      +9 -9      apache-1.3/htdocs/manual/suexec.html
  
  Index: suexec.html
  ===================================================================
  RCS file: /home/cvs/apache-1.3/htdocs/manual/suexec.html,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- suexec.html	1998/11/12 20:10:52	1.22
  +++ suexec.html	1999/01/08 23:13:27	1.23
  @@ -309,25 +309,25 @@
       activated by default. At least one --suexec-xxxxx option has to be
       provided together with the --enable-suexec option to let APACI
       accept your request for using the suEXEC feature.
  -<DT><CODE>--suexec-caller=<I>UID</I></CODE>
  +<DT><CODE>--suexec-caller=<EM>UID</EM></CODE>
   <DD>The <A HREF="mod/core.html#user">username</A> under which
       Apache normally runs.
       This is the only user allowed to execute this program.
  -<DT><CODE>--suexec-docroot=<I>DIR</I></CODE>
  +<DT><CODE>--suexec-docroot=<EM>DIR</EM></CODE>
   <DD>Define as the DocumentRoot set for Apache.
       This will be the only hierarchy (aside from UserDirs)
       that can be used for suEXEC behavior.
       The default directory is the --datadir value with 
  -    the suffix "/htdocs", e.g. if you configure with
  +    the suffix "/htdocs", <EM>e.g.</EM> if you configure with
       "<CODE>--datadir=/home/apache</CODE>" the directory
       "/home/apache/htdocs" is used as document root for
       the suEXEC wrapper.
  -<DT><CODE>--suexec-logfile=<I>FILE</I></CODE>
  +<DT><CODE>--suexec-logfile=<EM>FILE</EM></CODE>
   <DD>This defines the filename to which all suEXEC transactions and
       errors are logged (useful for auditing and debugging purposes).
       By default the logfile is named "suexec_log" and located in your
       standard logfile directory (--logfiledir).
  -<DT><CODE>--suexec-userdir=<I>DIR</I></CODE>
  +<DT><CODE>--suexec-userdir=<EM>DIR</EM></CODE>
   <DD>Define to be the subdirectory under users'
       home directories where suEXEC access should
       be allowed.  All executables under this directory
  @@ -346,15 +346,15 @@
       all reside in one parent directory; then name that
       parent directory here.  <STRONG>If this is not defined
       properly, "~userdir" cgi requests will not work!</STRONG>
  -<DT><CODE>--suexec-uidmin=<I>UID</I></CODE>
  +<DT><CODE>--suexec-uidmin=<EM>UID</EM></CODE>
   <DD>Define this as the lowest UID allowed to be a target user
       for suEXEC.  For most systems, 500 or 100 is common.
       Default value is 100.
  -<DT><CODE>--suexec-gidmin=<I>GID</I></CODE>
  +<DT><CODE>--suexec-gidmin=<EM>GID</EM></CODE>
   <DD>Define this as the lowest GID allowed to be a target group
       for suEXEC. For most systems, 100 is common and therefore
       used as default value.
  -<DT><CODE>--suexec-safepath=<I>PATH</I></CODE>
  +<DT><CODE>--suexec-safepath=<EM>PATH</EM></CODE>
   <DD>Define a safe PATH environment to pass to CGI executables.
       Default value is "/usr/local/bin:/usr/bin:/bin".
   </DL>
  @@ -407,7 +407,7 @@
   If Apache finds a properly configured suEXEC wrapper, it will print
   the following message to the error log:
   <PRE>
  -    [notice] suEXEC mechanism enabled (wrapper: <I>/path/to/suexec</I>)
  +    [notice] suEXEC mechanism enabled (wrapper: <EM>/path/to/suexec</EM>)
   </PRE>
   If you don't see this message at server startup, the server is most
   likely not finding the wrapper program where it expects it, or the
  
  
  
  1.2       +1 -1      apache-1.3/htdocs/manual/suexec_1_2.html
  
  Index: suexec_1_2.html
  ===================================================================
  RCS file: /home/cvs/apache-1.3/htdocs/manual/suexec_1_2.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- suexec_1_2.html	1998/11/12 20:13:08	1.1
  +++ suexec_1_2.html	1999/01/08 23:13:27	1.2
  @@ -172,7 +172,7 @@
   If you use Apache 1.3 the following message is printed to the
   error log:
   <PRE>
  -    [notice] suEXEC mechanism enabled (wrapper: <I>/path/to/suexec</I>)
  +    [notice] suEXEC mechanism enabled (wrapper: <EM>/path/to/suexec</EM>)
   </PRE>
   </P>
   <P ALIGN="LEFT">
  
  
  
  1.31      +1 -1      apache-1.3/htdocs/manual/mod/mod_mime.html
  
  Index: mod_mime.html
  ===================================================================
  RCS file: /home/cvs/apache-1.3/htdocs/manual/mod/mod_mime.html,v
  retrieving revision 1.30
  retrieving revision 1.31
  diff -u -r1.30 -r1.31
  --- mod_mime.html	1999/01/08 22:37:03	1.30
  +++ mod_mime.html	1999/01/08 23:13:29	1.31
  @@ -51,7 +51,7 @@
   <H2><A NAME="multipleext">Files with Multiple Extensions</A></H2>
   
   Files can have more than one extension, and the order of the
  -extensions is <i>normally</i> irrelevant. For example, if the file
  +extensions is <EM>normally</EM> irrelevant. For example, if the file
   <CODE>welcome.html.fr</CODE> maps onto content type text/html and
   language French then the file <CODE>welcome.fr.html</CODE> will map
   onto exactly the same information. The only exception to this is if an
  
  
  

Mime
View raw message