httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@hyperreal.org
Subject cvs commit: apache-1.3/htdocs/manual/vhosts details.html host.html virtual-host.html
Date Thu, 17 Sep 1998 14:52:05 GMT
coar        98/09/17 07:52:04

  Modified:    htdocs/manual suexec.html upgrading_to_1_3.html
               htdocs/manual/misc howto.html
               htdocs/manual/vhosts details.html host.html
                        virtual-host.html
  Log:
  	Some more consistency (cgi -> CGI) fixes, and shortened long lines.
  	(There are about 200 more >80 lines in the dos, but I haven't the
  	time now to fix 'em.  Oh well.)
  
  Revision  Changes    Path
  1.21      +2 -1      apache-1.3/htdocs/manual/suexec.html
  
  Index: suexec.html
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/suexec.html,v
  retrieving revision 1.20
  retrieving revision 1.21
  diff -u -r1.20 -r1.21
  --- suexec.html	1998/07/30 16:42:47	1.20
  +++ suexec.html	1998/09/17 14:52:01	1.21
  @@ -400,7 +400,8 @@
   
   <P ALIGN="LEFT">
   If your installation requires location of the wrapper program in a different
  -directory, either add <CODE>-DSUEXEC_BIN=\"<EM>&lt;/your/path/to/suexec&gt;</EM>\"</CODE>
  +directory, either add
  +<CODE>-DSUEXEC_BIN=\"<EM>&lt;/your/path/to/suexec&gt;</EM>\"</CODE>
   to your CFLAGS (or edit src/include/httpd.h) and recompile your Apache server.
   See <A HREF="install.html">Compiling and Installing Apache</A>
   (and the <SAMP>INSTALL</SAMP> file in the source distribution)
  
  
  
  1.32      +2 -1      apache-1.3/htdocs/manual/upgrading_to_1_3.html
  
  Index: upgrading_to_1_3.html
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/upgrading_to_1_3.html,v
  retrieving revision 1.31
  retrieving revision 1.32
  diff -u -r1.31 -r1.32
  --- upgrading_to_1_3.html	1998/09/17 14:14:49	1.31
  +++ upgrading_to_1_3.html	1998/09/17 14:52:01	1.32
  @@ -233,7 +233,8 @@
      To avoid symbol clashes with third-party code compiled into the server, the
      general prefix `<CODE>ap_</CODE>' was globally applied to the following
      classes of symbols: Apache provided general functions (<EM>e.g.</EM>,
  -   <CODE>ap_cpystrn</CODE>), public API functions (<EM>e.g.</EM>,
<CODE>palloc</CODE>,
  +   <CODE>ap_cpystrn</CODE>), public API functions (<EM>e.g.</EM>,
  +   <CODE>palloc</CODE>,
      <CODE>bgets</CODE>) and private functions which can't be made static
      (because of cross-object usage) but should be (<EM>e.g.</EM>,
      <CODE>new_connection</CODE>).  For backward source compatibility with
  
  
  
  1.9       +6 -4      apache-1.3/htdocs/manual/misc/howto.html
  
  Index: howto.html
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/howto.html,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- howto.html	1998/09/17 14:14:53	1.8
  +++ howto.html	1998/09/17 14:52:02	1.9
  @@ -60,13 +60,14 @@
   "http://www.apache.org".
   
   The second option is to set up a <CODE>ScriptAlias</CODE> pointing to
  -a <STRONG>cgi script</STRONG> which outputs a 301 or 302 status and the
  +a <STRONG>CGI script</STRONG> which outputs a 301 or 302 status and the
   location
   of the other server.</P>
   
  -<P>By using a <STRONG>cgi-script</STRONG> you can intercept various requests
  +<P>By using a <STRONG>CGI script</STRONG> you can intercept various requests
   and
  -treat them specially, <EM>e.g.</EM>, you might want to intercept <STRONG>POST</STRONG>
  +treat them specially, <EM>e.g.</EM>, you might want to intercept
  +<STRONG>POST</STRONG>
   requests, so that the client isn't redirected to a script on the other
   server which expects POST information (a redirect will lose the POST
   information.) You might also want to use a CGI script if you don't
  @@ -108,7 +109,8 @@
   <P>The correct procedure is to move the logfile, then signal Apache to tell
   it to reopen the logfiles.</P>
   
  -<P>Apache is signaled using the <STRONG>SIGHUP</STRONG> (-1) signal.
<EM>e.g.</EM>
  +<P>Apache is signaled using the <STRONG>SIGHUP</STRONG> (-1) signal.
  +<EM>e.g.</EM>
   <BLOCKQUOTE><CODE>
   mv access_log access_log.old<BR>
   kill -1 `cat httpd.pid`
  
  
  
  1.9       +3 -2      apache-1.3/htdocs/manual/vhosts/details.html
  
  Index: details.html
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/vhosts/details.html,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- details.html	1998/09/17 14:15:02	1.8
  +++ details.html	1998/09/17 14:52:03	1.9
  @@ -307,7 +307,7 @@
       number for the request. The request is only caught if the port number
       to which the client sent the request matches the port number of your
       <CODE>_default_</CODE> vhost which is your standard <CODE>Port</CODE>
  -    by default. A wildcard port can be specified (<EM>i.e.</EM>
  +    by default. A wildcard port can be specified (<EM>i.e.</EM>,
       <CODE>_default_:*</CODE>) to catch requests to any available port.
       <P>
       
  @@ -322,7 +322,8 @@
   <LI>A <CODE>_default_</CODE> vhost or the main_server is <EM>never</EM>
       matched for a request with an unknown or missing <CODE>Host:</CODE> header
       field if the client connected to an address (and port) which is used
  -    for name-based vhosts, <EM>e.g.</EM>, in a <CODE>NameVirtualHost</CODE>
directive.
  +    for name-based vhosts, <EM>e.g.</EM>, in a <CODE>NameVirtualHost</CODE>
  +    directive.
       <P>
       
   <LI>You should never specify DNS names in <CODE>VirtualHost</CODE>
  
  
  
  1.8       +2 -2      apache-1.3/htdocs/manual/vhosts/host.html
  
  Index: host.html
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/vhosts/host.html,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- host.html	1998/09/17 14:15:02	1.7
  +++ host.html	1998/09/17 14:52:03	1.8
  @@ -123,8 +123,8 @@
   private.foo.com</CODE> header.  It is important to note that this
   condition exists only if you only implement this policy at the IP
   layer - all security controls used by Apache (<EM>i.e.</EM>, <A
  -HREF="../mod/mod_access.html">allow, deny from,</A> <EM>etc.</EM>)
are consistently
  -respected.
  +HREF="../mod/mod_access.html">allow, deny from,</A> <EM>etc.</EM>)
are
  +consistently respected.
   
   <H2>Compatibility with Older Browsers</H2>
   
  
  
  
  1.8       +4 -3      apache-1.3/htdocs/manual/vhosts/virtual-host.html
  
  Index: virtual-host.html
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/vhosts/virtual-host.html,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- virtual-host.html	1998/07/16 22:59:58	1.7
  +++ virtual-host.html	1998/09/17 14:52:03	1.8
  @@ -66,7 +66,8 @@
   Use multiple daemons when:
   <UL>
   <LI>The different virtual hosts need very different httpd configurations, such
  -   as different values for: <A HREF="../mod/core.html#servertype">ServerType</A>,
  +   as different values for:
  +   <A HREF="../mod/core.html#servertype">ServerType</A>,
      <A HREF="../mod/core.html#user">User</A>,
      <A HREF="../mod/core.html#group">Group</A>,
      <A HREF="../mod/mod_mime.html#typesconfig">TypesConfig</A> or
  @@ -203,5 +204,5 @@
   The latter will probably manifest itself in a later version of Apache.
   
   <!--#include virtual="footer.html" -->
  -</BODY></HTML>
  -
  +</BODY>
  +</HTML>
  
  
  

Mime
View raw message