From: Joshua Slive
While filenames are generally case-insensitive on
+ Windows, URLs are still treated internally as case-sensitive
+ before they are mapped to the filesystem. For example, the
+ <Location>
,
+ Alias
, and ProxyPass
directives all use
+ case-sensitive arguments. For this reason, it is particularly
+ important to use the <Directory>
directive when attempting
+ to limit access to content in the filesystem, since this
+ directive applies to any content in a directory, regardless of
+ how it is accessed. If you wish to assure that only lowercase
+ is used in URLs, you can use something like:
+ RewriteEngine On
+ RewriteMap lowercase int:tolower
+ RewriteCond %{REQUEST_URI} [A-Z]
+ RewriteRule (.*) ${lowercase:$1} [R,L]
+
Apache for Windows contains the ability to load modules at runtime, without recompiling the server. If Apache is compiled normally, it will install a number of optional modules in the diff --git a/docs/manual/platform/windows.xml b/docs/manual/platform/windows.xml index 8f581187d0..e549739c3b 100644 --- a/docs/manual/platform/windows.xml +++ b/docs/manual/platform/windows.xml @@ -225,6 +225,27 @@ not backslashes. Drive letters can be used; if omitted, the drive with the Apache executable will be assumed.
While filenames are generally case-insensitive on
+ Windows, URLs are still treated internally as case-sensitive
+ before they are mapped to the filesystem. For example, the
+
Apache for Windows contains the ability to load modules at runtime, without recompiling the server. If Apache is compiled normally, it will install a number of optional modules in the