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