https://bz.apache.org/bugzilla/show_bug.cgi?id=60377
Philippe Cloutier <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED --- Comment #4 from Philippe Cloutier <[email protected]> --- Hi Rich, > Three changes to RewriteRule/RewriteCond documentation: > 1. Changed "The directory path where the rule is defined" to "The > directory-path for which the rule is defined" — clarifies that it's the > target directory, not the location of the config file. Also hyphenated > "directory-path" to match the syntax definition. Oh, I missed that, thanks! > 2. Replaced "perl compatible regular expression" with a glossary-linked > "regular expression" in both RewriteRule and RewriteCond, consistent with > the directive-dict syntax reference. > > Thanks for the report. Thanks to you All of these improve, but regarding the main issue, I only provided an example. The following sentences are also affected > In per-directory context (Directory and .htaccess), the Pattern is matched > against only a partial path, for example a request of "/app1/index.html" may > result in comparison against "app1/index.html" or "index.html" depending on > where the RewriteRule is defined. > The net result of this per-directory prefix stripping is that rules in this > context only match against the portion of the currently mapped filesystem > path "below" where the rule is defined. > If you wish to match against the full URL-path in a per-directory (htaccess) > RewriteRule, use the %{REQUEST_URI} variable in a RewriteCond. > To enable the rewrite engine in this context, you need to set "RewriteEngine > On" and "Options FollowSymLinks" must be enabled. If your administrator has > disabled override of FollowSymLinks for a user's directory, then you cannot > use the rewrite engine. Probably also: > For example, if you specify a Substitution string of /www/file.html, then > this will be treated as a URL-path unless a directory named www exists at the > root or your file-system (or, in the case of using rewrites in a .htaccess > file, relative to your document root), in which case it will be treated as a > file-system path By the way, there is the opposite problem in the following, which visibly implies .htaccess context is excluded from per-directory context (which does not match the above description): > Also prevents further execution of rewrite rules in per-directory and > .htaccess context. (Available in 2.3.9 and later) Same with last|L. 🅭🄍: https://www.philippecloutier.com/Common+infrastructure+licensing#its -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
