From: Daniel Gruno ~ character. For example:
<Directory ~ "^/www/.*/[0-9]{3}">
+
+<Directory ~ "^/www/.*/[0-9]{3}">
+
+</Directory>
+
would match directories in /www/ that consisted of
@@ -930,7 +934,11 @@ the contents of file-system directories matching a regular expression.
However, it takes as an argument a
regular expression. For example:
<DirectoryMatch "^/www/(.+/)?[0-9]{3}">
+
+<DirectoryMatch "^/www/(.+/)?[0-9]{3}">
+ # ...
+</DirectoryMatch>
+
would match directories in /www/ that consisted of three
@@ -1722,7 +1730,11 @@ filenames
can also be used, with the addition of the
~ character. For example:
<Files ~ "\.(gif|jpe?g|png)$">+
+<Files ~ "\.(gif|jpe?g|png)$"> + #... +</Files> +
would match most common Internet graphics formats. <FilesMatch> is preferred,
@@ -2603,7 +2615,8 @@ URLs
<Location /private1>
-# ...
+ # ...
+</Location>
@@ -2613,7 +2626,8 @@ URLs
<Location /private2/>
-# ...
+ # ...
+</Location>
@@ -2641,7 +2655,11 @@ URLs
can also be used, with the addition of the ~
character. For example:
- <Location ~ "/(extra|special)/data">+
+<Location ~ "/(extra|special)/data"> + #... +</Location> +
would match URLs that contained the substring /extra/data
@@ -2708,7 +2726,11 @@ matching URLs
it takes a regular expression
as an argument instead of a simple string. For example:
<LocationMatch "/(extra|special)/data">+
+<LocationMatch "/(extra|special)/data"> + # ... +</LocationMatch> +
would match URLs that contained the substring /extra/data