httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@hyperreal.org
Subject cvs commit: apache-devsite 404.html API.html binaries.html bug_track.html guidelines.html home.html how-to-release.html index.html members.html ports.html styleguide.html todo.html voting.html
Date Thu, 12 Feb 1998 14:39:27 GMT
coar        98/02/12 06:39:27

  Modified:    .        404.html API.html binaries.html bug_track.html
                        guidelines.html home.html how-to-release.html
                        index.html members.html ports.html styleguide.html
                        todo.html voting.html
  Log:
  	Applying the HTML cleanup to the dev.apache.org files..
  
  Revision  Changes    Path
  1.2       +8 -8      apache-devsite/404.html
  
  Index: 404.html
  ===================================================================
  RCS file: /export/home/cvs/apache-devsite/404.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- 404.html	1997/06/17 10:43:26	1.1
  +++ 404.html	1998/02/12 14:39:18	1.2
  @@ -12,7 +12,7 @@
   
   <OL>
   
  -<LI><B>You attempted to access a URL that is not valid here.</B>
  +<LI><STRONG>You attempted to access a URL that is not valid here.</STRONG>
   Double-check the URL for typos.  Perhaps the correct URL has changed from
   what it used to be, or perhaps whoever referred you to this URL got it
   wrong.  Try going to the <A HREF="http://hyperreal.org/">Hyperreal home 
  @@ -20,12 +20,12 @@
   
   <BR><BR>
   
  -<LI><B>You were attempting to access a URL through a non-standard port,
  +<LI><STRONG>You were attempting to access a URL through a non-standard port,
   but your network access provider is running a firewall or proxy cache
  -server that is stripping the port number from the URL.</b> For example,
  +server that is stripping the port number from the URL.</STRONG> For example,
   you may have tried to access :2000 but the firewall or cache is submitting
   the URL without the port number.  If you were attempting to access an http
  -URL via :70, <em>USE PORT 2000 INSTEAD</em>.  If you were attempting to
  +URL via :70, <EM>USE PORT 2000 INSTEAD</EM>.  If you were attempting to
   access port 2000 and received this message, it is definitely a proxy cache
   server or firewall problem, and you should consult with your network
   access provider. 
  @@ -33,10 +33,10 @@
   <!--#if expr="!\"$HTTP_HOST\"" -->
   
   <BR><BR>
  -<LI><B>Your browser does not support the Host: header - thus you may
  +<LI><STRONG>Your browser does not support the Host: header - thus you may
   have been trying to access a page which exists on one of Hyperreal's
   web sites but not another, and the server couldn't tell which one you
  -wanted</B>.  You can follow the links below to get to the content from
  +wanted</STRONG>.  You can follow the links below to get to the content from
   their respective home pages, but we recommend you upgrade your browser.
   
   <!--#include virtual="/home/vhosts.html" -->
  @@ -46,11 +46,11 @@
   </OL>
   
   <P>
  -A <A HREF="http://www.hyperreal.org/map.html">Brief Map/Index of This Site</a> is available.
  +A <A HREF="http://www.hyperreal.org/map.html">Brief Map/Index of This Site</A> is available.
   </P>
   
   <P>
  -Good Luck!   <I>--The Hyperreal Staff</I>
  +Good Luck!   <EM>--The Hyperreal Staff</EM>
   </P>
   
   </BODY>
  
  
  
  1.2       +250 -250  apache-devsite/API.html
  
  Index: API.html
  ===================================================================
  RCS file: /export/home/cvs/apache-devsite/API.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- API.html	1997/06/17 10:43:26	1.1
  +++ API.html	1998/02/12 14:39:19	1.2
  @@ -1,9 +1,9 @@
  -<title>Shambhala API notes</title>
  -<h1>Shambhala API notes</h1>
  +<TITLE>Shambhala API notes</TITLE>
  +<H1>Shambhala API notes</H1>
   
   These are some notes on the Shambhala API and the data structures you
   have to deal with, etc.  They are not yet nearly complete, but
  -hopefully, they will help you get your bearings.<p>
  +hopefully, they will help you get your bearings.<P>
   
   A few notes on general pedagogical style here.  In the interest of
   conciseness, all structure declarations here are incomplete --- the
  @@ -11,77 +11,77 @@
   most part, these are reserved to one component of the server core or
   another, and should be altered by modules with caution.  However, in
   some cases, they really are things I just haven't gotten around to
  -yet.  Welcome to the bleeding edge.<p>
  +yet.  Welcome to the bleeding edge.<P>
   
   Finally, here's an outline, to give you some bare idea of what's
   coming up, and in what order:
   
  -<ul>
  -  <li> <a href="#basics">Basic concepts.</a>
  -       <ul>
  -	 <li> <a href="#HMR">Handlers, Modules, and Requests</a>
  -	 <li> <a href="#moduletour">A brief tour of a module</a>
  -       </ul>
  -  <li> <a href="#handlers">How handlers work</a>
  -       <ul>
  -	 <li> <a href="#req_tour">A brief tour of the <code>request_rec</code></a>
  -	 <li> <a href="#req_orig">Where request_rec structures come from</a>
  -	 <li> <a href="#req_return">Handling requests, declining, and returning error codes</a>
  -	 <li> <a href="#resp_handlers">Special considerations for response handlers</a>
  -	 <li> <a href="#auth_handlers">Special considerations for authentication handlers</a>
  -	 <li> <a href="#log_handlers">Special considerations for logging handlers</a>
  -       </ul>
  -  <li> <a href="#pools">Resource allocation and resource pools</a>
  -  <li> <a href="#config">Configuration, commands and the like</a>
  -       <ul>
  -	 <li> <a href="#per-dir">Per-directory configuration structures</a>
  -	 <li> <a href="#commands">Command handling</a>
  -	 <li> <a href="#servconf">Side notes --- per-server configuration, virtual servers, etc.</a>
  -       </ul>
  -</ul>
  +<UL>
  +  <LI> <A HREF="#basics">Basic concepts.</A>
  +       <UL>
  +	 <LI> <A HREF="#HMR">Handlers, Modules, and Requests</A>
  +	 <LI> <A HREF="#moduletour">A brief tour of a module</A>
  +       </UL>
  +  <LI> <A HREF="#handlers">How handlers work</A>
  +       <UL>
  +	 <LI> <A HREF="#req_tour">A brief tour of the <CODE>request_rec</CODE></A>
  +	 <LI> <A HREF="#req_orig">Where request_rec structures come from</A>
  +	 <LI> <A HREF="#req_return">Handling requests, declining, and returning error codes</A>
  +	 <LI> <A HREF="#resp_handlers">Special considerations for response handlers</A>
  +	 <LI> <A HREF="#auth_handlers">Special considerations for authentication handlers</A>
  +	 <LI> <A HREF="#log_handlers">Special considerations for logging handlers</A>
  +       </UL>
  +  <LI> <A HREF="#pools">Resource allocation and resource pools</A>
  +  <LI> <A HREF="#config">Configuration, commands and the like</A>
  +       <UL>
  +	 <LI> <A HREF="#per-dir">Per-directory configuration structures</A>
  +	 <LI> <A HREF="#commands">Command handling</A>
  +	 <LI> <A HREF="#servconf">Side notes --- per-server configuration, virtual servers, etc.</A>
  +       </UL>
  +</UL>
   
  -<h2><a name="basics">Basic concepts.</a></h2>
  +<H2><A NAME="basics">Basic concepts.</A></H2>
   
   We begin with an overview of the basic concepts behind the Shambhala
   API, and how they are manifested in the code.
   
  -<h3><a name="HMR">Handlers, Modules, and Requests</a></h3>
  +<H3><A NAME="HMR">Handlers, Modules, and Requests</A></H3>
   
   Shambhala breaks down request handling into a series of steps, more or
   less the same way the Netscape Server API does (although Shambhala has
   a few more stages than NetSite does, as hooks for stuff I thought
   might be useful in the future).  These are:
   
  -<ul>
  -  <li> URI -&gt; Filename translation
  -  <li> Auth ID checking [is the user who they say they are?]
  -  <li> Auth access checking [is the user authorized <em>here</em>?]
  -  <li> Access checking other than auth
  -  <li> Determining MIME type of the object requested
  -  <li> "Fixups" --- there aren't any of these yet, but the phase is
  +<UL>
  +  <LI> URI -&gt; Filename translation
  +  <LI> Auth ID checking [is the user who they say they are?]
  +  <LI> Auth access checking [is the user authorized <EM>here</EM>?]
  +  <LI> Access checking other than auth
  +  <LI> Determining MIME type of the object requested
  +  <LI> "Fixups" --- there aren't any of these yet, but the phase is
          intended as a hook for possible extensions like
  -       <code>SetEnv</code>, which don't really fit well elsewhere.
  -  <li> Actually sending a response back to the client.  
  -  <li> Logging the request
  -</ul>
  +       <CODE>SetEnv</CODE>, which don't really fit well elsewhere.
  +  <LI> Actually sending a response back to the client.  
  +  <LI> Logging the request
  +</UL>
   
   These phases are handled by looking at each of a succession of
  -<em>modules</em>, looking to see if each of them has a handler for the
  +<EM>modules</EM>, looking to see if each of them has a handler for the
   phase, and attempting invoking it if so.  The handler can typically do
   one of three things:
   
  -<ul>
  -  <li> <em>Handle</em> the request, and indicate that it has done so
  -       by returning the magic constant <code>OK</code>.  
  -  <li> <em>Decline</em> to handle the request, by returning the magic
  -       integer constant <code>DECLINED</code>.  In this case, the
  +<UL>
  +  <LI> <EM>Handle</EM> the request, and indicate that it has done so
  +       by returning the magic constant <CODE>OK</CODE>.  
  +  <LI> <EM>Decline</EM> to handle the request, by returning the magic
  +       integer constant <CODE>DECLINED</CODE>.  In this case, the
          server behaves in all respects as if the handler simply hadn't
          been there.
  -  <li> Signal an error, by returning one of the HTTP error codes.
  +  <LI> Signal an error, by returning one of the HTTP error codes.
          This terminates normal handling of the request, although an
          ErrorDocument may be invoked to try to mop up, and it will be
          logged in any case.
  -</ul>
  +</UL>
   
   Most phases are terminated by the first module that handles them;
   however, for logging, "fixups", and non-access authentication
  @@ -89,47 +89,47 @@
   response phase is unique in that modules may declare multiple handlers
   for it, via a dispatch table keyed on the MIME type of the requested
   object.  Modules may declare a response-phase handler which can handle
  -<em>any</em> request, by giving it the key <code>*/*</code> (i.e., a
  +<EM>any</EM> request, by giving it the key <CODE>*/*</CODE> (i.e., a
   wildcard MIME type specification).  However, wildcard handlers are
   only invoked if the server has already tried and failed to find a more
   specific response handler for the MIME type of the requested object
  -(either none existed, or they all declined).<p>
  +(either none existed, or they all declined).<P>
   
   The handlers themselves are functions of one argument (a
  -<code>request_rec</code> structure. vide infra), which returns an
  -integer, as above.<p>
  +<CODE>request_rec</CODE> structure. vide infra), which returns an
  +integer, as above.<P>
   
  -<h3><a name="moduletour">A brief tour of a module</a></h3>
  +<H3><A NAME="moduletour">A brief tour of a module</A></H3>
   
   At this point, we need to explain the structure of a module.  Our
   candidate will be one of the messier ones, the CGI module --- this
  -handles both CGI scripts and the <code>ScriptAlias</code> config file
  +handles both CGI scripts and the <CODE>ScriptAlias</CODE> config file
   command.  It's actually a great deal more complicated than most
   modules, but if we're going to have only one example, it might as well
  -be the one with its fingers in everyplace.<p>
  +be the one with its fingers in everyplace.<P>
   
   Let's begin with handlers.  In order to handle the CGI scripts, the
   module declares a response handler for them. Because of
  -<code>ScriptAlias</code>, it also has handlers for the name
  -translation phase (to recognise <code>ScriptAlias</code>ed URI's), the
  -type-checking phase (any <code>ScriptAlias</code>ed request is typed
  -as a CGI script).<p>
  +<CODE>ScriptAlias</CODE>, it also has handlers for the name
  +translation phase (to recognise <CODE>ScriptAlias</CODE>ed URI's), the
  +type-checking phase (any <CODE>ScriptAlias</CODE>ed request is typed
  +as a CGI script).<P>
   
   The module needs to maintain some per (virtual)
  -server information, namely, the <code>ScriptAlias</code>es in effect;
  +server information, namely, the <CODE>ScriptAlias</CODE>es in effect;
   the module structure therefore contains pointers to a functions which
   builds these structures, and to another which combines two of them (in
   case the main server and a virtual server both have
  -<code>ScriptAlias</code>es declared).<p>
  +<CODE>ScriptAlias</CODE>es declared).<P>
   
   Finally, this module contains code to handle the
  -<code>ScriptAlias</code> command itself.  This particular module only
  +<CODE>ScriptAlias</CODE> command itself.  This particular module only
   declares one command, but there could be more, so modules have
  -<em>command tables</em> which declare their commands, and describe
  -where they are permitted, and how they are to be invoked.  <p>
  +<EM>command tables</EM> which declare their commands, and describe
  +where they are permitted, and how they are to be invoked.  <P>
   
   A final note on the declared types of the arguments of some of these
  -commands: a <code>pool</code> is a pointer to a <em>resource pool</em>
  +commands: a <CODE>pool</CODE> is a pointer to a <EM>resource pool</EM>
   structure; these are used by the server to keep track of the memory
   which has been allocated, files opened, etc., either to service a
   particular request, or to handle the process of configuring itself.
  @@ -137,14 +137,14 @@
   when the server is restarting), the memory can be freed, and the files
   closed, en masse, without anyone having to write explicit code to
   track them all down and dispose of them.  Also, a
  -<code>cmd_parms</code> structure contains various information about
  +<CODE>cmd_parms</CODE> structure contains various information about
   the config file being read, and other status information, which is
   sometimes of use to the function which processes a config-file command
  -(such as <code>ScriptAlias</code>).
  +(such as <CODE>ScriptAlias</CODE>).
   
   With no further ado, the module itself:
    
  -<pre>
  +<PRE>
   /* Declarations of handlers. */
   
   int translate_scriptalias (request_rec *);
  @@ -194,50 +194,50 @@
      NULL,			/* fixups */
      NULL				/* logger */
   };
  -</pre>
  +</PRE>
   
  -<h2><a name="handlers">How handlers work</a></h2>
  +<H2><A NAME="handlers">How handlers work</A></H2>
   
  -The sole argument to handlers is a <code>request_rec</code> structure.
  +The sole argument to handlers is a <CODE>request_rec</CODE> structure.
   This structure describes a particular request which has been made to
   the server, on behalf of a client.  In most cases, each connection to
  -the client generates only one <code>request_rec</code> structure.<p>
  +the client generates only one <CODE>request_rec</CODE> structure.<P>
   
  -<h3><a name="req_tour">A brief tour of the <code>request_rec</code></a></h3>
  +<H3><A NAME="req_tour">A brief tour of the <CODE>request_rec</CODE></A></H3>
   
  -The <code>request_rec</code> contains pointers to a resource pool
  +The <CODE>request_rec</CODE> contains pointers to a resource pool
   which will be cleared when the server is finished handling the
   request; to structures containing per-server and per-connection
  -information, and most importantly, information on the request itself.<p>
  +information, and most importantly, information on the request itself.<P>
   
   The most important such information is a small set of character
   strings describing attributes of the object being requested, including
   its URI, filename, content-type and content-encoding (these being filled
   in by the translation and type-check handlers which handle the
  -request, respectively). <p>
  +request, respectively). <P>
   
   Other commonly used data items are tables giving the MIME headers on
   the client's original request, MIME headers to be sent back with the
   ppppresponse (which modules can add to at will), and environment variables
   for any subprocesses which are spawned off in the course of servicing
   the request.  These tables are manipulated using the
  -<code>table_get</code> and <code>table_set</code> routines. <p>
  +<CODE>table_get</CODE> and <CODE>table_set</CODE> routines. <P>
   
   Finally, there are pointers to two data structures which, in turn,
   point to per-module configuration structures.  Specifically, these
   hold pointers to the data structures which the module has built to
   describe the way it has been configured to operate in a given
  -directory (via <code>.htaccess</code> files or
  -<code>&lt;Directory&gt;</code> sections), for private data it has
  +directory (via <CODE>.htaccess</CODE> files or
  +<CODE>&lt;Directory&gt;</CODE> sections), for private data it has
   built in the course of servicing the request (so modules' handlers for
   one phase can pass "notes" to their handlers for other phases).  There
  -is another such configuration vector in the <code>server_rec</code>
  -data structure pointed to by the <code>request_rec</code>, which
  -contains per (virtual) server configuration data.<p>
  +is another such configuration vector in the <CODE>server_rec</CODE>
  +data structure pointed to by the <CODE>request_rec</CODE>, which
  +contains per (virtual) server configuration data.<P>
   
  -Here is an abridged declaration, giving the fields most commonly used:<p>
  +Here is an abridged declaration, giving the fields most commonly used:<P>
   
  -<pre>
  +<PRE>
   struct request_rec {
   
     pool *pool;
  @@ -298,103 +298,103 @@
     
   };
   
  -</pre>
  +</PRE>
   
  -<h3><a name="req_orig">Where request_rec structures come from</a></h3>
  +<H3><A NAME="req_orig">Where request_rec structures come from</A></H3>
   
  -Most <code>request_rec</code> structures are built by reading an HTTP
  +Most <CODE>request_rec</CODE> structures are built by reading an HTTP
   request from a client, and filling in the fields.  However, there are
   a few exceptions:
   
  -<ul>
  -  <li> If the request is to an imagemap, a type map (i.e., a
  -       <code>*.var</code> file), or a CGI script which returned a
  +<UL>
  +  <LI> If the request is to an imagemap, a type map (i.e., a
  +       <CODE>*.var</CODE> file), or a CGI script which returned a
          local "Location:", then the resource which the user requested
          is going to be ultimately located by some URI other than what
          the client originally supplied.  In this case, the server does
  -       an <em>internal redirect</em>, constructing a new
  -       <code>request_rec</code> for the new URI, and processing it
  +       an <EM>internal redirect</EM>, constructing a new
  +       <CODE>request_rec</CODE> for the new URI, and processing it
          almost exactly as if the client had requested the new URI
  -       directly. <p>
  +       directly. <P>
   
  -  <li> If some handler signaled an error, and an
  -       <code>ErrorDocument</code> is in scope, the same internal
  -       redirect machinery comes into play.<p>
  +  <LI> If some handler signaled an error, and an
  +       <CODE>ErrorDocument</CODE> is in scope, the same internal
  +       redirect machinery comes into play.<P>
   
  -  <li> Finally, a handler occasionally needs to investigate "what
  +  <LI> Finally, a handler occasionally needs to investigate "what
          would happen if" some other request were run.  For instance,
          the directory indexing module needs to know what MIME type
          would be assigned to a request for each directory entry, in
  -       order to figure out what icon to use.<p>
  +       order to figure out what icon to use.<P>
   
  -       Such handlers can construct a <em>sub-request</em>, using the
  -       functions <code>sub_req_lookup_file</code> and
  -       <code>sub_req_lookup_uri</code>; this constructs a new
  -       <code>request_rec</code> structure and processes it as you
  +       Such handlers can construct a <EM>sub-request</EM>, using the
  +       functions <CODE>sub_req_lookup_file</CODE> and
  +       <CODE>sub_req_lookup_uri</CODE>; this constructs a new
  +       <CODE>request_rec</CODE> structure and processes it as you
          would expect, up to but not including the point of actually
          sending a response.  (These functions skip over the access
          checks if the sub-request is for a file in the same directory
  -       as the original request).<p>
  +       as the original request).<P>
   
          (Server-side includes work by building sub-requests and then
          actually invoking the response handler for them, via the
  -       function <code>run_sub_request</code>).
  -</ul>
  +       function <CODE>run_sub_request</CODE>).
  +</UL>
   
  -<h3><a name="req_return">Handling requests, declining, and returning error codes</a></h3>
  +<H3><A NAME="req_return">Handling requests, declining, and returning error codes</A></H3>
   
   As discussed above, each handler, when invoked to handle a particular
  -<code>request_rec</code>, has to return an <code>int</code> to
  +<CODE>request_rec</CODE>, has to return an <CODE>int</CODE> to
   indicate what happened.  That can either be
   
  -<ul>
  -  <li> OK --- the request was handled successfully.  This may or may
  +<UL>
  +  <LI> OK --- the request was handled successfully.  This may or may
          not terminate the phase.
  -  <li> DECLINED --- no erroneous condition exists, but the module
  +  <LI> DECLINED --- no erroneous condition exists, but the module
          declines to handle the phase; the server tries to find another.
  -  <li> an HTTP error code, which aborts handling of the request.
  -</ul>
  +  <LI> an HTTP error code, which aborts handling of the request.
  +</UL>
   
  -Note that if the error code returned is <code>REDIRECT</code>, then
  -the module should put a <code>Location</code> in the request's
  -<code>headers_out</code>, to indicate where the client should be
  -redirected <em>to</em>. <p>
  +Note that if the error code returned is <CODE>REDIRECT</CODE>, then
  +the module should put a <CODE>Location</CODE> in the request's
  +<CODE>headers_out</CODE>, to indicate where the client should be
  +redirected <EM>to</EM>. <P>
   
  -<h3><a name="resp_handlers">Special considerations for response handlers</a></h3>
  +<H3><A NAME="resp_handlers">Special considerations for response handlers</A></H3>
   
   Handlers for most phases do their work by simply setting a few fields
  -in the <code>request_rec</code> structure (or, in the case of access
  +in the <CODE>request_rec</CODE> structure (or, in the case of access
   checkers, simply by returning the correct error code).  However,
  -response handlers have to actually send a request back to the client. <p>
  +response handlers have to actually send a request back to the client. <P>
   
   They should begin by sending an HTTP response header, using the
  -function <code>send_http_header</code>.  (You don't have to do
  +function <CODE>send_http_header</CODE>.  (You don't have to do
   anything special to skip sending the header for HTTP/0.9 requests; the
   function figures out on its own that it shouldn't do anything).  If
  -the request is marked <code>header_only</code>, that's all they should
  +the request is marked <CODE>header_only</CODE>, that's all they should
   do; they should return after that, without attempting any further
  -output.  <p>
  +output.  <P>
   
   Otherwise, they should produce a request body which responds to the
  -client as appropriate.  The primitives for this are <code>rputc</code>
  -and <code>rprintf</code>, for internally generated output, and
  -<code>send_fd</code>, to copy the contents of some <code>FILE *</code>
  -straight to the client.  <p>
  +client as appropriate.  The primitives for this are <CODE>rputc</CODE>
  +and <CODE>rprintf</CODE>, for internally generated output, and
  +<CODE>send_fd</CODE>, to copy the contents of some <CODE>FILE *</CODE>
  +straight to the client.  <P>
   
   One final consideration: when doing I/O to the client, there is the
   possibility of indefinite delays.  It is therefore important to arm a
  -timeout before initiating I/O to the client.<p>
  +timeout before initiating I/O to the client.<P>
   
   At this point, you should more or less understand the following piece
  -of code, which is the handler which handles <code>GET</code> requests
  +of code, which is the handler which handles <CODE>GET</CODE> requests
   which have no more specific handler; it also shows how conditional
  -<code>GET</code>s can be handled, if it's desirable to do so in a
  -particular response handler.  (The functions <code>pfopen</code> and
  -<code>pfclose</code> tie the <code>FILE *</code> returned into the
  +<CODE>GET</CODE>s can be handled, if it's desirable to do so in a
  +particular response handler.  (The functions <CODE>pfopen</CODE> and
  +<CODE>pfclose</CODE> tie the <CODE>FILE *</CODE> returned into the
   resource pool machinery, so it will be closed even if the request is
  -aborted).<p>
  +aborted).<P>
   
  -<pre>
  +<PRE>
   int default_handler (request_rec *r)
   {
       int errstatus;
  @@ -425,51 +425,51 @@
       pfclose (r-&gt;pool, f);
       return OK;
   }
  -</pre>
  +</PRE>
   
   Finally, if all of this is too much of a challenge, there are a few
   ways out of it.  First off, as shown above, a response handler which
   has not yet produced any output can simply return an error code, in
   which case the server will automatically produce an error response.
   Secondly, it can punt to some other handler by invoking
  -<code>internal_redirect</code>, which is how the internal redirection
  +<CODE>internal_redirect</CODE>, which is how the internal redirection
   machinery discussed above is invoked.  A response handler which has
  -internally redirected should always return <code>OK</code>. <p>
  +internally redirected should always return <CODE>OK</CODE>. <P>
   
  -(Invoking <code>internal_redirect</code> from handlers which are
  -<em>not</em> response handlers will lead to serious confusion).
  +(Invoking <CODE>internal_redirect</CODE> from handlers which are
  +<EM>not</EM> response handlers will lead to serious confusion).
   
  -<h3><a name="auth_handlers">Special considerations for authentication handlers</a></h3>
  +<H3><A NAME="auth_handlers">Special considerations for authentication handlers</A></H3>
   
   Stuff that should be discussed here in detail:
   
  -<ul>
  -  <li> Authentication-phase handlers not invoked unless auth is
  +<UL>
  +  <LI> Authentication-phase handlers not invoked unless auth is
          configured for the directory.
  -  <li> Common auth configuration stored in the core per-dir
  -       configuration; it has accessors <code>auth_type</code>,
  -       <code>auth_name</code>, and <code>requires</code>.
  -  <li> Common routines, to handle the protocol end of things, at least
  -       for HTTP basic authentication (<code>get_basic_auth_pw</code>,
  -       which sets the <code>connection-&gt;user</code> structure field
  -       automatically, and <code>note_basic_auth_failure</code>, which
  -       arranges for the proper <code>WWW-Authenticate:</code> header
  +  <LI> Common auth configuration stored in the core per-dir
  +       configuration; it has accessors <CODE>auth_type</CODE>,
  +       <CODE>auth_name</CODE>, and <CODE>requires</CODE>.
  +  <LI> Common routines, to handle the protocol end of things, at least
  +       for HTTP basic authentication (<CODE>get_basic_auth_pw</CODE>,
  +       which sets the <CODE>connection-&gt;user</CODE> structure field
  +       automatically, and <CODE>note_basic_auth_failure</CODE>, which
  +       arranges for the proper <CODE>WWW-Authenticate:</CODE> header
          to be sent back).
  -</ul>
  +</UL>
   
  -<h3><a name="log_handlers">Special considerations for logging handlers</a></h3>
  +<H3><A NAME="log_handlers">Special considerations for logging handlers</A></H3>
   
   When a request has internally redirected, there is the question of
   what to log.  Shambhala handles this by bundling the entire chain of
  -redirects into a list of <code>request_rec</code> structures which are
  -threaded through the <code>r-&gt;prev</code> and <code>r-&gt;next</code>
  -pointers.  The <code>request_rec</code> which is passed to the logging
  +redirects into a list of <CODE>request_rec</CODE> structures which are
  +threaded through the <CODE>r-&gt;prev</CODE> and <CODE>r-&gt;next</CODE>
  +pointers.  The <CODE>request_rec</CODE> which is passed to the logging
   handlers in such cases is the one which was originally built for the
   intial request from the client; note that the bytes_sent field will
   only be correct in the last request in the chain (the one for which a
   response was actually sent). 
   
  -<h2><a name="pools">Resource allocation and resource pools</a></h2>
  +<H2><A NAME="pools">Resource allocation and resource pools</A></H2>
   
   One of the problems of writing and designing a server-pool server is
   that of preventing leakage, that is, allocating resources (memory,
  @@ -477,14 +477,14 @@
   pool machinery is designed to prevent this.  Stuff that should be
   discussed here in detail:
   
  -<ul>
  -  <li> Allocating memory --- <code>palloc</code> and friends
  -  <li> The array and table stuff
  -  <li> Files and file descriptors
  -  <li> sub-pools and <code>destroy_sub_request</code>
  -</ul>
  +<UL>
  +  <LI> Allocating memory --- <CODE>palloc</CODE> and friends
  +  <LI> The array and table stuff
  +  <LI> Files and file descriptors
  +  <LI> sub-pools and <CODE>destroy_sub_request</CODE>
  +</UL>
   
  -<h2><a name="config">Configuration, commands and the like</a></h2>
  +<H2><A NAME="config">Configuration, commands and the like</A></H2>
   
   One of the design goals for this server was to maintain external
   compatibility with the NCSA 1.3 server --- that is, to read the same
  @@ -494,7 +494,7 @@
   functionality into modules which have as little as possible to do with
   the monolithic server core.  The only way to reconcile these goals is
   to move the handling of most commands from the central server into the
  -modules.  <p>
  +modules.  <P>
   
   However, just giving the modules command tables is not enough to
   divorce them completely from the server core.  The server has to
  @@ -503,77 +503,77 @@
   either per-server, or per-directory.  Most things are per-directory,
   including in particular access control and authorization information,
   but also information on how to determine file types from suffixes,
  -which can be modified by <code>AddType</code> and
  -<code>DefaultType</code> directives, and so forth.  In general, the
  -governing philosophy is that anything which <em>can</em> be made
  +which can be modified by <CODE>AddType</CODE> and
  +<CODE>DefaultType</CODE> directives, and so forth.  In general, the
  +governing philosophy is that anything which <EM>can</EM> be made
   configurable by directory should be; per-server information is
   generally used in the standard set of modules for information like
  -<code>Alias</code>es and <code>Redirect</code>s which come into play
  +<CODE>Alias</CODE>es and <CODE>Redirect</CODE>s which come into play
   before the request is tied to a particular place in the underlying
  -file system. <p>
  +file system. <P>
   
   Another requirement for emulating the NCSA server is being able to
   handle the per-directory configuration files, generally called
  -<code>.htaccess</code> files, though even in the NCSA server they can
  +<CODE>.htaccess</CODE> files, though even in the NCSA server they can
   contain directives which have nothing at all to do with access
   control.  Accordingly, after URI -&gt; filename translation, but before
   performing any other phase, the server walks down the directory
   hierarchy of the underlying filesystem, following the translated
  -pathname, to read any <code>.htaccess</code> files which might be
  +pathname, to read any <CODE>.htaccess</CODE> files which might be
   present.  The information which is read in then has to be
  -<em>merged</em> with the applicable information from the server's own
  -config files (either from the <code>&lt;Directory&gt;</code> sections
  -in <code>access.conf</code>, or from defaults in
  -<code>srm.conf</code>, which actually behaves for most purposes almost
  -exactly like <code>&lt;Directory /&gt;</code>).<p>
  +<EM>merged</EM> with the applicable information from the server's own
  +config files (either from the <CODE>&lt;Directory&gt;</CODE> sections
  +in <CODE>access.conf</CODE>, or from defaults in
  +<CODE>srm.conf</CODE>, which actually behaves for most purposes almost
  +exactly like <CODE>&lt;Directory /&gt;</CODE>).<P>
   
   Finally, after having served a request which involved reading
  -<code>.htaccess</code> files, we need to discard the storage allocated
  +<CODE>.htaccess</CODE> files, we need to discard the storage allocated
   for handling them.  That is solved the same way it is solved wherever
   else similar problems come up, by tying those structures to the
  -per-transaction resource pool.  <p>
  +per-transaction resource pool.  <P>
   
  -<h3><a name="per-dir">Per-directory configuration structures</a></h3>
  +<H3><A NAME="per-dir">Per-directory configuration structures</A></H3>
   
  -Let's look out how all of this plays out in <code>mod_mime.c</code>,
  +Let's look out how all of this plays out in <CODE>mod_mime.c</CODE>,
   which defines the file typing handler which emulates the NCSA server's
   behavior of determining file types from suffixes.  What we'll be
   looking at, here, is the code which implements the
  -<code>AddType</code> and <code>AddEncoding</code> commands.  These
  -commands can appear in <code>.htaccess</code> files, so they must be
  +<CODE>AddType</CODE> and <CODE>AddEncoding</CODE> commands.  These
  +commands can appear in <CODE>.htaccess</CODE> files, so they must be
   handled in the module's private per-directory data, which in fact,
  -consists of two separate <code>table</code>s for MIME types and
  +consists of two separate <CODE>table</CODE>s for MIME types and
   encoding information, and is declared as follows:
   
  -<pre>
  +<PRE>
   typedef struct {
       table *forced_types;	/* Additional AddTyped stuff */
       table *encoding_types;	/* Added with AddEncoding... */
   } mime_dir_config;
  -</pre>
  +</PRE>
   
   When the server is reading a configuration file, or
  -<code>&lt;Directory&gt;</code> section, which includes one of the MIME
  -module's commands, it needs to create a <code>mime_dir_config</code>
  +<CODE>&lt;Directory&gt;</CODE> section, which includes one of the MIME
  +module's commands, it needs to create a <CODE>mime_dir_config</CODE>
   structure, so those commands have something to act on.  It does this
   by invoking the function it finds in the module's "create per-dir
   config slot", with two arguments: the name of the directory to which
  -this configuration information applies (or <code>NULL</code> for
  -<code>srm.conf</code>), and a pointer to a resource pool in which the
  -allocation should happen. <p>
  +this configuration information applies (or <CODE>NULL</CODE> for
  +<CODE>srm.conf</CODE>), and a pointer to a resource pool in which the
  +allocation should happen. <P>
   
  -(If we are reading a <code>.htaccess</code> file, that resource pool
  +(If we are reading a <CODE>.htaccess</CODE> file, that resource pool
   is the per-request resource pool for the request; otherwise it is a
   resource pool which is used for configuration data, and cleared on
   restarts.  Either way, it is important for the structure being created
   to vanish when the pool is cleared, by registering a cleanup on the
  -pool if necessary). <p>
  +pool if necessary). <P>
   
   For the MIME module, the per-dir config creation function just
  -<code>palloc</code>s the structure above, and a creates a couple of
  -<code>table</code>s to fill it.  That looks like this:
  +<CODE>palloc</CODE>s the structure above, and a creates a couple of
  +<CODE>table</CODE>s to fill it.  That looks like this:
   
  -<pre>
  +<PRE>
   void *create_mime_dir_config (pool *p, char *dummy)
   {
       mime_dir_config *new =
  @@ -584,15 +584,15 @@
       
       return new;
   }
  -</pre>
  +</PRE>
   
  -Now, suppose we've just read in a <code>.htaccess</code> file.  We
  +Now, suppose we've just read in a <CODE>.htaccess</CODE> file.  We
   already have the per-directory configuration structure for the next
  -directory up in the hierarchy.  If the <code>.htaccess</code> file we
  -just read in didn't have any <code>AddType</code> or
  -<code>AddEncoding</code> commands, its per-directory config structure
  +directory up in the hierarchy.  If the <CODE>.htaccess</CODE> file we
  +just read in didn't have any <CODE>AddType</CODE> or
  +<CODE>AddEncoding</CODE> commands, its per-directory config structure
   for the MIME module is still valid, and we can just use it.
  -Otherwise, we need to merge the two structures somehow. <p>
  +Otherwise, we need to merge the two structures somehow. <P>
   
   To do that, the server invokes the module's per-directory config merge
   function, if one is present.  That function takes three arguments:
  @@ -601,7 +601,7 @@
   is overlay the tables from the new per-directory config structure with
   those from the parent:
   
  -<pre>
  +<PRE>
   void *merge_mime_dir_configs (pool *p, void *parent_dirv, void *subdirv)
   {
       mime_dir_config *parent_dir = (mime_dir_config *)parent_dirv;
  @@ -616,63 +616,63 @@
   
       return new;
   }
  -</pre>
  +</PRE>
   
   As a note --- if there is no per-directory merge function present, the
   server will just use the subdirectory's configuration info, and ignore
   the parent's.  For some modules, that works just fine (e.g., for the
   includes module, whose per-directory configuration information
  -consists solely of the state of the <code>XBITHACK</code>), and for
  +consists solely of the state of the <CODE>XBITHACK</CODE>), and for
   those modules, you can just not declare one, and leave the
  -corresponding structure slot in the module itself <code>NULL</code>.<p>
  +corresponding structure slot in the module itself <CODE>NULL</CODE>.<P>
   
  -<h3><a name="commands">Command handling</a></h3>
  +<H3><A NAME="commands">Command handling</A></H3>
   
   Now that we have these structures, we need to be able to figure out
   how to fill them.  That involves processing the actual
  -<code>AddType</code> and <code>AddEncoding</code> commands.  To find
  -commands, the server looks in the module's <code>command table</code>.
  +<CODE>AddType</CODE> and <CODE>AddEncoding</CODE> commands.  To find
  +commands, the server looks in the module's <CODE>command table</CODE>.
   That table contains information on how many arguments the commands
   take, and in what formats, where it is permitted, and so forth.  That
   information is sufficient to allow the server to invoke most
   command-handling functions with preparsed arguments.  Without further
  -ado, let's look at the <code>AddType</code> command handler, which
  -looks like this (the <code>AddEncoding</code> command looks basically
  +ado, let's look at the <CODE>AddType</CODE> command handler, which
  +looks like this (the <CODE>AddEncoding</CODE> command looks basically
   the same, and won't be shown here):
   
  -<pre>
  +<PRE>
   char *add_type(cmd_parms *cmd, mime_dir_config *m, char *ct, char *ext)
   {
       if (*ext == '.') ++ext;
       table_set (m-&gt;forced_types, ext, ct);
       return NULL;
   }
  -</pre>
  +</PRE>
   
   This command handler is unusually simple.  As you can see, it takes
   four arguments, two of which are preparsed arguments, the third being
   the per-directory configuration structure for the module in question,
  -and the fourth being a pointer to a <code>cmd_parms</code> structure.
  +and the fourth being a pointer to a <CODE>cmd_parms</CODE> structure.
   That structure contains a bunch of arguments which are frequently of
   use to some, but not all, commands, including a resource pool (from
   which memory can be allocated, and to which cleanups should be tied),
   and the (virtual) server being configured, from which the module's
  -per-server configuration data can be obtained if required.<p>
  +per-server configuration data can be obtained if required.<P>
   
   Another way in which this particular command handler is unusually
   simple is that there are no error conditions which it can encounter.
   If there were, it could return an error message instead of
  -<code>NULL</code>; this causes an error to be printed out on the
  -server's <code>stderr</code>, followed by a quick exit, if it is in
  -the main config files; for a <code>.htaccess</code> file, the syntax
  +<CODE>NULL</CODE>; this causes an error to be printed out on the
  +server's <CODE>stderr</CODE>, followed by a quick exit, if it is in
  +the main config files; for a <CODE>.htaccess</CODE> file, the syntax
   error is logged in the server error log (along with an indication of
   where it came from), and the request is bounced with a server error
  -response (HTTP error status, code 500). <p>
  +response (HTTP error status, code 500). <P>
   
   The MIME module's command table has entries for these commands, which
   look like this:
   
  -<pre>
  +<PRE>
   command_rec mime_cmds[] = {
   { "AddType", add_type, NULL, OR_FILEINFO, TAKE2, 
       "a mime type followed by a file extension" },
  @@ -680,54 +680,54 @@
       "an encoding (e.g., gzip), followed by a file extension" },
   { NULL }
   };
  -</pre>
  +</PRE>
   
   The entries in these tables are:
   
  -<ul>
  -  <li> The name of the command
  -  <li> The function which handles it
  -  <li> a <code>(void *)</code> pointer, which is passed in the
  -       <code>cmd_parms</code> structure to the command handler ---
  +<UL>
  +  <LI> The name of the command
  +  <LI> The function which handles it
  +  <LI> a <CODE>(void *)</CODE> pointer, which is passed in the
  +       <CODE>cmd_parms</CODE> structure to the command handler ---
          this is useful in case many similar commands are handled by the
          same function.
  -  <li> A bit mask indicating where the command may appear.  There are
  -       mask bits corresponding to each <code>AllowOverride</code>
  -       option, and an additional mask bit, <code>RSRC_CONF</code>,
  +  <LI> A bit mask indicating where the command may appear.  There are
  +       mask bits corresponding to each <CODE>AllowOverride</CODE>
  +       option, and an additional mask bit, <CODE>RSRC_CONF</CODE>,
          indicating that the command may appear in the server's own
  -       config files, but <em>not</em> in any <code>.htaccess</code>
  +       config files, but <EM>not</EM> in any <CODE>.htaccess</CODE>
          file.
  -  <li> A flag indicating how many arguments the command handler wants
  +  <LI> A flag indicating how many arguments the command handler wants
          preparsed, and how they should be passed in.
  -       <code>TAKE2</code> indicates two preparsed arguments.  Other
  -       options are <code>TAKE1</code>, which indicates one preparsed
  -       argument, <code>FLAG</code>, which indicates that the argument
  -       should be <code>On</code> or <code>Off</code>, and is passed in
  -       as a boolean flag, <code>RAW_ARGS</code>, which causes the
  +       <CODE>TAKE2</CODE> indicates two preparsed arguments.  Other
  +       options are <CODE>TAKE1</CODE>, which indicates one preparsed
  +       argument, <CODE>FLAG</CODE>, which indicates that the argument
  +       should be <CODE>On</CODE> or <CODE>Off</CODE>, and is passed in
  +       as a boolean flag, <CODE>RAW_ARGS</CODE>, which causes the
          server to give the command the raw, unparsed arguments
          (everything but the command name itself).  There is also
  -       <code>ITERATE</code>, which means that the handler looks the
  -       same as <code>TAKE1</code>, but that if multiple arguments are
  +       <CODE>ITERATE</CODE>, which means that the handler looks the
  +       same as <CODE>TAKE1</CODE>, but that if multiple arguments are
          present, it should be called multiple times, and finally
  -       <code>ITERATE2</code>, which indicates that the command handler
  -       looks like a <code>TAKE2</code>, but if more arguments are
  +       <CODE>ITERATE2</CODE>, which indicates that the command handler
  +       looks like a <CODE>TAKE2</CODE>, but if more arguments are
          present, then it should be called multiple times, holding the
          first argument constant.
  -  <li> Finally, we have a string which describes the arguments that
  +  <LI> Finally, we have a string which describes the arguments that
          should be present.  If the arguments in the actual config file
          are not as required, this string will be used to help give a
          more specific error message.  (You can safely leave this
  -       <code>NULL</code>). 
  -</ul>
  +       <CODE>NULL</CODE>). 
  +</UL>
   
   Finally, having set this all up, we have to use it.  This is
   ultimately done in the module's handlers, specifically for its
   file-typing handler, which looks more or less like this; note that the
   per-directory configuration structure is extracted from the
  -<code>request_rec</code>'s per-directory configuration vector by using
  -the <code>get_module_config</code> function.
  +<CODE>request_rec</CODE>'s per-directory configuration vector by using
  +the <CODE>get_module_config</CODE> function.
   
  -<pre>
  +<PRE>
   int find_ct(request_rec *r)
   {
       int i;
  @@ -763,9 +763,9 @@
       return OK;
   }
   
  -</pre>
  +</PRE>
   
  -<h3><a name="servconf">Side notes --- per-server configuration, virtual servers, etc.</a></h3>
  +<H3><A NAME="servconf">Side notes --- per-server configuration, virtual servers, etc.</A></H3>
   
   The basic ideas behind per-server module configuration are basically
   the same as those for per-directory configuration; there is a creation
  @@ -774,17 +774,17 @@
   and a combined structure must be computed.  (As with per-directory
   configuration, the default if no merge function is specified, and a
   module is configured in some virtual server, is that the base
  -configuration is simply ignored). <p>
  +configuration is simply ignored). <P>
   
   The only substantial difference is that when a command needs to
   configure the per-server private module data, it needs to go to the
  -<code>cmd_parms</code> data to get at it.  Here's an example, from the
  +<CODE>cmd_parms</CODE> data to get at it.  Here's an example, from the
   alias module, which also indicates how a syntax error can be returned
   (note that the per-directory configuration argument to the command
   handler is declared as a dummy, since the module doesn't actually have
   per-directory config data):
   
  -<pre>
  +<PRE>
   char *add_redirect(cmd_parms *cmd, void *dummy, char *f, char *url)
   {
       server_rec *s = cmd->server;
  @@ -797,5 +797,5 @@
       new-&gt;fake = f; new-&gt;real = url;
       return NULL;
   }
  -</pre>
  +</PRE>
   
  
  
  
  1.3       +5 -5      apache-devsite/binaries.html
  
  Index: binaries.html
  ===================================================================
  RCS file: /export/home/cvs/apache-devsite/binaries.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- binaries.html	1998/01/07 13:53:44	1.2
  +++ binaries.html	1998/02/12 14:39:19	1.3
  @@ -13,13 +13,13 @@
   <P>
   
   Binaries are to be put in the
  -<code>dist/binaries/(platform)_(version)</code> directory of the
  +<CODE>dist/binaries/(platform)_(version)</CODE> directory of the
   apache web site (as in, dist/binaries/solaris_2.4), with the following
   format for its filename:
   
   <P>
   
  -<code>apache_(version)-(platform)-(OSversion).tar.gz</code>
  +<CODE>apache_(version)-(platform)-(OSversion).tar.gz</CODE>
   
   <P>
   
  @@ -28,15 +28,15 @@
   
   <P>
   
  -<code>httpd-(platform)</code>
  +<CODE>httpd-(platform)</CODE>
   
   <P>
   
  -As in, <code>httpd-solaris</code>.
  +As in, <CODE>httpd-solaris</CODE>.
   
   <P>
   
  -<B>Compiling:</B> Use the "best" compiler for the platform, given that
  +<STRONG>Compiling:</STRONG> Use the "best" compiler for the platform, given that
   the object code built with the compiler is free from any restrictions
   the compiler might put on it.  Set for the first or second level of
   optimization, and don't compile with debugging since anyone who can use a
  
  
  
  1.2       +16 -16    apache-devsite/bug_track.html
  
  Index: bug_track.html
  ===================================================================
  RCS file: /export/home/cvs/apache-devsite/bug_track.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- bug_track.html	1997/06/17 10:43:28	1.1
  +++ bug_track.html	1998/02/12 14:39:20	1.2
  @@ -10,38 +10,38 @@
   <DL>
     <DT>#0001</DT>
        <DD>
  -     <B>Version:</B> 1.1b1<BR>
  -     <B>Status:</B> pending<BR>
  -     <B>Description:</B> mod_status.c sprintf type problems w/ SunOS compiler.
  +     <STRONG>Version:</STRONG> 1.1b1<BR>
  +     <STRONG>Status:</STRONG> pending<BR>
  +     <STRONG>Description:</STRONG> mod_status.c sprintf type problems w/ SunOS compiler.
        </DD>
   
     <DT>#0002</DT>
        <DD>
  -     <B>Version:</B> 1.1b1<BR>
  -     <B>Status:</B> pending<BR>
  -     <B>Description:</B> Apache waits for background perl scripts to end (HPUX at least).
  +     <STRONG>Version:</STRONG> 1.1b1<BR>
  +     <STRONG>Status:</STRONG> pending<BR>
  +     <STRONG>Description:</STRONG> Apache waits for background perl scripts to end (HPUX at least).
        </DD>
   
     <DT>#0003</DT>
        <DD>
  -     <B>Version:</B> 1.0.3 &amp; 1.0.5<BR>
  -     <B>Status:</B> ?<BR>
  -     <B>Description:</B> Apache processes can loop in a CPU unfriendly way if a user directory doesn't exist.
  +     <STRONG>Version:</STRONG> 1.0.3 &amp; 1.0.5<BR>
  +     <STRONG>Status:</STRONG> ?<BR>
  +     <STRONG>Description:</STRONG> Apache processes can loop in a CPU unfriendly way if a user directory doesn't exist.
        </DD>
   
     <DT>#0004</DT>
        <DD>
  -     <B>Version:</B> 1.0.* &amp; 1.1b1<BR>
  -     <B>Status:</B> ?<BR>
  -     <B>Description:</B> HPUX 10 no longer needs <CODE>getwd</CODE>  to be defined... but HPUX 9.* still does  :-|<BR>
  +     <STRONG>Version:</STRONG> 1.0.* &amp; 1.1b1<BR>
  +     <STRONG>Status:</STRONG> ?<BR>
  +     <STRONG>Description:</STRONG> HPUX 10 no longer needs <CODE>getwd</CODE>  to be defined... but HPUX 9.* still does  :-|<BR>
        </DD>
   
     <DT>#0005</DT>
        <DD>
  -     <B>Version:</B>1.1b1<BR>
  -     <B>Status:</B> fixed in next release<BR>
  -     <B>Symptom:</B> On Solaris, authenticaton core dumps.<BR>
  -     <B>Description:</B> Solaris rightly doesn't like string functions to be given null pointers. (mod_digest.c, line 124).<BR>
  +     <STRONG>Version:</STRONG>1.1b1<BR>
  +     <STRONG>Status:</STRONG> fixed in next release<BR>
  +     <STRONG>Symptom:</STRONG> On Solaris, authenticaton core dumps.<BR>
  +     <STRONG>Description:</STRONG> Solaris rightly doesn't like string functions to be given null pointers. (mod_digest.c, line 124).<BR>
        </DD>
   
   </DL>
  
  
  
  1.8       +12 -12    apache-devsite/guidelines.html
  
  Index: guidelines.html
  ===================================================================
  RCS file: /export/home/cvs/apache-devsite/guidelines.html,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- guidelines.html	1998/01/25 09:08:33	1.7
  +++ guidelines.html	1998/02/12 14:39:20	1.8
  @@ -15,12 +15,12 @@
   <IMG SRC="images/apache_logo.gif" ALT="">
   <H1 ALIGN=CENTER>Apache Project Guidelines</H1>
   
  -<P><B>DRAFT</B>: These guidelines are not yet approved.</P>
  +<P><STRONG>DRAFT</STRONG>: These guidelines are not yet approved.</P>
   </CENTER>
   
   <P>
   This document defines the guidelines for the
  -<a href="http://dev.apache.org/">Apache Project</a>.
  +<A HREF="http://dev.apache.org/">Apache Project</A>.
   It includes definitions of how conflict is resolved by voting,
   who is able to vote, and the procedures to follow for proposing and making
   changes to the Apache products.
  @@ -150,7 +150,7 @@
     </DD><P>
     <DT><STRONG>-1</STRONG></DT>
     <DD>No. On issues where consensus is required, this vote counts as a
  -      <strong>veto</strong>.  All vetos must include an explanation of
  +      <STRONG>veto</STRONG>.  All vetos must include an explanation of
         why the veto is appropriate.  A veto with no explanation is void.
         No veto can be overruled. If you disagree with the veto, you
         should lobby the person who cast the veto. Voters intending to veto
  @@ -160,13 +160,13 @@
   </DL>
   
   <P>
  -An action item requiring <em>consensus approval</em> must receive
  +An action item requiring <EM>consensus approval</EM> must receive
   at least <STRONG>3 binding +1</STRONG> votes and <STRONG>no vetos</STRONG>.
  -An action item requiring <em>majority approval</em> must receive
  +An action item requiring <EM>majority approval</EM> must receive
   at least <STRONG>3 binding +1</STRONG> votes and more <STRONG>+1</STRONG>
   votes than <STRONG>-1</STRONG> votes (<EM>i.e.</EM>, a majority with a minimum
   quorum of three positive votes).  All other action items are considered
  -to have <em>lazy approval</em> until someone votes <STRONG>-1</STRONG>,
  +to have <EM>lazy approval</EM> until someone votes <STRONG>-1</STRONG>,
   after which point they are decided by either consensus or a majority vote,
   depending upon the type of action item.
   </P>
  @@ -188,7 +188,7 @@
         but group members who do not agree with a particular plan,
         or think an alternate plan would be better, are obligated to
         inform the group of their feelings.  In general, it is always
  -      better to hear about alternate plans <strong>prior</strong> to
  +      better to hear about alternate plans <STRONG>prior</STRONG> to
         spending time on less adequate solutions.
   
     <DT><STRONG>Short Term Plans</STRONG></DT>
  @@ -223,15 +223,15 @@
         will appear as action items under several categories corresponding
         to the change status:
         <DL>
  -      <DT><b>concept/plan</b>
  +      <DT><STRONG>concept/plan</STRONG>
         <DD>An idea or plan for a change.  These are usually only listed in
             STATUS when the change is substantial, significantly impacts the
             API, or is likely to be controversial.  Votes are being requested
             early so as to uncover conflicts before too much work is done.
  -      <DT><b>proposed patch</b>
  +      <DT><STRONG>proposed patch</STRONG>
         <DD>A specific set of changes to the current product in the form
  -          of <a href="#patch">input to the patch command</a> (a diff output).
  -      <DT><b>committed change</b>
  +          of <A HREF="#patch">input to the patch command</A> (a diff output).
  +      <DT><STRONG>committed change</STRONG>
         <DD>A one-line summary of a change that has been committed to the
             repository since the last public release.
         </DL>
  @@ -300,7 +300,7 @@
   </P>
   
   <H2><IMG SRC="images/apache_feather_bullet.gif" ALT="o ">
  -<a name="patch">Patch Format</a></H2>
  +<A NAME="patch">Patch Format</A></H2>
   
   <P>
   When a specific change to the software is proposed for discussion or
  
  
  
  1.2       +2 -2      apache-devsite/home.html
  
  Index: home.html
  ===================================================================
  RCS file: /export/home/cvs/apache-devsite/home.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- home.html	1997/06/17 10:43:29	1.1
  +++ home.html	1998/02/12 14:39:21	1.2
  @@ -9,11 +9,11 @@
   
   <P><HR>
   
  -<I>The Apache project has been organized in an attempt to answer some
  +<EM>The Apache project has been organized in an attempt to answer some
   of the concerns regarding active development of a public domain HTTP
   server. The goal of this project is to provide a secure, efficient and
   extensible server which provides HTTP services in sync with the
  -current HTTP standards.</I> 
  +current HTTP standards.</EM> 
   
   <HR><P>
   
  
  
  
  1.25      +211 -211  apache-devsite/how-to-release.html
  
  Index: how-to-release.html
  ===================================================================
  RCS file: /export/home/cvs/apache-devsite/how-to-release.html,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- how-to-release.html	1998/02/09 13:30:10	1.24
  +++ how-to-release.html	1998/02/12 14:39:21	1.25
  @@ -18,87 +18,87 @@
   
   <div align=center>
   <H1>How to build a release of Apache</H1>
  -Alexei Kosut &lt;akosut@apache.org&gt;<br>
  -Ralf S. Engelschall &lt;rse@apache.org&gt;<br>
  +Alexei Kosut &lt;akosut@apache.org&gt;<BR>
  +Ralf S. Engelschall &lt;rse@apache.org&gt;<BR>
   Jim Jagielski &lt;jim@apache.org&gt;
  -</div>
  +</DIV>
   
  -<blockquote>
  -<blockquote>
  -<blockquote>
  +<BLOCKQUOTE>
  +<BLOCKQUOTE>
  +<BLOCKQUOTE>
   This document describes the typical release cycle the release manager has to
   step through when creating a new Apache release.  It is written down as a
   step-by-step instruction list and should be followed exactly as specified to
   avoid problems or inconsistencies both in the created tarballs and the source
   repository.
  -</blockquote>
  -</blockquote>
  -</blockquote>
  -
  -<p>
  -<br>
  -<h2>Announcing a New Release</h2>
  +</BLOCKQUOTE>
  +</BLOCKQUOTE>
  +</BLOCKQUOTE>
   
  -<p>Once a release is built (<A HREF="#tarball">see below</A>),
  +<P>
  +<BR>
  +<H2>Announcing a New Release</H2>
  +
  +<P>Once a release is built (<A HREF="#tarball">see below</A>),
   it is time to announce it to the world. Ideally, the Announcement
  -should be composed <strong>before</strong> the Release is actually built. So
  +should be composed <STRONG>before</STRONG> the Release is actually built. So
   we describe these steps at the beginning.
   
  -<ol>
  -<hr>
  +<OL>
  +<HR>
   
  -  <b>[ Adjusting Announcement to taste ]</b><br>
  -  <p>
  -  <li>A prototype <code>Announcement</code> is included in
  +  <STRONG>[ Adjusting Announcement to taste ]</STRONG><BR>
  +  <P>
  +  <LI>A prototype <CODE>Announcement</CODE> is included in
         the main CVS source tree. This file should be updated
         to reflect the current state of affairs concerning the
         release. For example, the Release Version should reflect
         what is actually being announced. Also, the key enhancements
  -      of the Release should be noted.<br>
  -     <code><b>$ cvs checkout apache-1.3</b></code><br>
  -     <code><b>$ cd apache-1.3</b></code><br>
  -     <code><b>$ vi Announcement</b></code><br>
  -     <code><b>$ cvs commit Announcement</b></code>
  -  <p> 
  -  <hr>
  -  <b>[ Building the source release ]</b><br>
  -  <p>
  -  <li>First, build the source release (<A HREF="#tarball">see below</A>)
  +      of the Release should be noted.<BR>
  +     <CODE><STRONG>$ cvs checkout apache-1.3</STRONG></CODE><BR>
  +     <CODE><STRONG>$ cd apache-1.3</STRONG></CODE><BR>
  +     <CODE><STRONG>$ vi Announcement</STRONG></CODE><BR>
  +     <CODE><STRONG>$ cvs commit Announcement</STRONG></CODE>
  +  <P> 
  +  <HR>
  +  <STRONG>[ Building the source release ]</STRONG><BR>
  +  <P>
  +  <LI>First, build the source release (<A HREF="#tarball">see below</A>)
         if not already done.
  -  <p> 
  -  <hr>
  -  <b>[ Posting the Announcement ]</b><br>
  -  <p>
  -  <li>Once built, <code>Announcement</code> should be
  +  <P> 
  +  <HR>
  +  <STRONG>[ Posting the Announcement ]</STRONG><BR>
  +  <P>
  +  <LI>Once built, <CODE>Announcement</CODE> should be
         posted to the following places:
  -   <ul>
  -    <li>Unmoderated UseNet newsgroups (should be crossposted)
  -     <ul>
  -      <li><code>comp.infosystems.www.servers.unix</code>
  -      <li><code>comp.infosystems.www.servers.ms-windows</code>
  -      <li><code>comp.infosystems.www.servers.misc</code>
  -      <li><code>de.comm.infosystems.www.servers</code>
  -     </ul>
  -    <li>Moderated UseNet newsgroups (do <b>not</b> crosspost)
  -     <ul>
  -      <li><code>comp.infosystems.www.announce</code>
  -     </ul>
  -    <li>Mailing Lists
  -     <ul>
  -      <li><code>apache-announce@apache.org</code>
  -     </ul>
  -   </ul>
  -  <p>
  -  <li>Bask in the glow
  -</ol>
  +   <UL>
  +    <LI>Unmoderated UseNet newsgroups (should be crossposted)
  +     <UL>
  +      <LI><CODE>comp.infosystems.www.servers.unix</CODE>
  +      <LI><CODE>comp.infosystems.www.servers.ms-windows</CODE>
  +      <LI><CODE>comp.infosystems.www.servers.misc</CODE>
  +      <LI><CODE>de.comm.infosystems.www.servers</CODE>
  +     </UL>
  +    <LI>Moderated UseNet newsgroups (do <STRONG>not</STRONG> crosspost)
  +     <UL>
  +      <LI><CODE>comp.infosystems.www.announce</CODE>
  +     </UL>
  +    <LI>Mailing Lists
  +     <UL>
  +      <LI><CODE>apache-announce@apache.org</CODE>
  +     </UL>
  +   </UL>
  +  <P>
  +  <LI>Bask in the glow
  +</OL>
   
   <P>
   <BR>
   
  -<h2><A NAME="tarball">How to build an Apache Unix release</A></h2>
  +<H2><A NAME="tarball">How to build an Apache Unix release</A></H2>
   
   <P><FONT COLOR="red">Note:</FONT> The below assumes that you are
  -using <code>ssh</code> to login to your <code>dev.apache.org</code>
  +using <CODE>ssh</CODE> to login to your <CODE>dev.apache.org</CODE>
   account. If you are "rolling the tarball" remotely, the differences
   will be noted.
   
  @@ -109,221 +109,221 @@
   
   <OL>
   <HR>
  -<LI> Checkout the Apache source if needed into a scratch directory:<br>
  -     <code><b>$ cvs checkout apache-1.3</b></code>
  +<LI> Checkout the Apache source if needed into a scratch directory:<BR>
  +     <CODE><STRONG>$ cvs checkout apache-1.3</STRONG></CODE>
   <P>
  -<LI> cd into the <code>apache-1.3</code> CVS tree.<br>
  -     <code><b>$ cd apache-1.3</b></code>
  +<LI> cd into the <CODE>apache-1.3</CODE> CVS tree.<BR>
  +     <CODE><STRONG>$ cd apache-1.3</STRONG></CODE>
   <P>
   
  -<hr>
  -<b>[ Only for final releases, not for internal pre-releases ]</b><br>
  -<P>
  -<LI> Change <code>SERVER_VERSION</code> in <tt>src/main/httpd.h</tt>
  -	 from ``<code>Apache/1.X.Y-dev</code>'' to
  -	 ``<code>Apache/1.X.Y</code>''. Then also change
  -	 <code>APACHE_RELEASE</code> in same file from
  -	 ``<code>1XXYYZZ</code>'' to ``<code>1XXYY99</code>''. The format is
  -	 something like <code>printf("%d%02d%02d%02d", major, minor, bugfix,
  -	 betaseq)</code>.<br>
  -     <code><b>$ vi src/main/httpd.h</b></code><br>
  -     <code><b>$ cvs commit src/main/httpd.h</b></code>
  -<P>
  -<LI> Tag the sources for this release:<br>
  -     (<i>note: be sure to tag the whole thing, not just <code>src</code></i>!)<br>
  -     <code><b>$ cvs tag APACHE_1_X_Y .</b></code>
  +<HR>
  +<STRONG>[ Only for final releases, not for internal pre-releases ]</STRONG><BR>
  +<P>
  +<LI> Change <CODE>SERVER_VERSION</CODE> in <TT>src/main/httpd.h</TT>
  +	 from ``<CODE>Apache/1.X.Y-dev</CODE>'' to
  +	 ``<CODE>Apache/1.X.Y</CODE>''. Then also change
  +	 <CODE>APACHE_RELEASE</CODE> in same file from
  +	 ``<CODE>1XXYYZZ</CODE>'' to ``<CODE>1XXYY99</CODE>''. The format is
  +	 something like <CODE>printf("%d%02d%02d%02d", major, minor, bugfix,
  +	 betaseq)</CODE>.<BR>
  +     <CODE><STRONG>$ vi src/main/httpd.h</STRONG></CODE><BR>
  +     <CODE><STRONG>$ cvs commit src/main/httpd.h</STRONG></CODE>
  +<P>
  +<LI> Tag the sources for this release:<BR>
  +     (<EM>note: be sure to tag the whole thing, not just <CODE>src</CODE></EM>!)<BR>
  +     <CODE><STRONG>$ cvs tag APACHE_1_X_Y .</STRONG></CODE>
   <P>
   <HR>
  -<b>[ For all releases ]</b><br>
  +<STRONG>[ For all releases ]</STRONG><BR>
   <P>
  -<LI> Make an export version of the distribution:<br>
  -     <code><b>$ cd ..</b></code><br>
  -     <code><b>$ umask 022</b></code><br>
  -     <code><b>$ cvs export -r APACHE_1_X_Y -d apache_1.X.Y apache-1.3</b></code><br>
  -     <code><b>$ cd apache_1.X.Y</b></code><br>
  +<LI> Make an export version of the distribution:<BR>
  +     <CODE><STRONG>$ cd ..</STRONG></CODE><BR>
  +     <CODE><STRONG>$ umask 022</STRONG></CODE><BR>
  +     <CODE><STRONG>$ cvs export -r APACHE_1_X_Y -d apache_1.X.Y apache-1.3</STRONG></CODE><BR>
  +     <CODE><STRONG>$ cd apache_1.X.Y</STRONG></CODE><BR>
        <UL>
        <LI><FONT COLOR="red">Note:</FONT> There is a known problem
  -     using <code>cvs export</code> remotely with <code>cvs-1.9</code>
  +     using <CODE>cvs export</CODE> remotely with <CODE>cvs-1.9</CODE>
        and later. If this affects you, you will need to do a checkout
  -     instead:<br>
  -     <code><b>$ umask 022</b></code><br>
  -     <code><b>$ cvs checkout -r APACHE_1_X_Y -d apache_1.X.Y apache-1.3</b></code><br>
  -     <code><b>$ cd apache_1.X.Y</b></code><br>
  +     instead:<BR>
  +     <CODE><STRONG>$ umask 022</STRONG></CODE><BR>
  +     <CODE><STRONG>$ cvs checkout -r APACHE_1_X_Y -d apache_1.X.Y apache-1.3</STRONG></CODE><BR>
  +     <CODE><STRONG>$ cd apache_1.X.Y</STRONG></CODE><BR>
        </UL>
   <P>
  -<LI> Create <code>src/Configuration</code> file:<br>
  -     <code><b>$ cp src/Configuration.tmpl src/Configuration</b></code>
  +<LI> Create <CODE>src/Configuration</CODE> file:<BR>
  +     <CODE><STRONG>$ cp src/Configuration.tmpl src/Configuration</STRONG></CODE>
   <P>
  -<LI> Remove <code>STATUS</code>, <code>RULES.CVS</code> and
  -     <code>src/INDENT</code>file and various <code>.cvsignore</code> files:<br>
  -     <code><b>$ rm STATUS RULES.CVS src/INDENT</b></code><br>
  -     <code><b>$ find . -name ".cvsignore" -exec rm {} \;</b></code>
  +<LI> Remove <CODE>STATUS</CODE>, <CODE>RULES.CVS</CODE> and
  +     <CODE>src/INDENT</CODE>file and various <CODE>.cvsignore</CODE> files:<BR>
  +     <CODE><STRONG>$ rm STATUS RULES.CVS src/INDENT</STRONG></CODE><BR>
  +     <CODE><STRONG>$ find . -name ".cvsignore" -exec rm {} \;</STRONG></CODE>
        <UL>
        <LI><FONT COLOR="red">Note:</FONT> If you needed to do a
  -     <code>checkout</code> instead of a <code>export</code>, you
  -     will also need to remove the CVS administrative files:<br>
  -     <code><b>$ find . -type d -name "CVS" -exec rm -rf {} \;</b></code>
  +     <CODE>checkout</CODE> instead of a <CODE>export</CODE>, you
  +     will also need to remove the CVS administrative files:<BR>
  +     <CODE><STRONG>$ find . -type d -name "CVS" -exec rm -rf {} \;</STRONG></CODE>
        </UL>
   <P>
  -<LI> Add an empty <code>logs/</code> directory:<br>
  -     <code><b>$ mkdir logs</b></code>
  +<LI> Add an empty <CODE>logs/</CODE> directory:<BR>
  +     <CODE><STRONG>$ mkdir logs</STRONG></CODE>
   <P>
  -<LI> Expand the Service-Side-Include directives in the manual:<br>
  -     <code><b>$ cd htdocs/manual</b></code><br>
  -     <code><b>$ ./expand.pl</b></code><br>
  -     <code><b>$ rm ./expand.pl</b></code><br>
  -     <code><b>$ cd ../../..</b></code>
  -<P>
  -<LI> Roll the distribution tarball:<br>
  -     <code><b>$ tar cvf apache_1.X.Y.tar apache_1.X.Y</b></code><br>
  -<P>
  -<LI> Make the final packed distribution files:<br>
  -     <code><b>$ cp -p apache_1.X.Y.tar xapache_1.X.Y.tar</b></code><br>
  -     <code><b>$ gzip -9 apache_1.X.Y.tar</b></code><br>
  -     <code><b>$ mv xapache_1.X.Y.tar apache_1.X.Y.tar</b></code><br>
  -     <code><b>$ compress apache_1.X.Y.tar</b></code><br>
  -<P>
  -<LI> Test the packed tar files and check for errors:<br>
  -     <code><b>$ gunzip -c apache_1.X.Y.tar.gz | tar tvf -</b></code><br>
  -     <code><b>$ zcat apache_1.X.Y.tar.Z | tar tvf -</b></code><br>
  -<P>
  -<LI> Cleanup:<br>
  -     <code><b>$ rm -rf apache_1.X.Y</b></code>
  -<P>
  -<LI> Sign the distribution files:<br>
  -     <code><b>$ pgp -sba apache_1.X.Y.tar.gz</b></code><br>
  -     <code><b>$ pgp -sba apache_1.X.Y.tar.Z</b></code><br>
  +<LI> Expand the Service-Side-Include directives in the manual:<BR>
  +     <CODE><STRONG>$ cd htdocs/manual</STRONG></CODE><BR>
  +     <CODE><STRONG>$ ./expand.pl</STRONG></CODE><BR>
  +     <CODE><STRONG>$ rm ./expand.pl</STRONG></CODE><BR>
  +     <CODE><STRONG>$ cd ../../..</STRONG></CODE>
  +<P>
  +<LI> Roll the distribution tarball:<BR>
  +     <CODE><STRONG>$ tar cvf apache_1.X.Y.tar apache_1.X.Y</STRONG></CODE><BR>
  +<P>
  +<LI> Make the final packed distribution files:<BR>
  +     <CODE><STRONG>$ cp -p apache_1.X.Y.tar xapache_1.X.Y.tar</STRONG></CODE><BR>
  +     <CODE><STRONG>$ gzip -9 apache_1.X.Y.tar</STRONG></CODE><BR>
  +     <CODE><STRONG>$ mv xapache_1.X.Y.tar apache_1.X.Y.tar</STRONG></CODE><BR>
  +     <CODE><STRONG>$ compress apache_1.X.Y.tar</STRONG></CODE><BR>
  +<P>
  +<LI> Test the packed tar files and check for errors:<BR>
  +     <CODE><STRONG>$ gunzip -c apache_1.X.Y.tar.gz | tar tvf -</STRONG></CODE><BR>
  +     <CODE><STRONG>$ zcat apache_1.X.Y.tar.Z | tar tvf -</STRONG></CODE><BR>
  +<P>
  +<LI> Cleanup:<BR>
  +     <CODE><STRONG>$ rm -rf apache_1.X.Y</STRONG></CODE>
  +<P>
  +<LI> Sign the distribution files:<BR>
  +     <CODE><STRONG>$ pgp -sba apache_1.X.Y.tar.gz</STRONG></CODE><BR>
  +     <CODE><STRONG>$ pgp -sba apache_1.X.Y.tar.Z</STRONG></CODE><BR>
        <UL>
   	 <LI><FONT COLOR="red">Note:</FONT> Be sure your PGP key is already in the
  -	 <code>KEYS</code> file</em>!)<br>
  +	 <CODE>KEYS</CODE> file</EM>!)<BR>
   	 </UL>
   <P>
  -<LI> Make the tarball available for testing purposes:<br>
  -     <code><b>$ cp apache_1.X.Y.tar.gz /pub/httpd/dist</b></code><br>
  -     <code><b>$ cp apache_1.X.Y.tar.gz.asc /pub/httpd/dist</b></code><br>
  -     <code><b>$ cp apache_1.X.Y.tar.Z /pub/httpd/dist</b></code><br>
  -     <code><b>$ cp apache_1.X.Y.tar.Z.asc /pub/httpd/dist</b></code><br>
  +<LI> Make the tarball available for testing purposes:<BR>
  +     <CODE><STRONG>$ cp apache_1.X.Y.tar.gz /pub/httpd/dist</STRONG></CODE><BR>
  +     <CODE><STRONG>$ cp apache_1.X.Y.tar.gz.asc /pub/httpd/dist</STRONG></CODE><BR>
  +     <CODE><STRONG>$ cp apache_1.X.Y.tar.Z /pub/httpd/dist</STRONG></CODE><BR>
  +     <CODE><STRONG>$ cp apache_1.X.Y.tar.Z.asc /pub/httpd/dist</STRONG></CODE><BR>
        <UL>
        <LI><FONT COLOR="red">Note:</FONT> If rolling the tarball
  -     remotely, you should use <code>scp</code> to place them
  -     in <code>dev.apache.org</code> in the <code>/pub/httpd/dist</code>
  +     remotely, you should use <CODE>scp</CODE> to place them
  +     in <CODE>dev.apache.org</CODE> in the <CODE>/pub/httpd/dist</CODE>
        directory.
        </UL>
   
   <P>
   <HR>
  -<b>[ Final release steps <u>after</u> the group has approved the tarball ]</b><br>
  +<STRONG>[ Final release steps <U>after</U> the group has approved the tarball ]</STRONG><BR>
   <P>
   
  -<em><FONT COLOR="red">Note:</FONT> Do not continue with the rest of
  -these instructions until the group really approves the tarball !</em>
  +<EM><FONT COLOR="red">Note:</FONT> Do not continue with the rest of
  +these instructions until the group really approves the tarball !</EM>
   
   <P>
  -<LI> Make the distribution available:<br>
  -     <code><b>$ cp apache_1.X.Y.tar.gz /pub/apache/dist</b></code><br>
  -     <code><b>$ cp apache_1.X.Y.tar.gz.asc /pub/apache/dist</b></code><br>
  -     <code><b>$ cp apache_1.X.Y.tar.Z /pub/apache/dist</b></code><br>
  -     <code><b>$ cp apache_1.X.Y.tar.Z.asc /pub/apache/dist</b></code><br>
  +<LI> Make the distribution available:<BR>
  +     <CODE><STRONG>$ cp apache_1.X.Y.tar.gz /pub/apache/dist</STRONG></CODE><BR>
  +     <CODE><STRONG>$ cp apache_1.X.Y.tar.gz.asc /pub/apache/dist</STRONG></CODE><BR>
  +     <CODE><STRONG>$ cp apache_1.X.Y.tar.Z /pub/apache/dist</STRONG></CODE><BR>
  +     <CODE><STRONG>$ cp apache_1.X.Y.tar.Z.asc /pub/apache/dist</STRONG></CODE><BR>
        <UL>
        <LI><FONT COLOR="red">Note:</FONT> If rolling the tarball
  -     remotely, you should use <code>scp</code> to place them
  -     in <code>dev.apache.org</code> in the <code>/pub/apache/dist</code>
  +     remotely, you should use <CODE>scp</CODE> to place them
  +     in <CODE>dev.apache.org</CODE> in the <CODE>/pub/apache/dist</CODE>
        directory.
        </UL>
   <P>
  -<LI> Checkout the Apache site if needed into a scratch directory:<br>
  -     <code><b>$ cvs checkout apache-site</b></code>
  +<LI> Checkout the Apache site if needed into a scratch directory:<BR>
  +     <CODE><STRONG>$ cvs checkout apache-site</STRONG></CODE>
   <P>
  -<LI> cd into the <code>apache-site</code> CVS tree.<br>
  -     <code><b>$ cd apache-site</b></code>
  +<LI> cd into the <CODE>apache-site</CODE> CVS tree.<BR>
  +     <CODE><STRONG>$ cd apache-site</STRONG></CODE>
   <P>
  -<LI> Edit <code>README.html</code> from <code>apache-site</code> CVS tree
  -     (it's in the <code>./dist</code> subdirectory) as required:<br>
  -     <code><b>$ vi dist/README.html</b></code><br>
  -     <code><b>$ cvs commit dist/README.html</b></code><br>
  -<P>
  -<LI> Edit the Apache <code>index.html</code> from <code>apache-site</code>
  -     CVS tree as required:<br>
  -     <code><b>$ vi index.html</b></code><br>
  -     <code><b>$ cvs commit index.html</b></code><br>
  +<LI> Edit <CODE>README.html</CODE> from <CODE>apache-site</CODE> CVS tree
  +     (it's in the <CODE>./dist</CODE> subdirectory) as required:<BR>
  +     <CODE><STRONG>$ vi dist/README.html</STRONG></CODE><BR>
  +     <CODE><STRONG>$ cvs commit dist/README.html</STRONG></CODE><BR>
  +<P>
  +<LI> Edit the Apache <CODE>index.html</CODE> from <CODE>apache-site</CODE>
  +     CVS tree as required:<BR>
  +     <CODE><STRONG>$ vi index.html</STRONG></CODE><BR>
  +     <CODE><STRONG>$ cvs commit index.html</STRONG></CODE><BR>
   <P>
   <HR>
  -<b>[ Only for final releases, not for internal pre-releases ]</b><br>
  +<STRONG>[ Only for final releases, not for internal pre-releases ]</STRONG><BR>
   <P>
  -<LI> cd back into the <code>apache-1.3</code> CVS tree location.<br>
  -     <code><b>$ cd ../apache-1.3</b></code>
  +<LI> cd back into the <CODE>apache-1.3</CODE> CVS tree location.<BR>
  +     <CODE><STRONG>$ cd ../apache-1.3</STRONG></CODE>
   <P>
  -<LI> Change <code>SERVER_VERSION</code> in <code>src/main/httpd.h</code>
  -	 from ``<code>Apache/1.X.Y</code>'' to
  -	 ``<code>Apache/1.X.(Y+1)-dev</code>'' and change
  -	 <code>APACHE_RELEASE</code> to <code>1XX(YY+1)01</code>.<br>
  -     <code><b>$ vi src/main/httpd.h</b></code><br>
  -     <code><b>$ cvs commit src/main/httpd.h</b></code>
  +<LI> Change <CODE>SERVER_VERSION</CODE> in <CODE>src/main/httpd.h</CODE>
  +	 from ``<CODE>Apache/1.X.Y</CODE>'' to
  +	 ``<CODE>Apache/1.X.(Y+1)-dev</CODE>'' and change
  +	 <CODE>APACHE_RELEASE</CODE> to <CODE>1XX(YY+1)01</CODE>.<BR>
  +     <CODE><STRONG>$ vi src/main/httpd.h</STRONG></CODE><BR>
  +     <CODE><STRONG>$ cvs commit src/main/httpd.h</STRONG></CODE>
   </OL>
   
   <P>
   <BR>
  -<h2>How to build an Apache Windows release</h2>
  +<H2>How to build an Apache Windows release</H2>
   
   <FONT COLOR="red">Note:</FONT> These instructions are temporary, until we have a
   working installation of InstallShield, which will eventually be used to
   distribute Apache for Windows. At that time, these instructions will be
   replaced.
   
  -<ol>
  +<OL>
   
  -<hr>
  +<HR>
   
  -  <b>[ Building a source release ]</b><br>
  -  <p>
  -  <li>Follow the instructions numbered 3-7 for Unix, to build an Apache
  +  <STRONG>[ Building a source release ]</STRONG><BR>
  +  <P>
  +  <LI>Follow the instructions numbered 3-7 for Unix, to build an Apache
         distribution. Be sure to use CVS running on Windows, so that the
         linebreaks will be correct (alternately, export the repository with
         Unix, and convert all text files - all text files - from \n to
         \r\n)
  -  <p>
  -  <li>Create a zipfile, using your favorite zip program, containing the
  -      <code>apache_1.X.Y</code> directory. Name this zipfile
  -      <code>apache_1.X.Y-src.zip</code>.
  -
  -  <p>
  -  <hr>
  -  <b>[ Building a binary release ]</b><br>
  -  <p>
  -  <li>First, build the source release (see above).
  -  <p>
  -  <li>Compile and "install" a release version of Apache:<br>
  -      <code><b>&gt; nmake /f Makefile.nt _apacher</b></code><br>
  -      <code><b>&gt; nmake /f Makefile.nt installr</b></code>
  -  <p>
  -  <li>Rename the directory<br>
  -      <code><b>&gt; move \Apache \Apache_1.X.Y</b></code>
  -  <p>
  -  <li>Move the configuration files into the correct place<br>
  -      <code><b>&gt; copy conf\access.conf-dist-win
  -      \Apache_1.X.Y\access.conf-dist</b></code><br>
  -      <code><b>&gt; copy conf\httpd.conf-dist-win
  -      \Apache_1.X.Y\httpd.conf-dist</b></code><br>
  -      <code><b>&gt; copy conf\srm.conf-dist-win
  -      \Apache_1.X.Y\srm.conf</b></code><br>
  -      <code><b>&gt; copy conf\mime.types
  -      \Apache_1.X.Y\mime.types</b></code><br>
  -      <code><b>&gt; copy conf\magic
  -      \Apache_1.X.Y\magic</b></code>
  -  <p>
  -  <li>Move the HTML documents into place<br>
  -      <code><b>&gt; copy htdocs \Apache_1.X.Y\htdocs</b></code>
  -  <p>
  -  <li>Copy the readme file<br>
  -      <code><b>&gt; copy README.NT \Apache_1.X.Y\readme.txt</b></code>
  -  <p>
  -  <li>Install the Visual C++ runtime DLLs, wherever it is they need to
  +  <P>
  +  <LI>Create a zipfile, using your favorite zip program, containing the
  +      <CODE>apache_1.X.Y</CODE> directory. Name this zipfile
  +      <CODE>apache_1.X.Y-src.zip</CODE>.
  +
  +  <P>
  +  <HR>
  +  <STRONG>[ Building a binary release ]</STRONG><BR>
  +  <P>
  +  <LI>First, build the source release (see above).
  +  <P>
  +  <LI>Compile and "install" a release version of Apache:<BR>
  +      <CODE><STRONG>&gt; nmake /f Makefile.nt _apacher</STRONG></CODE><BR>
  +      <CODE><STRONG>&gt; nmake /f Makefile.nt installr</STRONG></CODE>
  +  <P>
  +  <LI>Rename the directory<BR>
  +      <CODE><STRONG>&gt; move \Apache \Apache_1.X.Y</STRONG></CODE>
  +  <P>
  +  <LI>Move the configuration files into the correct place<BR>
  +      <CODE><STRONG>&gt; copy conf\access.conf-dist-win
  +      \Apache_1.X.Y\access.conf-dist</STRONG></CODE><BR>
  +      <CODE><STRONG>&gt; copy conf\httpd.conf-dist-win
  +      \Apache_1.X.Y\httpd.conf-dist</STRONG></CODE><BR>
  +      <CODE><STRONG>&gt; copy conf\srm.conf-dist-win
  +      \Apache_1.X.Y\srm.conf</STRONG></CODE><BR>
  +      <CODE><STRONG>&gt; copy conf\mime.types
  +      \Apache_1.X.Y\mime.types</STRONG></CODE><BR>
  +      <CODE><STRONG>&gt; copy conf\magic
  +      \Apache_1.X.Y\magic</STRONG></CODE>
  +  <P>
  +  <LI>Move the HTML documents into place<BR>
  +      <CODE><STRONG>&gt; copy htdocs \Apache_1.X.Y\htdocs</STRONG></CODE>
  +  <P>
  +  <LI>Copy the readme file<BR>
  +      <CODE><STRONG>&gt; copy README.NT \Apache_1.X.Y\readme.txt</STRONG></CODE>
  +  <P>
  +  <LI>Install the Visual C++ runtime DLLs, wherever it is they need to
         go (???)
  -  <p>
  -  <li>Create a zipfile of <code>\Apache_1.X.Y</code> named
  -      <code>apache_1.X.Y-bin.zip</code>.      
  +  <P>
  +  <LI>Create a zipfile of <CODE>\Apache_1.X.Y</CODE> named
  +      <CODE>apache_1.X.Y-bin.zip</CODE>.      
   
  -</ol>
  +</OL>
   
   <!--#include virtual="footer.html" -->
   
  
  
  
  1.16      +2 -2      apache-devsite/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /export/home/cvs/apache-devsite/index.html,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- index.html	1998/01/25 09:08:33	1.15
  +++ index.html	1998/02/12 14:39:22	1.16
  @@ -26,7 +26,7 @@
      <LI><A HREF="guidelines">Apache Project Guidelines</A>, currently in
          draft form.  <A HREF="voting" >Old Guidelines</A>.
      </LI>
  -   <LI><A HREF="devnotes">Apache Development Notes</a> about
  +   <LI><A HREF="devnotes">Apache Development Notes</A> about
          using CVS and maintaining the Apache site.
      </LI>
      <LI><A HREF="http://bugs.apache.org/">Read-only</A>, or
  @@ -68,7 +68,7 @@
       >build binary distributions</A>
       (last modified on <!--#flastmod virtual="binaries.html" -->)
      </LI>
  -   <LI>A <a href="binbuild.sh">shell script to build a binary release</a>.
  +   <LI>A <A HREF="binbuild.sh">shell script to build a binary release</A>.
      </LI>
      <LI>Record of changes to the
       <A
  
  
  
  1.2       +84 -84    apache-devsite/members.html
  
  Index: members.html
  ===================================================================
  RCS file: /export/home/cvs/apache-devsite/members.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- members.html	1997/06/17 10:43:30	1.1
  +++ members.html	1998/02/12 14:39:22	1.2
  @@ -6,125 +6,125 @@
   
   <BODY>
   <P><HR><P>
  -<B>Name:</B> Brian Behlendorf<BR>
  -<B>email:</B> <A HREF="mailto:brian@organic.com or brian@hyperreal.org">brian@organic.com or brian@hyperreal.org</A><BR>
  -<B>URL:</B> <A HREF="http://www.organic.com/Staff/brian/">http://www.organic.com/Staff/brian/</A><BR>
  -<B>Company:</B> Organic</A><BR>
  -<B>Occupation:</B> Chief Technical Officer<BR>
  -<B>Location:</B> San FranDisco, CA, USA<BR>
  -<B>Comments:</B> The Midwife<BR>
  +<STRONG>Name:</STRONG> Brian Behlendorf<BR>
  +<STRONG>email:</STRONG> <A HREF="mailto:brian@organic.com or brian@hyperreal.org">brian@organic.com or brian@hyperreal.org</A><BR>
  +<STRONG>URL:</STRONG> <A HREF="http://www.organic.com/Staff/brian/">http://www.organic.com/Staff/brian/</A><BR>
  +<STRONG>Company:</STRONG> Organic</A><BR>
  +<STRONG>Occupation:</STRONG> Chief Technical Officer<BR>
  +<STRONG>Location:</STRONG> San FranDisco, CA, USA<BR>
  +<STRONG>Comments:</STRONG> The Midwife<BR>
   
   <P>
   
  -<B>Name:</B> Ron Daniel<BR>
  -<B>email:</B> <A HREF="mailto:rdaniel@lanl.gov">rdaniel@lanl.gov</A><BR>
  -<B>URL:</B> <A HREF="http://www.acl.lanl.gov/~rdaniel/">
  +<STRONG>Name:</STRONG> Ron Daniel<BR>
  +<STRONG>email:</STRONG> <A HREF="mailto:rdaniel@lanl.gov">rdaniel@lanl.gov</A><BR>
  +<STRONG>URL:</STRONG> <A HREF="http://www.acl.lanl.gov/~rdaniel/">
     http://www.acl.lanl.gov/~rdaniel/<BR></A>
  -<B>Company:</B> Los Alamos National Laboratory<BR>
  -<B>Occupation:</B> Technical Staff Member<BR>
  -<B>Location:</B> Los Alamos, NM, USA<BR>
  -<B>Comments:</B> interested in security mods<BR>
  +<STRONG>Company:</STRONG> Los Alamos National Laboratory<BR>
  +<STRONG>Occupation:</STRONG> Technical Staff Member<BR>
  +<STRONG>Location:</STRONG> Los Alamos, NM, USA<BR>
  +<STRONG>Comments:</STRONG> interested in security mods<BR>
   
   <P>
   
  -<B>Name:</B> <A NAME="fielding">Roy T. Fielding</A><BR>
  -<B>email:</B> <A HREF="mailto:fielding@ics.uci.edu">fielding@ics.uci.edu</A><BR>
  -<B>URL:</B> <A HREF="http://www.ics.uci.edu/dir/grad/Software/fielding">
  +<STRONG>Name:</STRONG> <A NAME="fielding">Roy T. Fielding</A><BR>
  +<STRONG>email:</STRONG> <A HREF="mailto:fielding@ics.uci.edu">fielding@ics.uci.edu</A><BR>
  +<STRONG>URL:</STRONG> <A HREF="http://www.ics.uci.edu/dir/grad/Software/fielding">
                        http://www.ics.uci.edu/dir/grad/Software/fielding <BR></A>
  -<B>Company:</B> University of California, Irvine<BR>
  -<B>Occupation:</B> Ph.D. Student, ICS<BR>
  -<B>Location:</B> Irvine, CA <BR>
  -<B>Comments:</B> The HTTP cop <BR>
  +<STRONG>Company:</STRONG> University of California, Irvine<BR>
  +<STRONG>Occupation:</STRONG> Ph.D. Student, ICS<BR>
  +<STRONG>Location:</STRONG> Irvine, CA <BR>
  +<STRONG>Comments:</STRONG> The HTTP cop <BR>
   
   <P>
   
  -<B>Name:</B> Eric Hagberg<BR>
  -<B>email:</B> <A HREF="mailto:hagberg@mail.med.cornell.edu">hagberg@mail.med.cornell.edu</A><BR>
  -<B>URL:</B> <A HREF="http://www2.med.cornell.edu/~hagberg/">http://www2.med.cornell.edu/~hagberg/</A><BR>
  -<B>Company:</B> Cornell Medical College</A><BR>
  -<B>Occupation:</B> User Services Manager<BR>
  -<B>Location:</B> New York, NY, USA<BR>
  -<B>Comments:</B> <BR>
  +<STRONG>Name:</STRONG> Eric Hagberg<BR>
  +<STRONG>email:</STRONG> <A HREF="mailto:hagberg@mail.med.cornell.edu">hagberg@mail.med.cornell.edu</A><BR>
  +<STRONG>URL:</STRONG> <A HREF="http://www2.med.cornell.edu/~hagberg/">http://www2.med.cornell.edu/~hagberg/</A><BR>
  +<STRONG>Company:</STRONG> Cornell Medical College</A><BR>
  +<STRONG>Occupation:</STRONG> User Services Manager<BR>
  +<STRONG>Location:</STRONG> New York, NY, USA<BR>
  +<STRONG>Comments:</STRONG> <BR>
   
   <P>
   
  -<B>Name:</B> Rob Hartill</A><BR>
  -<B>email:</B> <A HREF="mailto:hartill@lanl.gov">hartill@lanl.gov</A><BR>
  -<B>URL:</B> <A HREF="http://www.cm.cf.ac.uk/People/Robert.Hartill.html"> Rob's stuff<BR></A>
  -<B>Company:</B> Los Alamos National Laboratory<BR>
  -<B>Occupation:</B> Post-doc, webmaster, hacker<BR>
  -<B>Location:</B> Los Alamos, New Mexico, Good Old US of A<BR>
  -<B>Comments:</B> err, hummm, none<BR>
  +<STRONG>Name:</STRONG> Rob Hartill</A><BR>
  +<STRONG>email:</STRONG> <A HREF="mailto:hartill@lanl.gov">hartill@lanl.gov</A><BR>
  +<STRONG>URL:</STRONG> <A HREF="http://www.cm.cf.ac.uk/People/Robert.Hartill.html"> Rob's stuff<BR></A>
  +<STRONG>Company:</STRONG> Los Alamos National Laboratory<BR>
  +<STRONG>Occupation:</STRONG> Post-doc, webmaster, hacker<BR>
  +<STRONG>Location:</STRONG> Los Alamos, New Mexico, Good Old US of A<BR>
  +<STRONG>Comments:</STRONG> err, hummm, none<BR>
   
   <P>
   
  -<B>Name:</B> Kipp Jones<BR>
  -<B>email:</B> <A HREF="mailto:kipp@cc.gatech.edu">kipp@cc.gatech.edu</A><BR>
  -<B>URL:</B> <A HREF="http://www.cc.gatech.edu/grads/j/Kipp.Jones/">http://www.cc.gatech.edu/grads/j/Kipp.Jones/</A><BR>
  -<B>Company:</B> Georgia Tech</A><BR>
  -<B>Occupation:</B> Graduate Research Assistant<BR>
  -<B>Location:</B> Atlanta, Ga, USA<BR>
  -<B>Comments:</B> I would like to be involved some of the publishing aspects for www servers.<BR>
  +<STRONG>Name:</STRONG> Kipp Jones<BR>
  +<STRONG>email:</STRONG> <A HREF="mailto:kipp@cc.gatech.edu">kipp@cc.gatech.edu</A><BR>
  +<STRONG>URL:</STRONG> <A HREF="http://www.cc.gatech.edu/grads/j/Kipp.Jones/">http://www.cc.gatech.edu/grads/j/Kipp.Jones/</A><BR>
  +<STRONG>Company:</STRONG> Georgia Tech</A><BR>
  +<STRONG>Occupation:</STRONG> Graduate Research Assistant<BR>
  +<STRONG>Location:</STRONG> Atlanta, Ga, USA<BR>
  +<STRONG>Comments:</STRONG> I would like to be involved some of the publishing aspects for www servers.<BR>
   
   <P>
   
  -<B>Name:</B> Nicolas Pioch<BR>
  -<B>email:</B> <A HREF="mailto:pioch@email.enst.fr">pioch@email.enst.fr</A><BR>
  -<B>URL:</B> <A HREF="http://mistral.enst.fr/">http://mistral.enst.fr/</A><BR>
  -<B>Company:</B> Free mind.</A><BR>
  -<B>Occupation:</B> Too many.<BR>
  -<B>Location:</B> Paris, France, Outside USA<BR>
  -<B>Comments:</B> <BR>
  +<STRONG>Name:</STRONG> Nicolas Pioch<BR>
  +<STRONG>email:</STRONG> <A HREF="mailto:pioch@email.enst.fr">pioch@email.enst.fr</A><BR>
  +<STRONG>URL:</STRONG> <A HREF="http://mistral.enst.fr/">http://mistral.enst.fr/</A><BR>
  +<STRONG>Company:</STRONG> Free mind.</A><BR>
  +<STRONG>Occupation:</STRONG> Too many.<BR>
  +<STRONG>Location:</STRONG> Paris, France, Outside USA<BR>
  +<STRONG>Comments:</STRONG> <BR>
   
   <P>
   
  -<B>Name:</B> David Robinson<BR>
  -<B>email:</B> <A HREF="mailto:drtr@ast.cam.ac.uk">drtr@ast.cam.ac.uk</A><BR>
  -<B>URL:</B><BR>
  -<B>Company:</B> University of Cambridge<BR>
  -<B>Occupation:</B> Astronomer<BR>
  -<B>Location:</B> Cambridge, UK<BR>
  -<B>Comments:</B> <BR>
  +<STRONG>Name:</STRONG> David Robinson<BR>
  +<STRONG>email:</STRONG> <A HREF="mailto:drtr@ast.cam.ac.uk">drtr@ast.cam.ac.uk</A><BR>
  +<STRONG>URL:</STRONG><BR>
  +<STRONG>Company:</STRONG> University of Cambridge<BR>
  +<STRONG>Occupation:</STRONG> Astronomer<BR>
  +<STRONG>Location:</STRONG> Cambridge, UK<BR>
  +<STRONG>Comments:</STRONG> <BR>
   
   <P>
   
  -<B>Name:</B> Cliff Skolnick<BR>
  -<B>email:</B> <A HREF="mailto:cliffs@sun.com">cliffs@sun.com</A><BR>
  -<B>URL:</B> <A HREF="http://www.steam.com/~cliffs/">http://www.steam.com/~cliffs/</A><BR>
  -<B>Company:</B> Sun Microsystems<BR>
  -<B>Occupation:</B> Software Engineer<BR>
  -<B>Location:</B> Mountain View, CA, USA<BR>
  -<B>Comments:</B> <BR>
  +<STRONG>Name:</STRONG> Cliff Skolnick<BR>
  +<STRONG>email:</STRONG> <A HREF="mailto:cliffs@sun.com">cliffs@sun.com</A><BR>
  +<STRONG>URL:</STRONG> <A HREF="http://www.steam.com/~cliffs/">http://www.steam.com/~cliffs/</A><BR>
  +<STRONG>Company:</STRONG> Sun Microsystems<BR>
  +<STRONG>Occupation:</STRONG> Software Engineer<BR>
  +<STRONG>Location:</STRONG> Mountain View, CA, USA<BR>
  +<STRONG>Comments:</STRONG> <BR>
   
   <P>
   
  -<B>Name:</B> Randy Terbush<BR>
  -<B>email:</B> <A HREF="mailto:randy@zyzzyva.com">randy@zyzzyva.com</A><BR>
  -<B>URL:</B> <A HREF="http://www.zyzzyva.com/zyzzyva/">http://www.zyzzyva.com/zyzzyva/</A><BR>
  -<B>Company:</B> Zyzzyva Enterprises</A><BR>
  -<B>Occupation:</B> Internet Services, Sysadmin, Webmaster<BR>
  -<B>Location:</B> Lincoln, NE, USA<BR>
  -<B>Comments:</B> <BR>
  +<STRONG>Name:</STRONG> Randy Terbush<BR>
  +<STRONG>email:</STRONG> <A HREF="mailto:randy@zyzzyva.com">randy@zyzzyva.com</A><BR>
  +<STRONG>URL:</STRONG> <A HREF="http://www.zyzzyva.com/zyzzyva/">http://www.zyzzyva.com/zyzzyva/</A><BR>
  +<STRONG>Company:</STRONG> Zyzzyva Enterprises</A><BR>
  +<STRONG>Occupation:</STRONG> Internet Services, Sysadmin, Webmaster<BR>
  +<STRONG>Location:</STRONG> Lincoln, NE, USA<BR>
  +<STRONG>Comments:</STRONG> <BR>
   
   <P>
   
  -<B>Name:</B> Robert Thau<BR>
  -<B>email:</B> <A HREF="mailto:rst@ai.mit.edu">rst@ai.mit.edu</A><BR>
  -<B>URL:</B> <A HREF="http://www.ai.mit.edu/people/rst/rst.html">http://www.ai.mit.edu/people/rst/rst.html</A><BR>
  -<B>Company:</B> MIT</A><BR>
  -<B>Occupation:</B> grad student<BR>
  -<B>Location:</B> Boston, Mass., USA<BR>
  -<B>Comments:</B> <BR>
  +<STRONG>Name:</STRONG> Robert Thau<BR>
  +<STRONG>email:</STRONG> <A HREF="mailto:rst@ai.mit.edu">rst@ai.mit.edu</A><BR>
  +<STRONG>URL:</STRONG> <A HREF="http://www.ai.mit.edu/people/rst/rst.html">http://www.ai.mit.edu/people/rst/rst.html</A><BR>
  +<STRONG>Company:</STRONG> MIT</A><BR>
  +<STRONG>Occupation:</STRONG> grad student<BR>
  +<STRONG>Location:</STRONG> Boston, Mass., USA<BR>
  +<STRONG>Comments:</STRONG> <BR>
   
   <P>
   
  -<B>Name:</B> Andrew Wilson</A><BR>
  -<B>email:</B> <A HREF="mailto:Andrew.Wilson@cm.cf.ac.uk">Andrew.Wilson@cm.cf.ac.uk</A><BR>
  -<B>URL:</B> <A HREF="http://www.cm.cf.ac.uk/User/Andrew.Wilson/"> http://www.cm.cf.ac.uk/User/Andrew.Wilson/<BR></A>
  -<B>Company:</B><BR>
  -<B>Occupation:</B><BR>
  -<B>Location:</B><BR>
  -<B>Comments:</B><BR>
  +<STRONG>Name:</STRONG> Andrew Wilson</A><BR>
  +<STRONG>email:</STRONG> <A HREF="mailto:Andrew.Wilson@cm.cf.ac.uk">Andrew.Wilson@cm.cf.ac.uk</A><BR>
  +<STRONG>URL:</STRONG> <A HREF="http://www.cm.cf.ac.uk/User/Andrew.Wilson/"> http://www.cm.cf.ac.uk/User/Andrew.Wilson/<BR></A>
  +<STRONG>Company:</STRONG><BR>
  +<STRONG>Occupation:</STRONG><BR>
  +<STRONG>Location:</STRONG><BR>
  +<STRONG>Comments:</STRONG><BR>
   
   <P><HR><P>
   
  
  
  
  1.2       +20 -20    apache-devsite/ports.html
  
  Index: ports.html
  ===================================================================
  RCS file: /export/home/cvs/apache-devsite/ports.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- ports.html	1997/06/17 10:43:31	1.1
  +++ ports.html	1998/02/12 14:39:23	1.2
  @@ -10,11 +10,11 @@
   
   <P>
   
  -<NOTE><B>mod_auth_msql can be excluded from the "all distribution modules
  +<NOTE><STRONG>mod_auth_msql can be excluded from the "all distribution modules
   compile" list since most people do not have MSQL on their systems.
   Likewise, mod_dld is also excluded from this list.  Perhaps the
   "Configuration" file should mention which platforms DLD support exists
  -on.</B></NOTE>
  +on.</STRONG></NOTE>
   
   <P>
   
  @@ -29,17 +29,17 @@
   <TR><TD>DEC OSF/1	<TD>	<TD>	<TD>	<TD>	</TR>
   <TR><TD>DG/UX 5.x	<TD>	<TD>	<TD>	<TD>	</TR>
   <TR><TD>FreeBSD	<TD>Yes	<TD>Yes	<TD>Chuck Murcko	<TD>mod_proxy warning (no error)	</TR>
  -<TR><TD>HPUX 9.x	<TD>Yes	<TD>Yes (except msql, dld, db)	<TD>Alexei	<TD>Warnings:<br>mod_proxy.c:2694: warning: passing arg 2 of `select' from incompatible pointer type
  +<TR><TD>HPUX 9.x	<TD>Yes	<TD>Yes (except msql, dld, db)	<TD>Alexei	<TD>Warnings:<BR>mod_proxy.c:2694: warning: passing arg 2 of `select' from incompatible pointer type
   	</TR>
   <TR><TD>HPUX 10.x	<TD>	<TD>	<TD>	<TD>	</TR>
   <TR><TD>Irix 5.x, gcc	<TD>Yes	<TD>Yes	<TD>Chuck Murcko	<TD>http_main.c: In function `sig_term':
  -http_main.c:904: warning: implicit declaration of function `killpg'<br>
  +http_main.c:904: warning: implicit declaration of function `killpg'<BR>
   http_main.c: In function `standalone_main':
  -http_main.c:1404: warning: implicit declaration of function `bzero'<br>
  +http_main.c:1404: warning: implicit declaration of function `bzero'<BR>
   mod_auth.c: In function `authenticate_basic_user':
  -mod_auth.c:180: warning: implicit declaration of function `crypt'<br>
  +mod_auth.c:180: warning: implicit declaration of function `crypt'<BR>
   mod_proxy.c: In function `connect_handler':
  -mod_proxy.c:2687: warning: implicit declaration of function `bzero'<br>
  +mod_proxy.c:2687: warning: implicit declaration of function `bzero'<BR>
   no mod_auth_db
   </TR>
   <TR><TD>Irix 5.x, SGI cc	<TD>Yes	<TD>Yes	<TD>Mark Cox	<TD>Warnings: http_bprintf.c, line 86: Long double not supported; double assumed.	</TR>
  @@ -56,25 +56,25 @@
   <TR><TD>SCO 5	<TD>	<TD>	<TD>	<TD>	</TR>
   <TR><TD>Sequent	<TD>	<TD>	<TD>	<TD>	</TR>
   <TR><TD>Solaris 2.4, gcc	<TD>Yes	<TD>Yes	<TD>Chuck Murcko	<TD>util.c: In function `get_local_host':
  -util.c:1090: warning: implicit declaration of function `gethostname'<br>
  +util.c:1090: warning: implicit declaration of function `gethostname'<BR>
   mod_auth.c: In function `authenticate_basic_user':
  -mod_auth.c:180: warning: implicit declaration of function `crypt'<br>
  +mod_auth.c:180: warning: implicit declaration of function `crypt'<BR>
   mod_auth_dbm.c: In function `dbm_authenticate_basic_user':
  -mod_auth_dbm.c:170: warning: implicit declaration of function `crypt'<br>
  +mod_auth_dbm.c:170: warning: implicit declaration of function `crypt'<BR>
   mod_cookies.c: In function `make_cookie':
  -mod_cookies.c:133: warning: implicit declaration of function `gettimeofday'<br>
  +mod_cookies.c:133: warning: implicit declaration of function `gettimeofday'<BR>
   mod_proxy.c: In function `cache_check':
   mod_proxy.c:1663: warning: empty body in an else-statement
  -<br>no mod_auth_db	</TR>
  -<TR><TD>Solaris 2.4, Sun cc	<TD>Yes	<TD>Yes	<TD>Chuck Murcko	<TD>"http_main.c", line 1565: warning: Function has no return statement : main<br>
  -"util.c", line 1090: warning: implicitly declaring function to return int: gethostname()<br>
  -"mod_auth.c", line 180: warning: implicitly declaring function to return int: crypt()<br>
  -"mod_auth_dbm.c", line 170: warning: implicitly declaring function to return int: crypt()<br>
  -"mod_cookies.c", line 133: warning: implicitly declaring function to return int:gettimeofday()<br>
  -"mod_proxy.c", line 756: warning: semantics of "<" change in ANSI C; use explicit cast<br>
  -"mod_proxy.c", line 1649: warning: semantics of "<" change in ANSI C; use explicit cast<br>
  +<BR>no mod_auth_db	</TR>
  +<TR><TD>Solaris 2.4, Sun cc	<TD>Yes	<TD>Yes	<TD>Chuck Murcko	<TD>"http_main.c", line 1565: warning: Function has no return statement : main<BR>
  +"util.c", line 1090: warning: implicitly declaring function to return int: gethostname()<BR>
  +"mod_auth.c", line 180: warning: implicitly declaring function to return int: crypt()<BR>
  +"mod_auth_dbm.c", line 170: warning: implicitly declaring function to return int: crypt()<BR>
  +"mod_cookies.c", line 133: warning: implicitly declaring function to return int:gettimeofday()<BR>
  +"mod_proxy.c", line 756: warning: semantics of "<" change in ANSI C; use explicit cast<BR>
  +"mod_proxy.c", line 1649: warning: semantics of "<" change in ANSI C; use explicit cast<BR>
   "mod_proxy.c", line 2658: warning: statement not reached
  -<br>no mod_auth_db	</TR>
  +<BR>no mod_auth_db	</TR>
   <TR><TD>Solaris 2.5, gcc	<TD>	<TD>	<TD>	<TD>	</TR>
   <TR><TD>Solaris 2.5, Sun cc	<TD>Yes	<TD>Yes (except msql, dld, db)	<TD>Alexei	<TD>Warnings: http_main, util, mod_auth, mod_auth_dbm, mod_cookies, mod_proxy
   	</TR>
  
  
  
  1.6       +1 -1      apache-devsite/styleguide.html
  
  Index: styleguide.html
  ===================================================================
  RCS file: /export/home/cvs/apache-devsite/styleguide.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- styleguide.html	1998/01/12 14:18:06	1.5
  +++ styleguide.html	1998/02/12 14:39:23	1.6
  @@ -23,7 +23,7 @@
   
   <P>This style can be generated with the following arguments to indent:
   
  -<P><UL><code>-i4 -npsl -di0 -br -nce -d0 -cli0 -npcs -nfc1</code></UL>
  +<P><UL><CODE>-i4 -npsl -di0 -br -nce -d0 -cli0 -npcs -nfc1</CODE></UL>
   
   <H2>The Guidelines</H2>
     <UL>
  
  
  
  1.3       +3 -3      apache-devsite/todo.html
  
  Index: todo.html
  ===================================================================
  RCS file: /export/home/cvs/apache-devsite/todo.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- todo.html	1998/01/12 14:27:36	1.2
  +++ todo.html	1998/02/12 14:39:24	1.3
  @@ -4,7 +4,7 @@
   
   <H2>Apache Bugs List / To Do List / Wish List</H2>
   
  -<B>BUGS</B>
  +<STRONG>BUGS</STRONG>
   
   <UL> 
   
  @@ -16,7 +16,7 @@
   
   </UL>
   
  -<B>To Do List</B>
  +<STRONG>To Do List</STRONG>
   
   <UL>
   
  @@ -33,7 +33,7 @@
   
   </UL>
   
  -<B>Wish List</B>
  +<STRONG>Wish List</STRONG>
   
   <UL>
   
  
  
  
  1.5       +8 -8      apache-devsite/voting.html
  
  Index: voting.html
  ===================================================================
  RCS file: /export/home/cvs/apache-devsite/voting.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- voting.html	1998/01/09 16:26:02	1.4
  +++ voting.html	1998/02/12 14:39:24	1.5
  @@ -51,7 +51,7 @@
   </DL>
   
   <HR SIZE=6>
  -<H2><IMG SRC="images/apache_feather_bullet.gif" alt="o ">
  +<H2><IMG SRC="images/apache_feather_bullet.gif" ALT="o ">
   Issues and Action Items</H2>
   
   Many issues will be encountered by the project, each resulting in zero
  @@ -67,7 +67,7 @@
     <DT><STRONG>Code Changes</STRONG></DT>
     <DD>Code changes require peer review and testing over a wide range
         of server platforms.  Therefore, all code changes must pass through
  -      a formal "patch vote", as described <a href="#patchvote">below</A>.
  +      a formal "patch vote", as described <A HREF="#patchvote">below</A>.
         All those participating in a patch vote must be willing and able
         to test the patched system.</DD>
   
  @@ -90,11 +90,11 @@
         but group members who do not agree with a particular plan,
         or think an alternate plan would be better, are obligated to
         inform the group of their feelings.  In general, it is always
  -      better to hear about alternate plans <strong>prior</strong> to
  +      better to hear about alternate plans <STRONG>prior</STRONG> to
         spending time on less adequate solutions.
   </DL>
   
  -<H2><IMG SRC="images/apache_feather_bullet.gif" alt="o ">
  +<H2><IMG SRC="images/apache_feather_bullet.gif" ALT="o ">
   Casting Votes</H2>
   
   Anyone on the mailing list may vote on any issue.  However, the act
  @@ -116,7 +116,7 @@
          too many people abstain.
     </DD><P>
     <DT><STRONG>-1</STRONG></DT>
  -  <DD> No, I <strong>veto</strong> this action.  All vetos must include
  +  <DD> No, I <STRONG>veto</STRONG> this action.  All vetos must include
          an explanation of why the veto is appropriate.  A veto with
          no explanation is void.
     </DD>
  @@ -125,7 +125,7 @@
   <P>All votes must be sent to the mailing list.
   
   
  -<H2><IMG SRC="images/apache_feather_bullet.gif" alt="o ">
  +<H2><IMG SRC="images/apache_feather_bullet.gif" ALT="o ">
   <A NAME="patchvote">Formal Patch Votes</A></H2>
   <P>
   As mentioned above, changes to the source code require peer review
  @@ -257,7 +257,7 @@
   on a timetable and announce it on the mailing list.  The important
   part of the timetable is the vote deadline, which specifies when
   the votes will be tallied and the new version can be built.
  -Unless it is an <A href="#emergency">emergency</A>, the initial
  +Unless it is an <A HREF="#emergency">emergency</A>, the initial
   deadline should be at least three days after the announcement.</P>
   
   <P>The vote deadline can be moved if, using the same voting rules
  @@ -338,7 +338,7 @@
   should be reported to the group and any public release postponed until
   a majority decision on how to rectify the problem is obtained.</P>
   
  -<H3><A name="emergency">Emergency Patch Votes</A></H3>
  +<H3><A NAME="emergency">Emergency Patch Votes</A></H3>
   
   <P>In the event of an emergency patch/vote session to fix a security
   problem, the group may need to bypass the normal operating procedures
  
  
  

Mime
View raw message