From 990fe8636a565582f75ac20268a4b4c0471f4caa Mon Sep 17 00:00:00 2001
From: Joshua Slive The following directive must be given for the directories
containing the shtml files (typically in a
This directive changes the string that mod_include looks for
- to mark the end of a include command.<Directory>
section, but this directive is
- also valid .htaccess files if AllowOverride
+ also valid in .htaccess files if
AllowOverride
Options
is set):
- in foo
+ in foo
<!--#elif expr="\"$DOCUMENT_URI\" = \"/bar/file.html\"" -->
- in bar
+ in bar
<!--#else -->
- in neither
+ in neither
<!--#endif -->
This directive changes the string that mod_include looks for to mark an include element to process.
-You may want to use this option if have 2 servers parsing the +
You may want to use this option if you have 2 servers parsing the output of a file each processing different commands (possibly at different times).
The XBitHack directives controls the parsing of ordinary
diff --git a/docs/manual/mod/mod_so.xml b/docs/manual/mod/mod_so.xml
index b5aee029eb..1c633d9eec 100755
--- a/docs/manual/mod/mod_so.xml
+++ b/docs/manual/mod/mod_so.xml
@@ -4,14 +4,11 @@
On Unix, the loaded code typically comes from shared object
files (usually with In previous releases, the functionality of this module was
- provided for Unix by mod_dld, and for Windows by mod_dll. On
- Windows, mod_dll was used in beta release 1.3b1 through 1.3b5.
- mod_so combines these two modules into a single module for all
- operating systems..so
extension), on Windows
this may either the .so
or .dll
- extension. This module is only available in Apache 1.3 and
- up.
Apache 1.3 modules cannot be directly used with Apache 2.0 - the module must be modified to dynamically @@ -44,6 +35,7 @@
The module name format changed for Windows with Apache 1.3.15 and 2.0 - the modules are now named as mod_foo.so
+While mod_so still loads modules with
ApacheModuleFoo.dll names, the new naming convention is
preferred; if you are converting your loadable module for 2.0,
@@ -113,7 +105,6 @@