diff options
| -rw-r--r-- | docs/manual/mod/core.html | 50 | ||||
| -rw-r--r-- | docs/manual/mod/mod_cgi.html | 13 | ||||
| -rw-r--r-- | docs/manual/mod/mod_cgid.html | 5 |
3 files changed, 68 insertions, 0 deletions
diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html index a40ca645ea..ec332498be 100644 --- a/docs/manual/mod/core.html +++ b/docs/manual/mod/core.html @@ -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> @@ -141,6 +143,54 @@ </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> +<Files "mypaths.shtml"> + Options +Includes + SetOutputFilter INCLUDES + AcceptPathInfo on +</Files> +</pre> + <hr /> + <h2><a id="accessfilename" name="accessfilename">AccessFileName directive</a></h2> diff --git a/docs/manual/mod/mod_cgi.html b/docs/manual/mod/mod_cgi.html index e478a22681..1a355eee58 100644 --- a/docs/manual/mod/mod_cgi.html +++ b/docs/manual/mod/mod_cgi.html @@ -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 diff --git a/docs/manual/mod/mod_cgid.html b/docs/manual/mod/mod_cgid.html index be5337f31b..ac3c8e4f8f 100644 --- a/docs/manual/mod/mod_cgid.html +++ b/docs/manual/mod/mod_cgid.html @@ -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 |