httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wr...@apache.org
Subject cvs commit: httpd-2.0/docs/manual/mod mod_cgi.html mod_cgid.html core.html
Date Thu, 13 Dec 2001 18:19:22 GMT
wrowe       01/12/13 10:19:22

  Modified:    docs/manual/mod mod_cgi.html mod_cgid.html core.html
  Log:
    A little loopy commit.  Refer mod_cgid users to the mod_cgi docs for
    extra info, document the AcceptPathInfo impact in the PATH_INFO comments
    of mod_cgi, and document it's configuration in core.
  
  Revision  Changes    Path
  1.25      +13 -0     httpd-2.0/docs/manual/mod/mod_cgi.html
  
  Index: mod_cgi.html
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_cgi.html,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- mod_cgi.html	2001/09/22 19:36:01	1.24
  +++ mod_cgi.html	2001/12/13 18:19:21	1.25
  @@ -28,6 +28,7 @@
       <h2>Summary</h2>
       <!-- XXX: Should have references to CGI definition/RFC -->
       <!-- XXX: Should mention Options ExecCGI  -->
  +    <!-- XXX: Should mention AcceptPathInfo   -->
   
       <p>Any file that has the mime type
       <code>application/x-httpd-cgi</code> or handler
  @@ -75,6 +76,18 @@
       specification</a>, with the following provisions: 
   
       <dl>
  +      <dt>PATH_INFO</dt>
  +
  +      <dd>This will not be available if the <a
  +      href="core.html#acceptpathinfo"><code>AcceptPathInfo</code></a>
  +      directive is explicitly set to <code>off</code>.  The default
  +      behavior, if AcceptPathInfo is not given, is that mod_cgi will
  +      accept path info (trailing /more/path/info following the script
  +      filename in the URI), while the core server will return a 404
  +      NOT FOUND error for requests with additional path info.  
  +      Omitting the AcceptPathInfo directive has the same effect as 
  +      setting it <code>on</code> for mod_cgi requests.</dd>
  +
         <dt>REMOTE_HOST</dt>
   
         <dd>This will only be set if <a
  
  
  
  1.3       +5 -0      httpd-2.0/docs/manual/mod/mod_cgid.html
  
  Index: mod_cgid.html
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_cgid.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- mod_cgid.html	2001/09/22 19:36:01	1.2
  +++ mod_cgid.html	2001/12/13 18:19:21	1.3
  @@ -29,6 +29,11 @@
   
       <h2>Summary</h2>
   
  +    <p>Except for the optimizations and the additional ScriptSock
  +    directive noted below, mod_cgid behaves similarly to mod_cgi.  
  +    <strong>See the <a href="mod_cgi.html">mod_cgi</a> Summary 
  +    for additional details about Apache and CGI.</strong></p>
  +
       <p>On certain unix operating systems, forking a process from a
       multi-threaded server is a very expensive operation because the
       new process will replicate all the threads of the parent
  
  
  
  1.204     +50 -0     httpd-2.0/docs/manual/mod/core.html
  
  Index: core.html
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/core.html,v
  retrieving revision 1.203
  retrieving revision 1.204
  diff -u -r1.203 -r1.204
  --- core.html	2001/11/10 03:37:15	1.203
  +++ core.html	2001/12/13 18:19:21	1.204
  @@ -21,6 +21,8 @@
       <h2>Directives</h2>
   
       <ul>
  +      <li><a href="#acceptpathinfo">AcceptPathInfo</a></li>
  +
         <li><a href="#accessfilename">AccessFileName</a></li>
   
         <li><a href="#adddefaultcharset">AddDefaultCharset</a></li>
  @@ -139,6 +141,54 @@
   
         <li><a href="#virtualhost">&lt;VirtualHost&gt;</a></li>
       </ul>
  +    <hr />
  +
  +    <h2><a id="acceptpathinfo"
  +    name="adddefaultcharset">AcceptPathInfo directive</a></h2>
  +    <a href="directive-dict.html#Syntax"
  +    rel="Help"><strong>Syntax:</strong></a> AcceptPathInfo On|Off<br
/>
  +     <a href="directive-dict.html#Context"
  +    rel="Help"><strong>Context:</strong></a> all<br />
  +     <a href="directive-dict.html#Status"
  +    rel="Help"><strong>Status:</strong></a> core<br />
  +     <a href="directive-dict.html#Default"
  +    rel="Help"><strong>Default:</strong></a>
  +    <code>Varies by handler, see below</code><br />
  +     <a href="directive-dict.html#Compatibility"
  +    rel="Help"><strong>Compatibility:</strong></a>
  +    AcceptPathInfo is only available in Apache 2.0.30 and later 
  +
  +    <p>This directive provides the ability to accept or reject requests
  +    that contain PATH_INFO, or trailing pathname information that follows
  +    an actual filename (or non-existant file in an existing directory).
  +    For example, if the location /test/ points to a directory, and the
  +    file here.html exists, while the file nothere.html does not exist,
  +    the requests for <code>/test/here.html/more</code> and 
  +    <code>/test/nothere.html/more</code> both collect <code>/more</code>

  +    as PATH_INFO.</p>
  +
  +    <p>By default, the core handler for normal files rejects any
  +    PATH_INFO with an error 404 NOT FOUND, since the file does not
  +    exist (in our example above, <code>/test/here.html/more</code>
  +    is not a file name.)  Other handlers that serve scripts, such as 
  +    mod_cgi, mod_cgid and mod_isapi, generally accept PATH_INFO by 
  +    default.</p>
  +
  +    <p>You may override the default behavior of any Apache module, and 
  +    possibly third party modules, with the AcceptPathInfo directive.
  +    It is up to the individual module to respect your override.</p>
  +
  +    <p>This override is required, for example, when you use a filter,
  +    such as mod_includes, to generate content based on PATH_INFO.  The
  +    core module would usually reject the request, so you could use the
  +    following configuration to enable such a script:</p>
  +<pre>
  +&lt;Files "mypaths.shtml"&gt;
  +    Options +Includes
  +    SetOutputFilter INCLUDES
  +    AcceptPathInfo on
  +&lt;/Files&gt;
  +</pre>
       <hr />
   
       <h2><a id="accessfilename" name="accessfilename">AccessFileName
  
  
  

Mime
View raw message