From a33f617e1a272f095de8f1f591a0487b3b0a368e Mon Sep 17 00:00:00 2001 From: "William A. Rowe Jr" Date: Thu, 13 Dec 2001 18:19:21 +0000 Subject: [PATCH] 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. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@92455 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/core.html | 50 +++++++++++++++++++++++++++++++++++ docs/manual/mod/mod_cgi.html | 13 +++++++++ docs/manual/mod/mod_cgid.html | 5 ++++ 3 files changed, 68 insertions(+) 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 @@

Directives

+

AcceptPathInfo directive

+ Syntax: AcceptPathInfo On|Off
+ Context: all
+ Status: core
+ Default: + Varies by handler, see below
+ Compatibility: + AcceptPathInfo is only available in Apache 2.0.30 and later + +

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 /test/here.html/more and + /test/nothere.html/more both collect /more + as PATH_INFO.

+ +

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, /test/here.html/more + 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.

+ +

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.

+ +

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:

+
+<Files "mypaths.shtml">
+    Options +Includes
+    SetOutputFilter INCLUDES
+    AcceptPathInfo on
+</Files>
+
+
+

AccessFileName directive

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 @@

Summary

+

Any file that has the mime type application/x-httpd-cgi or handler @@ -75,6 +76,18 @@ specification, with the following provisions:

+
PATH_INFO
+ +
This will not be available if the AcceptPathInfo + directive is explicitly set to off. 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 on for mod_cgi requests.
+
REMOTE_HOST
This will only be set if Summary +

Except for the optimizations and the additional ScriptSock + directive noted below, mod_cgid behaves similarly to mod_cgi. + See the mod_cgi Summary + for additional details about Apache and CGI.

+

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 -- 2.40.0