httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexei Kosut <ako...@hyperreal.com>
Subject cvs commit: apache/htdocs/manual/mod mod_cgi.html mod_log_config.html mod_usertrack.html
Date Mon, 09 Dec 1996 02:05:02 GMT
akosut      96/12/08 18:05:01

  Modified:    htdocs/manual/mod  mod_cgi.html mod_log_config.html
                        mod_usertrack.html
  Log:
  Fix some typos. Make some clarifications in mod_usertrack.html (and
  put the directives in alphabetical order).
  
  Submitted by by: WWW server manager <webadm@info.cam.ac.uk>
  
  Revision  Changes    Path
  1.6       +3 -3      apache/htdocs/manual/mod/mod_cgi.html
  
  Index: mod_cgi.html
  ===================================================================
  RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_cgi.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -C3 -r1.5 -r1.6
  *** mod_cgi.html	1996/12/02 18:14:03	1.5
  --- mod_cgi.html	1996/12/09 02:04:55	1.6
  ***************
  *** 73,79 ****
      %% <i>HTTP-status</i> <i>CGI-script-filename</i>
    </pre>
    
  ! If the error is the that CGI script cannot be run, the log file will
    contain
    an extra two lines:
    
  --- 73,79 ----
      %% <i>HTTP-status</i> <i>CGI-script-filename</i>
    </pre>
    
  ! If the error is that CGI script cannot be run, the log file will
    contain
    an extra two lines:
    
  ***************
  *** 82,88 ****
      <i>error-message</i>
    </pre>
    
  ! Alternatively, if the error is the result of the script returning the
    incorrect header information (often due to a bug in the script), the
    following information is logged:
    
  --- 82,88 ----
      <i>error-message</i>
    </pre>
    
  ! Alternatively, if the error is the result of the script returning
    incorrect header information (often due to a bug in the script), the
    following information is logged:
    
  ***************
  *** 146,152 ****
    <b>Status:</b> mod_cgi
    <p>
    
  ! The size of any PUR or POST entity body that is logged to the file is
    limited, to prevent the log file growing too big too quickly if large
    bodies are being received. By default, up to 1024 bytes are logged,
    but this can be changed with this directive.
  --- 146,152 ----
    <b>Status:</b> mod_cgi
    <p>
    
  ! The size of any PUT or POST entity body that is logged to the file is
    limited, to prevent the log file growing too big too quickly if large
    bodies are being received. By default, up to 1024 bytes are logged,
    but this can be changed with this directive.
  
  
  
  1.7       +3 -3      apache/htdocs/manual/mod/mod_log_config.html
  
  Index: mod_log_config.html
  ===================================================================
  RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_log_config.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -C3 -r1.6 -r1.7
  *** mod_log_config.html	1996/12/02 18:14:08	1.6
  --- mod_log_config.html	1996/12/09 02:04:56	1.7
  ***************
  *** 20,26 ****
    to create a log file, <code>LogFormat</code> to set a custom format,
    and <code>CustomLog</code> to define a log file and format in one go.
    The <code>TransferLog</code> and <code>CustomLog</code> directives
can
  ! be use multiple times in each server to cause each request to be
    logged to multiple files.
    <P>
    
  --- 20,26 ----
    to create a log file, <code>LogFormat</code> to set a custom format,
    and <code>CustomLog</code> to define a log file and format in one go.
    The <code>TransferLog</code> and <code>CustomLog</code> directives
can
  ! be used multiple times in each server to cause each request to be
    logged to multiple files.
    <P>
    
  ***************
  *** 29,36 ****
    <ul>
    <li>This module is based on mod_log_config distributed with
    previous Apache releases, now updated to handle multiple logs.
  ! There is now no need to re-configure Apache to get use
  ! configuration log formats.
    
    <li>The module also implements the <code>CookieLog</code> directive,
    used to log user-tracking information created by <a
  --- 29,36 ----
    <ul>
    <li>This module is based on mod_log_config distributed with
    previous Apache releases, now updated to handle multiple logs.
  ! There is now no need to re-configure Apache to use configuration log
  ! formats.
    
    <li>The module also implements the <code>CookieLog</code> directive,
    used to log user-tracking information created by <a
  
  
  
  1.7       +16 -13    apache/htdocs/manual/mod/mod_usertrack.html
  
  Index: mod_usertrack.html
  ===================================================================
  RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_usertrack.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -C3 -r1.6 -r1.7
  *** mod_usertrack.html	1996/12/05 06:26:26	1.6
  --- mod_usertrack.html	1996/12/09 02:04:56	1.7
  ***************
  *** 40,51 ****
    <h2>Directives</h2>
    
    <ul>
  - <li><a href="#cookieenable">CookieTracking</a>
    <li><a href="#cookieexpires">CookieExpires</a>
    </ul>
    
    <hr>
    
    <a name="cookieexpires"><h2>CookieTracking</h2></A>
    <strong>Syntax:</strong> CookieTracking <em>on | off</em><br>
    <strong>Context:</strong> server config, virtual host, directory,
  --- 40,66 ----
    <h2>Directives</h2>
    
    <ul>
    <li><a href="#cookieexpires">CookieExpires</a>
  + <li><a href="#cookietracking">CookieTracking</a>
    </ul>
    
    <hr>
    
  + <a name="cookieexpires"><h2>CookieExpires</h2></A>
  + <strong>Syntax:</strong> CookieExpires <em>expiry-period</em><br>
  + <strong>Context:</strong> server config, virtual host<br>
  + <strong>Status:</strong> optional<br>
  + <strong>Module:</strong> mod_usertrack<p>
  + 
  + When used, this directive sets an expiry time on the cookie generated
  + by the usertrack module. The <i>expiry-period</i> can be given either
  + as a number of seconds, or in the format such as "2 weeks 3 days 7
  + hours".  Valid denominations are: years, months, weeks, hours, minutes
  + and seconds.
  + 
  + <p>If this directive is not used, cookies last only for the current
  + browser session.</p>
  + 
    <a name="cookieexpires"><h2>CookieTracking</h2></A>
    <strong>Syntax:</strong> CookieTracking <em>on | off</em><br>
    <strong>Context:</strong> server config, virtual host, directory,
  ***************
  *** 59,76 ****
    requests. This directive can be used to turn this behavior on or off
    on a per-server or per-directory basis.  By default, compiling
    mod_usertrack will not activate cookies.
  - 
  - <a name="cookieexpires"><h2>CookieExpires</h2></A>
  - <strong>Syntax:</strong> CookieExpires <em>expiry-period</em><br>
  - <strong>Context:</strong> server config, virtual host<br>
  - <strong>Status:</strong> optional<br>
  - <strong>Module:</strong> mod_usertrack<p>
  - 
  - When used, this directive sets an expiry time on the cookie generated
  - by the usertrack module. The <i>expiry-period</i> can be given either
  - as a number of seconds, or in the format such as "2 weeks 3 days 7
  - hours".  Valid denominations are: years, months, weeks, hours, minutes
  - and seconds.
    
    
    <!--#include virtual="footer.html" -->
  --- 74,79 ----
  
  
  

Mime
View raw message