https://bz.apache.org/bugzilla/show_bug.cgi?id=65055
Bug ID: 65055
Summary: tiny ambiguity of <Directory>'s/<Location>'s
documentation
Product: Apache httpd-2
Version: 2.5-HEAD
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Documentation
Assignee: docs@httpd.apache.org
Reporter: calestyo@scientia.net
Target Milestone: ---
Hey.
mod/core.html says for <Directory>:
"or a wild-card string using Unix shell-style matching. In a wild-card string,
? matches any single character, and * matches any sequences of characters."
In Unix shell-style matching "*" is actually any character sequence (i.e. also
no characters at all).
In Apache e.g. the following directive:
<Directory /var/www/*/foo>
would match:
/var/www/bar/foo
/var/www/baz/foo
but not
/var/www//foo
/var/www/foo
While this is consistent with the Unix shell style matching, the text alone
could still be confusing to readers, so perhaps it makes sense to either remark
that "/*/" still requires at least one character (not being . or ..) or just
illustrate it with an example.
The same is the case for <Location>.
But I guess it's *not* for the regexp versions, or is it?
Cheers,
Chris.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Bug ID: 65055
Summary: tiny ambiguity of <Directory>'s/<Location>'s
documentation
Product: Apache httpd-2
Version: 2.5-HEAD
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Documentation
Assignee: docs@httpd.apache.org
Reporter: calestyo@scientia.net
Target Milestone: ---
Hey.
mod/core.html says for <Directory>:
"or a wild-card string using Unix shell-style matching. In a wild-card string,
? matches any single character, and * matches any sequences of characters."
In Unix shell-style matching "*" is actually any character sequence (i.e. also
no characters at all).
In Apache e.g. the following directive:
<Directory /var/www/*/foo>
would match:
/var/www/bar/foo
/var/www/baz/foo
but not
/var/www//foo
/var/www/foo
While this is consistent with the Unix shell style matching, the text alone
could still be confusing to readers, so perhaps it makes sense to either remark
that "/*/" still requires at least one character (not being . or ..) or just
illustrate it with an example.
The same is the case for <Location>.
But I guess it's *not* for the regexp versions, or is it?
Cheers,
Chris.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org