coar 99/01/08 14:37:04
Modified: . STATUS
htdocs/manual/mod mod_mime.html
Log:
Add the documentation for the RemoveHandler directive.
Revision Changes Path
1.596 +1 -3 apache-1.3/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/apache-1.3/STATUS,v
retrieving revision 1.595
retrieving revision 1.596
diff -u -r1.595 -r1.596
--- STATUS 1999/01/08 22:20:36 1.595
+++ STATUS 1999/01/08 22:37:02 1.596
@@ -1,5 +1,5 @@
1.3 STATUS:
- Last modified at [$Date: 1999/01/08 22:20:36 $]
+ Last modified at [$Date: 1999/01/08 22:37:02 $]
Release:
@@ -46,8 +46,6 @@
Documentation that needs writing:
* Document compilation on Win95 and NT
-
- * RemoveHandler directive needs docs
* Need a document explaining mod_rewrite/"UseCanonicalName off" based
virtualhosting. (If it exists already I can't find it easily.)
1.30 +47 -1 apache-1.3/htdocs/manual/mod/mod_mime.html
Index: mod_mime.html
===================================================================
RCS file: /home/cvs/apache-1.3/htdocs/manual/mod/mod_mime.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- mod_mime.html 1998/12/27 02:38:15 1.29
+++ mod_mime.html 1999/01/08 22:37:03 1.30
@@ -48,7 +48,7 @@
value of the <CODE>Last-Modified</CODE> header. Thus, previously cached
copies may still be used by a client or proxy, with the previous headers.
-<A NAME="multipleext"><H2>Files with Multiple Extensions</H2></A>
+<H2><A NAME="multipleext">Files with Multiple Extensions</A></H2>
Files can have more than one extension, and the order of the
extensions is <i>normally</i> irrelevant. For example, if the file
@@ -92,6 +92,7 @@
<LI><A HREF="#addtype">AddType</A>
<LI><A HREF="#defaultlanguage">DefaultLanguage</A>
<LI><A HREF="#forcetype">ForceType</A>
+<LI><A HREF="#removehandler">RemoveHandler</A>
<LI><A HREF="#sethandler">SetHandler</A>
<LI><A HREF="#typesconfig">TypesConfig</A>
</UL>
@@ -389,6 +390,51 @@
</PRE>
<P>Note that this will override any filename extensions that might determine
the media type.</P><HR>
+
+<H2><A NAME="removehandler">RemoveHandler</A></H2>
+
+<A
+ HREF="directive-dict.html#Syntax"
+ REL="Help"
+><STRONG>Syntax:</STRONG></A> RemoveHandler <EM>extension
extension...</EM><BR>
+<A
+ HREF="directive-dict.html#Context"
+ REL="Help"
+><STRONG>Context:</STRONG></A> directory, .htaccess<BR>
+<A
+ HREF="directive-dict.html#Status"
+ REL="Help"
+><STRONG>Status:</STRONG></A> Base<BR>
+<A
+ HREF="directive-dict.html#Module"
+ REL="Help"
+><STRONG>Module:</STRONG></A> mod_mime<BR>
+<A
+ HREF="directive-dict.html#Compatibility"
+ REL="Help"
+><STRONG>Compatibility:</STRONG></A> RemoveHandler is only available in
Apache
+1.3.4 and later.<P>
+
+<P>
+The <SAMP>RemoveHandler</SAMP> directive removes any
+handler associations for files with the given extensions.
+This allows <CODE>.htaccess</CODE> files in subdirectories to undo
+any associations inherited from parent directories or the server
+config files. An example of its use might be:
+</P>
+<DL>
+ <DT><CODE>/foo/.htaccess:</CODE></DT>
+ <DD><CODE>AddHandler server-parsed .html</CODE></DD>
+ <DT><CODE>/foo/bar/.htaccess:</CODE></DT>
+ <DD><CODE>RemoveHandler .html</CODE></DD>
+</DL>
+<P>
+This has the effect of returning <SAMP>.html</SAMP> files in the
+<SAMP>/foo/bar</SAMP> directory to being treated as normal
+files, rather than as candidates for parsing (see the
+<A HREF="mod_include.html"><SAMP>mod_include</SAMP></A> module).
+</P>
+<HR>
<H2><A NAME="sethandler">SetHandler</A></H2>
