Bug 65055 - tiny ambiguity of <Directory>'s/<Location>'s documentation
Summary: tiny ambiguity of <Directory>'s/<Location>'s documentation
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 2.5-HEAD
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: HTTP Server Documentation List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-05 01:14 UTC by Christoph Anton Mitterer
Modified: 2021-01-05 01:14 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Anton Mitterer 2021-01-05 01:14:33 UTC
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.