httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From n.@apache.org
Subject cvs commit: httpd-2.0/docs/manual/mod mod_include.html.en quickreference.html.de quickreference.html.en quickreference.html.ru.koi8-r
Date Mon, 30 Jun 2003 01:24:03 GMT
nd          2003/06/29 18:24:02

  Modified:    docs/manual Tag: APACHE_2_0_BRANCH bind.html.en
                        cgi_path.html.en custom-error.html.en env.html.en
                        filter.html.en handler.html.en logs.html.en
                        suexec.html.en
               docs/manual/mod Tag: APACHE_2_0_BRANCH mod_include.html.en
                        quickreference.html.de quickreference.html.en
                        quickreference.html.ru.koi8-r
  Log:
  update transformation
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.26.2.5  +3 -3      httpd-2.0/docs/manual/bind.html.en
  
  Index: bind.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/bind.html.en,v
  retrieving revision 1.26.2.4
  retrieving revision 1.26.2.5
  diff -u -r1.26.2.4 -r1.26.2.5
  --- bind.html.en	29 May 2003 19:29:34 -0000	1.26.2.4
  +++ bind.html.en	30 Jun 2003 01:23:59 -0000	1.26.2.5
  @@ -33,10 +33,10 @@
   <div class="section">
   <h2><a name="overview" id="overview">Overview</a></h2>
       
  -    
  +
       <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="./mod/core.html">core</a></code></li><li><code class="module"><a href="./mod/mpm_common.html">mpm_common</a></code></li></ul></td><td><ul><li><code class="directive"><a href="./mod/core.html#virtualhost">&lt;VirtualHost&gt;</a></code></li><li><code class="directive"><a href="./mod/mpm_common.html#listen">Listen</a></code></li></ul></td></tr></table>
  -    
  -    
  +
  +
       <p>When Apache starts, it binds to some port and address on
       the local machine and waits for incoming requests. By default,
       it listens to all addresses on the machine.  However, it needs to
  
  
  
  1.10.2.3  +1 -1      httpd-2.0/docs/manual/cgi_path.html.en
  
  Index: cgi_path.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/cgi_path.html.en,v
  retrieving revision 1.10.2.2
  retrieving revision 1.10.2.3
  diff -u -r1.10.2.2 -r1.10.2.3
  --- cgi_path.html.en	29 May 2003 19:29:34 -0000	1.10.2.2
  +++ cgi_path.html.en	30 Jun 2003 01:23:59 -0000	1.10.2.3
  @@ -50,7 +50,7 @@
       <div class="example"><p><code>
         Alias /cgi-ralph /usr/local/httpd/cgi-bin/user.cgi/ralph
       </code></p></div>    
  -    
  +
       <p>In this case, <code>user.cgi</code> is the CGI script, the
       "/ralph" is information to be passed onto the CGI. If this
       configuration was in place, and a request came for
  
  
  
  1.18.2.5  +31 -31    httpd-2.0/docs/manual/custom-error.html.en
  
  Index: custom-error.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/custom-error.html.en,v
  retrieving revision 1.18.2.4
  retrieving revision 1.18.2.5
  diff -u -r1.18.2.4 -r1.18.2.5
  --- custom-error.html.en	29 May 2003 19:29:34 -0000	1.18.2.4
  +++ custom-error.html.en	30 Jun 2003 01:23:59 -0000	1.18.2.5
  @@ -25,10 +25,10 @@
   
       <p>Additional functionality allows webmasters to configure the response 
       of Apache to some error or problem.</p>
  -    
  +
       <p>Customizable responses can be defined to be activated in the event of 
       a server detected error or problem.</p>
  -    
  +
       <p>If a script crashes and produces a "500 Server Error" response, 
       then this response can be replaced with either some friendlier text or by 
       a redirection to another URL (local or external).</p>
  @@ -41,36 +41,36 @@
   <div class="section">
   <h2><a name="behavior" id="behavior">Behavior</a></h2>
       
  -    
  +
       <h3>Old Behavior</h3>
         
  -      
  +
         <p>NCSA httpd 1.3 would return some boring old error/problem message 
         which would often be meaningless to the user, and would provide no 
         means of logging the symptoms which caused it.</p>
       
  -    
  +
       <h3>New Behavior</h3>
         
  -      
  +
         <p>The server can be asked to:</p>
  -      
  +
         <ol>
           <li>Display some other text, instead of the NCSA hard coded 
           messages, or</li>
  -      
  +
           <li>redirect to a local URL, or</li>
  -      
  +
           <li>redirect to an external URL.</li>
         </ol>
  -      
  +
         <p>Redirecting to another URL can be useful, but only if some 
         information can be passed which can then be used to explain and/or log 
         the error/problem more clearly.</p>
  -      
  +
         <p>To achieve this, Apache will define new CGI-like environment 
         variables:</p>
  -      
  +
         <div class="example"><p><code>
           REDIRECT_HTTP_ACCEPT=*/*, image/gif, image/x-xbitmap, 
               image/jpeg<br />
  @@ -85,9 +85,9 @@
           REDIRECT_SERVER_SOFTWARE=Apache/0.8.15<br />
           REDIRECT_URL=/cgi-bin/buggy.pl
         </code></p></div>
  -      
  +
         <p>Note the <code>REDIRECT_</code> prefix.</p>
  -      
  +
         <p>At least <code>REDIRECT_URL</code> and
         <code>REDIRECT_QUERY_STRING</code> will be passed to the
         new URL (assuming it's a cgi-script or a cgi-include). The
  @@ -102,13 +102,13 @@
   <div class="section">
   <h2><a name="configuration" id="configuration">Configuration</a></h2>
       
  -    
  +
       <p>Use of <code class="directive"><a href="./mod/core.html#errordocument">ErrorDocument</a></code> is enabled 
       for .htaccess files when the 
       <code class="directive"><a href="./mod/core.html#allowoverride">AllowOverride</a></code> is set accordingly.</p>
  -    
  +
       <p>Here are some examples...</p>
  -    
  +
       <div class="example"><p><code>
         ErrorDocument 500 /cgi-bin/crash-recover <br />
         ErrorDocument 500 "Sorry, our script crashed. Oh dear" <br />
  @@ -116,44 +116,44 @@
         ErrorDocument 404 /Lame_excuses/not_found.html <br />
         ErrorDocument 401 /Subscription/how_to_subscribe.html
       </code></p></div>
  -    
  +
       <p>The syntax is,</p>
  -    
  +
       <div class="example"><p><code>
         ErrorDocument &lt;3-digit-code&gt; &lt;action&gt;
       </code></p></div>
  -    
  +
       <p>where the action can be,</p>
  -    
  +
       <ol>
         <li>Text to be displayed. Prefix the text with a quote
         ("). Whatever follows the quote is displayed. <em>Note:
         the (") prefix isn't displayed.</em></li>
  -    
  +
         <li>An external URL to redirect to.</li>
  -    
  +
         <li>A local URL to redirect to.</li>
       </ol>
     </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
   <div class="section">
   <h2><a name="custom" id="custom">Custom Error Responses and Redirects</a></h2>
       
  -    
  +
       <p>Apache's behavior to redirected URLs has been modified so
       that additional environment variables are available to a
       script/server-include.</p>
  -    
  +
       <h3>Old behavior</h3>
         
  -    
  +
         <p>Standard CGI vars were made available to a script which
         has been redirected to. No indication of where the
         redirection came from was provided.</p>
       
  -    
  +
       <h3>New behavior</h3>
         
  -    
  +
         <p>A new batch of environment variables will be initialized
         for use by a script which has been redirected to. Each new
         variable will have the prefix <code>REDIRECT_</code>.
  @@ -166,21 +166,21 @@
         and <code>REDIRECT_STATUS</code> to help the script trace its
         origin. Both the original URL and the URL being redirected to
         can be logged in the access log.</p>
  -    
  +
         <p>If the ErrorDocument specifies a local redirect to a CGI
         script, the script should include a "<code>Status:</code>"
         header field in its output in order to ensure the propagation
         all the way back to the client of the error condition that
         caused it to be invoked. For instance, a Perl ErrorDocument
         script might include the following:</p>
  -    
  +
         <div class="example"><p><code>
           ... <br />
           print  "Content-type: text/html\n"; <br />
           printf "Status: %s Condition Intercepted\n", $ENV{"REDIRECT_STATUS"}; <br />
           ...
         </code></p></div>
  -    
  +
         <p>If the script is dedicated to handling a particular error
         condition, such as <code>404&nbsp;Not&nbsp;Found</code>, it can
         use the specific code and error text instead.</p>
  
  
  
  1.33.2.6  +45 -45    httpd-2.0/docs/manual/env.html.en
  
  Index: env.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/env.html.en,v
  retrieving revision 1.33.2.5
  retrieving revision 1.33.2.6
  diff -u -r1.33.2.5 -r1.33.2.6
  --- env.html.en	29 May 2003 19:29:35 -0000	1.33.2.5
  +++ env.html.en	30 Jun 2003 01:23:59 -0000	1.33.2.6
  @@ -30,7 +30,7 @@
       also used as a mechanism to communicate with external programs
       such as CGI scripts. This document discusses different ways to
       manipulate and use these variables.</p>
  -        
  +
       <p>Although these variables are referred to as <em>environment
       variables</em>, they are not the same as the environment
       variables controlled by the underlying operating system.
  @@ -53,19 +53,19 @@
   <h2><a name="setting" id="setting">Setting Environment Variables</a></h2>
       
       <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="./mod/mod_env.html">mod_env</a></code></li><li><code class="module"><a href="./mod/mod_rewrite.html">mod_rewrite</a></code></li><li><code class="module"><a href="./mod/mod_setenvif.html">mod_setenvif</a></code></li><li><code class="module"><a href="./mod/mod_unique_id.html">mod_unique_id</a></code></li></ul></td><td><ul><li><code class="directive"><a href="./mod/mod_setenvif.html#browsermatch">BrowserMatch</a></code></li><li><code class="directive"><a href="./mod/mod_setenvif.html#browsermatchnocase">BrowserMatchNoCase</a></code></li><li><code class="directive"><a href="./mod/mod_env.html#passenv">PassEnv</a></code></li><li><code class="directive"><a href="./mod/mod_rewrite.html#rewriterule">RewriteRule</a></code></li><li><code class="directive"><a href="./mod/mod_env.html#setenv">SetEnv</a></code></li><li><code class="directive"><a href="./mod/mod_setenvif.html#setenvif">SetEnvIf</a></code></li><li><code class="directive"><a href="./mod/mod_setenvif.html#setenvifnocase">SetEnvIfNoCase</a></code></li><li><code class="directive"><a href="./mod/mod_env.html#unsetenv">UnsetEnv</a></code></li></ul></td></tr></table>
  -    
  +
       <h3><a name="basic-manipulation" id="basic-manipulation">Basic Environment Manipulation</a></h3>
           
  -    
  +
           <p>The most basic way to set an environment variable in Apache
           is using the unconditional <code class="directive"><a href="./mod/mod_env.html#setenv">SetEnv</a></code> directive. Variables may also be passed from
           the environment of the shell which started the server using the
           <code class="directive"><a href="./mod/mod_env.html#passenv">PassEnv</a></code> directive.</p>
  -    
  +
       
       <h3><a name="conditional" id="conditional">Conditional Per-Request Settings</a></h3>
           
  -    
  +
           <p>For additional flexibility, the directives provided by
           mod_setenvif allow environment variables to be set on a
           per-request basis, conditional on characteristics of particular
  @@ -74,41 +74,41 @@
           a specific Referer [sic] header is found. Even more flexibility
           is available through the mod_rewrite's <code class="directive"><a href="./mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> which uses the 
           <code>[E=...]</code> option to set environment variables.</p>
  -    
  +
       
       <h3><a name="unique-identifiers" id="unique-identifiers">Unique Identifiers</a></h3>
           
  -    
  +
           <p>Finally, mod_unique_id sets the environment variable
           <code>UNIQUE_ID</code> for each request to a value which is
           guaranteed to be unique across "all" requests under very
           specific conditions.</p>
  -    
  +
       
       <h3><a name="standard-cgi" id="standard-cgi">Standard CGI Variables</a></h3>
           
  -    
  +
           <p>In addition to all environment variables set within the
           Apache configuration and passed from the shell, CGI scripts and
           SSI pages are provided with a set of environment variables
           containing meta-information about the request as required by
           the <a href="http://cgi-spec.golux.com/">CGI
           specification</a>.</p>
  -    
  +
       
       <h3><a name="caveats" id="caveats">Some Caveats</a></h3>
           
  -    
  +
           <ul>
             <li>It is not possible to override or change the standard CGI
             variables using the environment manipulation directives.</li>
  -    
  +
             <li>When <a href="suexec.html">suexec</a> is used to launch
             CGI scripts, the environment will be cleaned down to a set of
             <em>safe</em> variables before CGI scripts are launched. The
             list of <em>safe</em> variables is defined at compile-time in
             <code>suexec.c</code>.</li>
  -    
  +
             <li>For portability reasons, the names of environment
             variables may contain only letters, numbers, and the
             underscore character. In addition, the first character may
  @@ -121,23 +121,23 @@
   <div class="section">
   <h2><a name="using" id="using">Using Environment Variables</a></h2>
       
  -    
  +
       <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="./mod/mod_access.html">mod_access</a></code></li><li><code class="module"><a href="./mod/mod_cgi.html">mod_cgi</a></code></li><li><code class="module"><a href="./mod/mod_ext_filter.html">mod_ext_filter</a></code></li><li><code class="module"><a href="./mod/mod_headers.html">mod_headers</a></code></li><li><code class="module"><a href="./mod/mod_include.html">mod_include</a></code></li><li><code class="module"><a href="./mod/mod_log_config.html">mod_log_config</a></code></li><li><code class="module"><a href="./mod/mod_rewrite.html">mod_rewrite</a></code></li></ul></td><td><ul><li><code class="directive"><a href="./mod/mod_access.html#allow">Allow</a></code></li><li><code class="directive"><a href="./mod/mod_log_config.html#customlog">CustomLog</a></code></li><li><code class="directive"><a href="./mod/mod_access.html#deny">Deny</a></code></li><li><code class="directive"><a href="./mod/mod_ext_filter.html#extfilterdefine">ExtFilterDefine</a></code></li><li><code class="directive"><a href="./mod/mod_headers.html#header">Header</a></code></li><li><code class="directive"><a href="./mod/mod_log_config.html#logformat">LogFormat</a></code></li><li><code class="directive"><a href="./mod/mod_rewrite.html#rewritecond">RewriteCond</a></code></li><li><code class="directive"><a href="./mod/mod_rewrite.html#rewriterule">RewriteRule</a></code></li></ul></td></tr></table>
   
       <h3><a name="cgi-scripts" id="cgi-scripts">CGI Scripts</a></h3>
           
  -    
  +
           <p>One of the primary uses of environment variables is to
           communicate information to CGI scripts. As discussed above, the
           environment passed to CGI scripts includes standard
           meta-information about the request in addition to any variables
           set within the Apache configuration. For more details, see the
           <a href="howto/cgi.html">CGI tutorial</a>.</p>
  -    
  +
       
       <h3><a name="ssi-pages" id="ssi-pages">SSI Pages</a></h3>
           
  -    
  +
           <p>Server-parsed (SSI) documents processed by mod_include's
           <code>INCLUDES</code> filter can print environment variables
           using the <code>echo</code> element, and can use environment
  @@ -145,11 +145,11 @@
           conditional on characteristics of a request. Apache also
           provides SSI pages with the standard CGI environment variables
           as discussed above. For more details, see the <a href="howto/ssi.html">SSI tutorial</a>.</p>
  -    
  +
       
       <h3><a name="access-control" id="access-control">Access Control</a></h3>
           
  -    
  +
           <p>Access to the server can be controlled based on the value of
           environment variables using the <code>allow from env=</code>
           and <code>deny from env=</code> directives. In combination with
  @@ -158,11 +158,11 @@
           characteristics of the client. For example, you can use these 
           directives to deny access to a particular browser (User-Agent).
           </p>
  -    
  +
       
       <h3><a name="logging" id="logging">Conditional Logging</a></h3>
           
  -    
  +
           <p>Environment variables can be logged in the access log using
           the <code class="directive"><a href="./mod/mod_log_config.html#logformat">LogFormat</a></code>
           option <code>%e</code>. In addition, the decision on whether
  @@ -174,11 +174,11 @@
           requests for filenames ending in <code>gif</code>, or you can
           choose to only log requests from clients which are outside your
           subnet.</p>
  -    
  +
       
       <h3><a name="response-headers" id="response-headers">Conditional Response Headers</a></h3>
           
  -    
  +
           <p>The <code class="directive"><a href="./mod/mod_headers.html#header">Header</a></code>
           directive can use the presence or
           absence of an environment variable to determine whether or not
  @@ -186,7 +186,7 @@
           client. This allows, for example, a certain response header to
           be sent only if a corresponding header is received in the
           request from the client.</p>
  -    
  +
       
   
       <h3><a name="external-filter" id="external-filter">External Filter Activation</a></h3>
  @@ -200,7 +200,7 @@
   
       <h3><a name="url-rewriting" id="url-rewriting">URL Rewriting</a></h3>
           
  -    
  +
           <p>The <code>%{ENV:...}</code> form of <em>TestString</em> in
           the <code class="directive"><a href="./mod/mod_rewrite.html#rewritecond">RewriteCond</a></code>
           allows mod_rewrite's rewrite
  @@ -214,7 +214,7 @@
   <div class="section">
   <h2><a name="special" id="special">Special Purpose Environment Variables</a></h2>
       
  -    
  +
           <p>Interoperability problems have led to the introduction of
           mechanisms to modify the way Apache behaves when talking to
           particular clients. To make these mechanisms as flexible as
  @@ -223,28 +223,28 @@
           though <code class="directive"><a href="./mod/mod_env.html#setenv">SetEnv</a></code> and 
           <code class="directive"><a href="./mod/mod_env.html#passenv">PassEnv</a></code> could also be used,
           for example.</p>
  -    
  +
       <h3><a name="downgrade" id="downgrade">downgrade-1.0</a></h3>
           
  -    
  +
           <p>This forces the request to be treated as a HTTP/1.0 request
           even if it was in a later dialect.</p>
  -    
  +
       
       <h3><a name="force-no-vary" id="force-no-vary">force-no-vary</a></h3>
           
  -    
  +
           <p>This causes any <code>Vary</code> fields to be removed from
           the response header before it is sent back to the client. Some
           clients don't interpret this field correctly (see the <a href="misc/known_client_problems.html">known client
           problems</a> page); setting this variable can work around this
           problem. Setting this variable also implies
           <strong>force-response-1.0</strong>.</p>
  -    
  +
       
       <h3><a name="force-response" id="force-response">force-response-1.0</a></h3>
           
  -    
  +
         <p>This forces an HTTP/1.0 response to clients making an HTTP/1.0
         request. It was originally
         implemented as a result of a problem with AOL's proxies. Some
  @@ -270,32 +270,32 @@
   
       <h3><a name="nokeepalive" id="nokeepalive">nokeepalive</a></h3>
           
  -    
  +
           <p>This disables <code class="directive"><a href="./mod/core.html#keepalive">KeepAlive</a></code> when set.</p>
  -    
  +
       
   
       <h3><a name="prefer-language" id="prefer-language">prefer-language</a></h3>
  -    
  +
           <p>This influences <code class="module"><a href="./mod/mod_negotiation.html">mod_negotiation</a></code>'s behaviour. If
           it contains a language tag (such as <code>en</code>, <code>ja</code>
           or <code>x-klingon</code>), <code class="module"><a href="./mod/mod_negotiation.html">mod_negotiation</a></code> tries
           to deliver a variant with that language. If there's no such variant,
           the normal <a href="content-negotiation.html">negotiation</a> process
           applies.</p>
  +
       
  -    
  -    
  +
       <h3><a name="redirect-carefully" id="redirect-carefully">redirect-carefully</a></h3>
           
  -    
  +
           <p>This forces the server to be more careful when sending a redirect
           to the client.  This is typically used when a client has a known
           problem handling redirects.  This was originally implemented as a
           result of a problem with Microsoft's WebFolders software which has
           a problem handling redirects on directory resources via DAV 
           methods.</p>
  -    
  +
       
   
      <h3><a name="suppress-error-charset" id="suppress-error-charset">suppress-error-charset</a></h3>
  @@ -322,10 +322,10 @@
   <div class="section">
   <h2><a name="examples" id="examples">Examples</a></h2>
       
  -    
  +
       <h3><a name="misbehaving" id="misbehaving">Changing protocol behavior with misbehaving clients</a></h3>
           
  -    
  +
           <p>We recommend that the following lines be included in
           httpd.conf to deal with known client problems.</p>
   <div class="example"><pre>
  @@ -352,7 +352,7 @@
       
       <h3><a name="no-img-log" id="no-img-log">Do not log requests for images in the access log</a></h3>
           
  -    
  +
           <p>This example keeps requests for images from appearing in the
           access log. It can be easily modified to prevent logging of
           particular directories, or to prevent logging of requests
  @@ -362,11 +362,11 @@
   SetEnvIf Request_URI \.jpg image-request
   SetEnvIf Request_URI \.png image-request
   CustomLog logs/access_log common env=!image-request</pre></div>
  -    
  +
       
       <h3><a name="image-theft" id="image-theft">Prevent "Image Theft"</a></h3>
           
  -    
  +
           <p>This example shows how to keep people not on your server
           from using images on your server as inline-images on their
           pages. This is not a recommended configuration, but it can work
  @@ -381,7 +381,7 @@
      Deny from all
      Allow from env=local_referal
   &lt;/Directory&gt;</pre></div>
  -    
  +
           <p>For more information about this technique, see the
           ApacheToday tutorial " <a href="http://apachetoday.com/news_story.php3?ltsn=2000-06-14-002-01-PS">
       Keeping Your Images from Adorning Other Sites</a>".</p>
  
  
  
  1.17.2.4  +1 -1      httpd-2.0/docs/manual/filter.html.en
  
  Index: filter.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/filter.html.en,v
  retrieving revision 1.17.2.3
  retrieving revision 1.17.2.4
  diff -u -r1.17.2.3 -r1.17.2.4
  --- filter.html.en	29 May 2003 19:29:35 -0000	1.17.2.3
  +++ filter.html.en	30 Jun 2003 01:23:59 -0000	1.17.2.4
  @@ -30,7 +30,7 @@
   <h2><a name="filters" id="filters">Filters</a></h2>
       
       <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="./mod/mod_deflate.html">mod_deflate</a></code></li><li><code class="module"><a href="./mod/mod_ext_filter.html">mod_ext_filter</a></code></li><li><code class="module"><a href="./mod/mod_include.html">mod_include</a></code></li></ul></td><td><ul><li><code class="directive"><a href="./mod/mod_mime.html#addinputfilter">AddInputFilter</a></code></li><li><code class="directive"><a href="./mod/mod_mime.html#addoutputfilter">AddOutputFilter</a></code></li><li><code class="directive"><a href="./mod/mod_mime.html#removeinputfilter">RemoveInputFilter</a></code></li><li><code class="directive"><a href="./mod/mod_mime.html#removeoutputfilter">RemoveOutputFilter</a></code></li><li><code class="directive"><a href="./mod/mod_ext_filter.html#extfilterdefine">ExtFilterDefine</a></code></li><li><code class="directive"><a href="./mod/mod_ext_filter.html#extfilteroptions">ExtFilterOptions</a></code></li><li><code class="directive"><a href="./mod/core.html#setinputfilter">SetInputFilter</a></code></li><li><code class="directive"><a href="./mod/core.html#setoutputfilter">SetOutputFilter</a></code></li></ul></td></tr></table>
  -    
  +
       <p>A <em>filter</em> is a process that is applied to data that
       is sent or received by the server. Data sent by clients to the
       server is processed by <em>input filters</em> while data sent
  
  
  
  1.33.2.3  +4 -4      httpd-2.0/docs/manual/handler.html.en
  
  Index: handler.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/handler.html.en,v
  retrieving revision 1.33.2.2
  retrieving revision 1.33.2.3
  diff -u -r1.33.2.2 -r1.33.2.3
  --- handler.html.en	29 May 2003 19:29:35 -0000	1.33.2.2
  +++ handler.html.en	30 Jun 2003 01:23:59 -0000	1.33.2.3
  @@ -34,7 +34,7 @@
   <h2><a name="definition" id="definition">What is a Handler</a></h2>
       
       <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="./mod/mod_actions.html">mod_actions</a></code></li><li><code class="module"><a href="./mod/mod_asis.html">mod_asis</a></code></li><li><code class="module"><a href="./mod/mod_cgi.html">mod_cgi</a></code></li><li><code class="module"><a href="./mod/mod_imap.html">mod_imap</a></code></li><li><code class="module"><a href="./mod/mod_info.html">mod_info</a></code></li><li><code class="module"><a href="./mod/mod_mime.html">mod_mime</a></code></li><li><code class="module"><a href="./mod/mod_negotiation.html">mod_negotiation</a></code></li><li><code class="module"><a href="./mod/mod_status.html">mod_status</a></code></li></ul></td><td><ul><li><code class="directive"><a href="./mod/mod_actions.html#action">Action</a></code></li><li><code class="directive"><a href="./mod/mod_mime.html#addhandler">AddHandler</a></code></li><li><code class="directive"><a href="./mod/mod_mime.html#removehandler">RemoveHandler</a></code></li><li><code class="directive"><a href="./mod/core.html#sethandler">SetHandler</a></code></li></ul></td></tr></table>
  -    
  +
   
       <p>A "handler" is an internal Apache representation of the
       action to be performed when a file is called. Generally, files
  @@ -89,7 +89,7 @@
         <p>The following directives will cause requests for files with
         the <code>html</code> extension to trigger the launch of the
         <code>footer.pl</code> CGI script.</p>
  -      
  +
         <div class="example"><p><code>
           Action add-footer /cgi-bin/footer.pl<br />
           AddHandler add-footer .html
  @@ -99,7 +99,7 @@
         originally requested document (pointed to by the
         <code>PATH_TRANSLATED</code> environment variable) and making
         whatever modifications or additions are desired.</p>
  - 
  +
       
       <h3><a name="example2" id="example2">Files with HTTP headers</a></h3>
         
  @@ -116,7 +116,7 @@
           SetHandler send-as-is<br />
           &lt;/Directory&gt;
         </code></p></div>
  -      
  +
       
     </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
   <div class="section">
  
  
  
  1.18.2.6  +36 -36    httpd-2.0/docs/manual/logs.html.en
  
  Index: logs.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/logs.html.en,v
  retrieving revision 1.18.2.5
  retrieving revision 1.18.2.6
  diff -u -r1.18.2.5 -r1.18.2.6
  --- logs.html.en	29 May 2003 19:29:36 -0000	1.18.2.5
  +++ logs.html.en	30 Jun 2003 01:23:59 -0000	1.18.2.6
  @@ -43,7 +43,7 @@
   <div class="section">
   <h2><a name="security" id="security">Security Warning</a></h2>
       
  -    
  +
       <p>Anyone who can write to the directory where Apache is
       writing a log file can almost certainly gain access to the uid
       that the server is started as, which is normally root. Do
  @@ -61,9 +61,9 @@
   <div class="section">
   <h2><a name="errorlog" id="errorlog">Error Log</a></h2>
       
  -    
  +
       <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td /><td><ul><li><code class="directive"><a href="./mod/core.html#errorlog">ErrorLog</a></code></li><li><code class="directive"><a href="./mod/core.html#loglevel">LogLevel</a></code></li></ul></td></tr></table>
  -    
  +
       <p>The server error log, whose name and location is set by the
       <code class="directive"><a href="./mod/core.html#errorlog">ErrorLog</a></code> directive, is the
       most important log file. This is the place where Apache httpd
  @@ -79,18 +79,18 @@
       is also possible to have the server send errors to
       <code>syslog</code> or <a href="#piped">pipe them to a
       program</a>.</p>
  -    
  +
       <p>The format of the error log is relatively free-form and
       descriptive. But there is certain information that is contained
       in most error log entries. For example, here is a typical
       message.</p>
  -    
  +
       <div class="example"><p><code>
         [Wed Oct 11 14:32:52 2000] [error] [client 127.0.0.1]
         client denied by server configuration:
         /export/home/live/ap/htdocs/test
       </code></p></div>
  -    
  +
       <p>The first item in the log entry is the date and time of the
       message. The second entry lists the severity of the error being
       reported. The <code class="directive"><a href="./mod/core.html#loglevel">LogLevel</a></code>
  @@ -115,11 +115,11 @@
       Since it is possible to customize the access log, you can
       obtain more information about error conditions using that log
       file.</p>
  -    
  +
       <p>During testing, it is often useful to continuously monitor
       the error log for any problems. On unix systems, you can
       accomplish this using:</p>
  -    
  +
       <div class="example"><p><code>
         tail -f error_log
       </code></p></div>
  @@ -127,9 +127,9 @@
   <div class="section">
   <h2><a name="accesslog" id="accesslog">Access Log</a></h2>
       
  -    
  +
       <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="./mod/mod_log_config.html">mod_log_config</a></code></li><li><code class="module"><a href="./mod/mod_setenvif.html">mod_setenvif</a></code></li></ul></td><td><ul><li><code class="directive"><a href="./mod/mod_log_config.html#customlog">CustomLog</a></code></li><li><code class="directive"><a href="./mod/mod_log_config.html#logformat">LogFormat</a></code></li><li><code class="directive"><a href="./mod/mod_setenvif.html#setenvif">SetEnvIf</a></code></li></ul></td></tr></table>
  -    
  +
       <p>The server access log records all requests processed by the
       server. The location and content of the access log are
       controlled by the <code class="directive"><a href="./mod/mod_log_config.html#customlog">CustomLog</a></code>
  @@ -147,7 +147,7 @@
       analysis, check the <a href="http://dmoz.org/Computers/Software/Internet/Site_Management/Log_analysis/">
       Open Directory</a> or <a href="http://dir.yahoo.com/Computers_and_Internet/Software/Internet/World_Wide_Web/Servers/Log_Analysis_Tools/">
       Yahoo</a>.</p>
  -    
  +
       <p>Various versions of Apache httpd have used other modules and
       directives to control access logging, including
       mod_log_referer, mod_log_agent, and the
  @@ -159,10 +159,10 @@
       printf(1) format string. Some examples are presented in the next
       sections. For a complete list of the possible contents of the
       format string, see the <code class="module"><a href="./mod/mod_log_config.html">mod_log_config</a></code> <a href="mod/mod_log_config.html#formats">format strings</a>.</p>
  -    
  +
       <h3><a name="common" id="common">Common Log Format</a></h3>
         
  -    
  +
         <p>A typical configuration for the access log might look as
         follows.</p>
   
  @@ -170,7 +170,7 @@
           LogFormat "%h %l %u %t \"%r\" %&gt;s %b" common<br />
            CustomLog logs/access_log common
         </code></p></div>
  -    
  +
         <p>This defines the <em>nickname</em> <code>common</code> and
         associates it with a particular log format string. The format
         string consists of percent directives, each of which tell the
  @@ -188,7 +188,7 @@
   	  <em>nickname</em>. The filename for the access log is relative to
   	  the <code class="directive"><a href="./mod/core.html#serverroot">ServerRoot</a></code> unless it
   	  begins with a slash.</p>
  -    
  +
         <p>The above configuration will write log entries in a format
         known as the Common Log Format (CLF). This standard format can
         be produced by many different web servers and read by many log
  @@ -199,9 +199,9 @@
           127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET
           /apache_pb.gif HTTP/1.0" 200 2326
         </code></p></div>
  -    
  +
         <p>Each part of this log entry is described below.</p>
  -    
  +
         <dl>
           <dt><code>127.0.0.1</code> (<code>%h</code>)</dt>
   
  @@ -299,10 +299,10 @@
           <code>%B</code> instead.</dd>
         </dl>
       
  -    
  +
       <h3><a name="combined" id="combined">Combined Log Format</a></h3>
         
  -      
  +
         <p>Another commonly used format string is called the Combined
         Log Format. It can be used as follows.</p>
   
  @@ -318,7 +318,7 @@
         <code>%{<em>header</em>}i</code>, where <em>header</em> can be
         any HTTP request header. The access log under this format will
         look like:</p>
  -      
  +
         <div class="example"><p><code>
           127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET
           /apache_pb.gif HTTP/1.0" 200 2326
  @@ -327,7 +327,7 @@
         </code></p></div>
   
         <p>The additional fields are:</p>
  -      
  +
         <dl>
           <dt><code>"http://www.example.com/start.html"</code>
           (<code>\"%{Referer}i\"</code>)</dt>
  @@ -345,10 +345,10 @@
           itself.</dd>
         </dl>
       
  -    
  +
       <h3><a name="multiple" id="multiple">Multiple Access Logs</a></h3>
         
  -      
  +
         <p>Multiple access logs can be created simply by specifying
         multiple <code class="directive"><a href="./mod/mod_log_config.html#customlog">CustomLog</a></code> 
         directives in the configuration
  @@ -369,10 +369,10 @@
         nickname with the <code class="directive"><a href="./mod/mod_log_config.html#logformat">LogFormat</a></code> directive. Instead,
         the log format can be specified directly in the <code class="directive"><a href="./mod/mod_log_config.html#customlog">CustomLog</a></code> directive.</p>
       
  -    
  +
       <h3><a name="conditional" id="conditional">Conditional Logs</a></h3>
         
  -      
  +
         <p>There are times when it is convenient to exclude certain
         entries from the access logs based on characteristics of the
         client request. This is easily accomplished with the help of <a href="env.html">environment variables</a>. First, an
  @@ -413,7 +413,7 @@
   <div class="section">
   <h2><a name="rotation" id="rotation">Log Rotation</a></h2>
       
  -    
  +
       <p>On even a moderately busy server, the quantity of
       information stored in the log files is very large. The access
       log file typically grows 1 MB or more per 10,000 requests. It
  @@ -448,7 +448,7 @@
   <div class="section">
   <h2><a name="piped" id="piped">Piped Logs</a></h2>
       
  -    
  +
       <p>Apache httpd is capable of writing error and access log
       files through a pipe to another process, rather than directly
       to a file. This capability dramatically increases the
  @@ -476,7 +476,7 @@
         CustomLog "|/usr/local/apache/bin/rotatelogs
         /var/log/access_log 86400" common
       </code></p></div>
  -    
  +
       <p>Notice that quotes are used to enclose the entire command
       that will be called for the pipe. Although these examples are
       for the access log, the same technique can be used for the
  @@ -493,7 +493,7 @@
   <div class="section">
   <h2><a name="virtualhost" id="virtualhost">Virtual Hosts</a></h2>
       
  -    
  +
       <p>When running a server with many <a href="vhosts/">virtual
       hosts</a>, there are several options for dealing with log
       files. First, it is possible to use logs exactly as in a
  @@ -537,12 +537,12 @@
   <div class="section">
   <h2><a name="other" id="other">Other Log Files</a></h2>
       
  -    
  +
       <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="./mod/mod_cgi.html">mod_cgi</a></code></li><li><code class="module"><a href="./mod/mod_rewrite.html">mod_rewrite</a></code></li></ul></td><td><ul><li><code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code></li><li><code class="directive"><a href="./mod/mod_rewrite.html#rewritelog">RewriteLog</a></code></li><li><code class="directive"><a href="./mod/mod_rewrite.html#rewriteloglevel">RewriteLogLevel</a></code></li><li><code class="directive"><a href="./mod/mod_cgi.html#scriptlog">ScriptLog</a></code></li><li><code class="directive"><a href="./mod/mod_cgi.html#scriptlogbuffer">ScriptLogBuffer</a></code></li><li><code class="directive"><a href="./mod/mod_cgi.html#scriptloglength">ScriptLogLength</a></code></li></ul></td></tr></table>
  -    
  +
       <h3><a name="pidfile" id="pidfile">PID File</a></h3>
         
  -    
  +
         <p>On startup, Apache httpd saves the process id of the parent
         httpd process to the file <code>logs/httpd.pid</code>. This
         filename can be changed with the <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> directive. The
  @@ -552,20 +552,20 @@
         For more information see the <a href="stopping.html">Stopping
         and Restarting</a> page.</p>    
       
  -    
  +
       <h3><a name="scriptlog" id="scriptlog">Script Log</a></h3>
         
  -      
  +
         <p>In order to aid in debugging, the
         <code class="directive"><a href="./mod/mod_cgi.html#scriptlog">ScriptLog</a></code> directive
         allows you to record the input to and output from CGI scripts.
         This should only be used in testing - not for live servers.
         More information is available in the <a href="mod/mod_cgi.html">mod_cgi</a> documentation.</p>
       
  -    
  +
       <h3><a name="rewritelog" id="rewritelog">Rewrite Log</a></h3>
         
  -      
  +
         <p>When using the powerful and complex features of <a href="mod/mod_rewrite.html">mod_rewrite</a>, it is almost
         always necessary to use the <code class="directive"><a href="./mod/mod_rewrite.html#rewritelog">RewriteLog</a></code> to help
         in debugging. This log file produces a detailed analysis of how
  
  
  
  1.37.2.4  +1 -1      httpd-2.0/docs/manual/suexec.html.en
  
  Index: suexec.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/suexec.html.en,v
  retrieving revision 1.37.2.3
  retrieving revision 1.37.2.4
  diff -u -r1.37.2.3 -r1.37.2.4
  --- suexec.html.en	29 May 2003 19:29:36 -0000	1.37.2.3
  +++ suexec.html.en	30 Jun 2003 01:23:59 -0000	1.37.2.4
  @@ -187,7 +187,7 @@
   
         <li>
           <strong>Is the target user <em>NOT</em> superuser?</strong>
  -        
  +
   
           <p class="indent">
             Presently, suEXEC does not allow 'root' to execute
  
  
  
  No                   revision
  No                   revision
  1.18.2.5  +2 -2      httpd-2.0/docs/manual/mod/mod_include.html.en
  
  Index: mod_include.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_include.html.en,v
  retrieving revision 1.18.2.4
  retrieving revision 1.18.2.5
  diff -u -r1.18.2.4 -r1.18.2.5
  --- mod_include.html.en	29 May 2003 19:29:47 -0000	1.18.2.4
  +++ mod_include.html.en	30 Jun 2003 01:24:00 -0000	1.18.2.5
  @@ -638,7 +638,7 @@
   <table class="directive">
   <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>String that starts an include element</td></tr>
   <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>SSIStartTag <var>tag</var></code></td></tr>
  -<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>SSIStartTag "&lt;!--"</code></td></tr>
  +<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>SSIStartTag "&lt;!--#"</code></td></tr>
   <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host</td></tr>
   <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Base</td></tr>
   <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_include</td></tr>
  @@ -661,7 +661,7 @@
       below:</p>
   
       <div class="example"><h3>SSI directives with alternate start and end tags</h3><p><code>
  -      &lt;%#printenv %&gt;
  +      &lt;%printenv %&gt;
       </code></p></div>
   
   <h3>See also</h3>
  
  
  
  1.1.2.25  +1 -1      httpd-2.0/docs/manual/mod/quickreference.html.de
  
  Index: quickreference.html.de
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/quickreference.html.de,v
  retrieving revision 1.1.2.24
  retrieving revision 1.1.2.25
  diff -u -r1.1.2.24 -r1.1.2.25
  --- quickreference.html.de	29 May 2003 19:29:52 -0000	1.1.2.24
  +++ quickreference.html.de	30 Jun 2003 01:24:00 -0000	1.1.2.25
  @@ -612,7 +612,7 @@
   <tr><td><a href="mod_include.html#ssiendtag">SSIEndTag <var>tag</var></a></td><td> "--&gt;" </td><td>sv</td><td>B</td></tr><tr><td class="descr" colspan="4">String that ends an include element</td></tr>
   <tr class="odd"><td><a href="mod_include.html#ssierrormsg">SSIErrorMsg <var>message</var></a></td><td> "[an error occurred +</td><td>svdh</td><td>B</td></tr><tr class="odd"><td class="descr" colspan="4">Error message displayed when there is an SSI
   error</td></tr>
  -<tr><td><a href="mod_include.html#ssistarttag">SSIStartTag <var>tag</var></a></td><td> "&lt;!--" </td><td>sv</td><td>B</td></tr><tr><td class="descr" colspan="4">String that starts an include element</td></tr>
  +<tr><td><a href="mod_include.html#ssistarttag">SSIStartTag <var>tag</var></a></td><td> "&lt;!--#" </td><td>sv</td><td>B</td></tr><tr><td class="descr" colspan="4">String that starts an include element</td></tr>
   <tr class="odd"><td><a href="mod_include.html#ssitimeformat">SSITimeFormat <var>formatstring</var></a></td><td> "%A, %d-%b-%Y %H:%M +</td><td>svdh</td><td>B</td></tr><tr class="odd"><td class="descr" colspan="4">Configures the format in which date strings are
   displayed</td></tr>
   <tr><td><a href="mod_include.html#ssiundefinedecho">SSIUndefinedEcho <var>string</var></a></td><td> "(none)" </td><td>sv</td><td>B</td></tr><tr><td class="descr" colspan="4">String displayed when an unset variable is echoed</td></tr>
  
  
  
  1.47.2.35 +1 -1      httpd-2.0/docs/manual/mod/quickreference.html.en
  
  Index: quickreference.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/quickreference.html.en,v
  retrieving revision 1.47.2.34
  retrieving revision 1.47.2.35
  diff -u -r1.47.2.34 -r1.47.2.35
  --- quickreference.html.en	29 May 2003 19:29:52 -0000	1.47.2.34
  +++ quickreference.html.en	30 Jun 2003 01:24:01 -0000	1.47.2.35
  @@ -595,7 +595,7 @@
   <tr><td><a href="mod_include.html#ssiendtag">SSIEndTag <var>tag</var></a></td><td> "--&gt;" </td><td>sv</td><td>B</td></tr><tr><td class="descr" colspan="4">String that ends an include element</td></tr>
   <tr class="odd"><td><a href="mod_include.html#ssierrormsg">SSIErrorMsg <var>message</var></a></td><td> "[an error occurred +</td><td>svdh</td><td>B</td></tr><tr class="odd"><td class="descr" colspan="4">Error message displayed when there is an SSI
   error</td></tr>
  -<tr><td><a href="mod_include.html#ssistarttag">SSIStartTag <var>tag</var></a></td><td> "&lt;!--" </td><td>sv</td><td>B</td></tr><tr><td class="descr" colspan="4">String that starts an include element</td></tr>
  +<tr><td><a href="mod_include.html#ssistarttag">SSIStartTag <var>tag</var></a></td><td> "&lt;!--#" </td><td>sv</td><td>B</td></tr><tr><td class="descr" colspan="4">String that starts an include element</td></tr>
   <tr class="odd"><td><a href="mod_include.html#ssitimeformat">SSITimeFormat <var>formatstring</var></a></td><td> "%A, %d-%b-%Y %H:%M +</td><td>svdh</td><td>B</td></tr><tr class="odd"><td class="descr" colspan="4">Configures the format in which date strings are
   displayed</td></tr>
   <tr><td><a href="mod_include.html#ssiundefinedecho">SSIUndefinedEcho <var>string</var></a></td><td> "(none)" </td><td>sv</td><td>B</td></tr><tr><td class="descr" colspan="4">String displayed when an unset variable is echoed</td></tr>
  
  
  
  1.1.2.15  +1 -1      httpd-2.0/docs/manual/mod/Attic/quickreference.html.ru.koi8-r
  
  Index: quickreference.html.ru.koi8-r
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/Attic/quickreference.html.ru.koi8-r,v
  retrieving revision 1.1.2.14
  retrieving revision 1.1.2.15
  diff -u -r1.1.2.14 -r1.1.2.15
  --- quickreference.html.ru.koi8-r	29 May 2003 19:29:53 -0000	1.1.2.14
  +++ quickreference.html.ru.koi8-r	30 Jun 2003 01:24:01 -0000	1.1.2.15
  @@ -597,7 +597,7 @@
   <tr><td><a href="mod_include.html#ssiendtag">SSIEndTag <var>tag</var></a></td><td> "--&gt;" </td><td>sv</td><td>B</td></tr><tr><td class="descr" colspan="4">String that ends an include element</td></tr>
   <tr class="odd"><td><a href="mod_include.html#ssierrormsg">SSIErrorMsg <var>message</var></a></td><td> "[an error occurred +</td><td>svdh</td><td>B</td></tr><tr class="odd"><td class="descr" colspan="4">Error message displayed when there is an SSI
   error</td></tr>
  -<tr><td><a href="mod_include.html#ssistarttag">SSIStartTag <var>tag</var></a></td><td> "&lt;!--" </td><td>sv</td><td>B</td></tr><tr><td class="descr" colspan="4">String that starts an include element</td></tr>
  +<tr><td><a href="mod_include.html#ssistarttag">SSIStartTag <var>tag</var></a></td><td> "&lt;!--#" </td><td>sv</td><td>B</td></tr><tr><td class="descr" colspan="4">String that starts an include element</td></tr>
   <tr class="odd"><td><a href="mod_include.html#ssitimeformat">SSITimeFormat <var>formatstring</var></a></td><td> "%A, %d-%b-%Y %H:%M +</td><td>svdh</td><td>B</td></tr><tr class="odd"><td class="descr" colspan="4">Configures the format in which date strings are
   displayed</td></tr>
   <tr><td><a href="mod_include.html#ssiundefinedecho">SSIUndefinedEcho <var>string</var></a></td><td> "(none)" </td><td>sv</td><td>B</td></tr><tr><td class="descr" colspan="4">String displayed when an unset variable is echoed</td></tr>
  
  
  

Mime
View raw message