From: Ken Coar Date: Thu, 13 May 1999 18:25:45 +0000 (+0000) Subject: Someone finally stood up and made the ReadmeName and HeaderName X-Git-Tag: apache-apr-merge-3~8 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=7af4a107fc02315a6f9a085772f4a9753767efb3;p=thirdparty%2Fapache%2Fhttpd.git Someone finally stood up and made the ReadmeName and HeaderName features use subrequests. Not only that, but they can be parsed for SSIs too! PR: 1574, 3026, 3529, 3569, 4256 Submitted by: Raymond S Brand Reviewed by: Ken Coar git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@83202 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_autoindex.html b/docs/manual/mod/mod_autoindex.html index 5755a94e3fa..7fedd69c48a 100644 --- a/docs/manual/mod/mod_autoindex.html +++ b/docs/manual/mod/mod_autoindex.html @@ -426,20 +426,53 @@ preference. Module: mod_autoindex

+>Module: mod_autoindex +
+ Compatibility: some features only available after + 1.3.6; see text +

The HeaderName directive sets the name of the file that will be inserted at the top of the index listing. Filename is the name of the file -to include, and is taken to be relative to the directory being indexed. -The server first attempts to include filename.html -as an HTML document, otherwise it will include filename as plain -text. Example: +to include. +

+
Apache 1.3.6 and earlier: +The module first attempts to include filename.html +as an HTML document, otherwise it will try to include filename as +plain text. Filename is treated as a filesystem path relative +to the directory being indexed. In no case is SSI processing done. +Example:
HeaderName HEADER
when indexing the directory /web, the server will first look for the HTML file /web/HEADER.html and include it if found, otherwise it will include the plain text file /web/HEADER, if it exists. - -

See also ReadmeName.

+
+
Apache versions after 1.3.6: +Filename is treated as a URI path relative to the one used +to access the directory being indexed, and must resolve to a document +with a major content type of "text" (e.g., +text/html, text/plain, etc.). +This means that filename may refer to a CGI script if the +script's actual file type (as opposed to its output) is marked as +text/html such as with a directive like: +
+    AddType text/html .cgi
+
+Content negotiation +will be performed if the MultiViews +option is enabled. +If filename resolves to a static text/html document +(not a CGI script) and the +Includes option is enabled, +the file will be processed for server-side includes (see the +mod_include documentation). +
+

+See also ReadmeName. +

IndexIgnore

@@ -753,19 +786,26 @@ the client from requesting the directory listing in a different order. Module: mod_autoindex

+>Module: mod_autoindex +
+ Compatibility: some features only available after + 1.3.6; see text +

The ReadmeName directive sets the name of the file that will be appended to the end of the index listing. Filename is the name of the file -to include, and is taken to be relative to the directory being indexed. -The server first attempts to include filename.html -as an HTML document, otherwise it will include filename as plain -text. Example: -

ReadmeName README
-when indexing the directory /web, the server will first look for -the HTML file /web/README.html and include it if found, otherwise -it will include the plain text file /web/README, if it exists. - +to include, and is taken to be relative to the location being indexed. +

+
+The filename argument is treated as a stub filename +in Apache 1.3.6 and earlier, and as a relative URI in later versions. +Details of how it is handled may be found under the description of +the HeaderName directive, which uses the +same mechanism and changed at the same time as ReadmeName. +

See also HeaderName.