httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rodent of Unusual Size <c...@hyperreal.com>
Subject cvs commit: apache/htdocs/manual/misc FAQ.html
Date Sun, 20 Apr 1997 15:40:08 GMT
coar        97/04/20 08:40:07

  Modified:    htdocs/manual/misc  FAQ.html
  Log:
  	Cleaned up some <PRE> sections to use <CODE> and <DL> instead;
  	Lynx (2.7.1) wasn't indenting properly.
  
  Revision  Changes    Path
  1.27      +48 -22    apache/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===================================================================
  RCS file: /export/home/cvs/apache/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.26
  retrieving revision 1.27
  diff -C3 -r1.26 -r1.27
  *** FAQ.html	1997/04/20 02:43:12	1.26
  --- FAQ.html	1997/04/20 15:40:06	1.27
  ***************
  *** 8,14 ****
    <!--#include virtual="header.html" -->
    <H1>Apache Server Frequently Asked Questions</H1>
    <P>
  ! $Revision: 1.26 $ ($Date: 1997/04/20 02:43:12 $)
    </P>
    <P>
    If you are reading a text-only version of this FAQ, you may find numbers
  --- 8,14 ----
    <!--#include virtual="header.html" -->
    <H1>Apache Server Frequently Asked Questions</H1>
    <P>
  ! $Revision: 1.27 $ ($Date: 1997/04/20 15:40:06 $)
    </P>
    <P>
    If you are reading a text-only version of this FAQ, you may find numbers
  ***************
  *** 351,361 ****
        If your problem involves the server crashing and generating a core
        dump, please include a backtrace (if possible).  As an example,
        </P>
  !     <PRE>
  !      # cd <EM>ServerRoot</EM>
  !      # dbx httpd core
  !      (dbx) where
  !     </PRE>
        <P>
        (Substitute the appropiate locations for your
        <SAMP>ServerRoot</SAMP> and your <SAMP>httpd</SAMP> and
  --- 351,368 ----
        If your problem involves the server crashing and generating a core
        dump, please include a backtrace (if possible).  As an example,
        </P>
  !     <P>
  !     <CODE>
  !      <DL>
  !       <DD># cd <EM>ServerRoot</EM>
  !       </DD>
  !       <DD># dbx httpd core
  !       </DD>
  !       <DD>(dbx) where
  !       </DD>
  !      </DL>
  !     </CODE>
  !     </P>
        <P>
        (Substitute the appropiate locations for your
        <SAMP>ServerRoot</SAMP> and your <SAMP>httpd</SAMP> and
  ***************
  *** 414,427 ****
      <A
       HREF="../mod/mod_mime.html#addhandler"
      ><SAMP>AddHandler</SAMP></A>
  -   </P>
      directive.
      <OL>
       <LI>In an appropriate section of your server configuration files, add
        a line such as
  !     <PRE>
  !      AddHandler cgi-script .cgi
  !     </PRE>
        The server will then recognise that all files in that location (and
        its logical descendants) that end in &quot;<SAMP>.cgi</SAMP>&quot;
        are script files, not documents.
  --- 421,437 ----
      <A
       HREF="../mod/mod_mime.html#addhandler"
      ><SAMP>AddHandler</SAMP></A>
      directive.
  +   </P>
      <OL>
       <LI>In an appropriate section of your server configuration files, add
        a line such as
  !     <P>
  !     <DL>
  !      <DD><CODE>AddHandler cgi-script .cgi</CODE>
  !      </DD>
  !     </DL>
  !     </P>
        The server will then recognise that all files in that location (and
        its logical descendants) that end in &quot;<SAMP>.cgi</SAMP>&quot;
        are script files, not documents.
  ***************
  *** 448,458 ****
      disabled buffering; if you insert the following statements before your
      first <SAMP>print</SAMP> statement, this will probably go away.
      </P>
  !   <PRE>
  !    $cfh = select (STDOUT);
  !    $| = 1;
  !    select ($cfh);
  !   </PRE>
      <P>
      If your script isn't written in Perl, do the equivalent thing for
      whatever language you <EM>are</EM> using (<EM>e.g.</EM>, for
C, call 
  --- 458,475 ----
      disabled buffering; if you insert the following statements before your
      first <SAMP>print</SAMP> statement, this will probably go away.
      </P>
  !   <P>
  !   <CODE>
  !    <DL>
  !     <DD>$cfh = select (STDOUT);
  !     </DD>
  !     <DD>$| = 1;
  !     </DD>
  !     <DD>select ($cfh);
  !     </DD>
  !    </DL>
  !   </CODE>
  !   </P>
      <P>
      If your script isn't written in Perl, do the equivalent thing for
      whatever language you <EM>are</EM> using (<EM>e.g.</EM>, for
C, call 
  ***************
  *** 500,508 ****
         HREF="../mod/mod_mime.html#addhandler"
        ><SAMP>AddHandler</SAMP></A>
        directive:
  !     <PRE>
  !      AddHandler server-parsed .shtml
  !     </PRE>
        This indicates that all files ending in &quot;.shtml&quot; in that
        location (or its descendants) should be parsed.  Note that using
        &quot;.html&quot; will cause all normal HTML files to be parsed,
  --- 517,528 ----
         HREF="../mod/mod_mime.html#addhandler"
        ><SAMP>AddHandler</SAMP></A>
        directive:
  !     <P>
  !     <DL>
  !      <DD><CODE>AddHandler server-parsed .shtml</CODE>
  !      </DD>
  !     </DL>
  !     </P>
        This indicates that all files ending in &quot;.shtml&quot; in that
        location (or its descendants) should be parsed.  Note that using
        &quot;.html&quot; will cause all normal HTML files to be parsed,
  ***************
  *** 669,678 ****
      configuration files for something that resembles the following and
      would affect the location where the POST-handling script resides:
      </P>
  !   <PRE>
  !    &lt;Limit GET&gt;
  !       :
  !   </PRE>
      <P>
      Change that to <SAMP>&lt;Limit GET POST&gt;</SAMP> and the problem
      will probably go away.
  --- 689,704 ----
      configuration files for something that resembles the following and
      would affect the location where the POST-handling script resides:
      </P>
  !   <P>
  !   <CODE>
  !    <DL>
  !     <DD>&lt;Limit GET&gt;
  !     </DD>
  !     <DD>&nbsp;&nbsp;&nbsp;&nbsp;:
  !     </DD>
  !    </DL>
  !   </CODE>
  !   </P>
      <P>
      Change that to <SAMP>&lt;Limit GET POST&gt;</SAMP> and the problem
      will probably go away.
  
  
  

Mime
View raw message