From: Eric Covener Date: Sat, 20 Aug 2016 19:07:07 +0000 (+0000) Subject: xforms X-Git-Tag: 2.5.0-alpha~1232 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=2824969b40c8f953634f81d1fd2c1e76f83ed182;p=thirdparty%2Fapache%2Fhttpd.git xforms git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1757025 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_rewrite.html.en b/docs/manual/mod/mod_rewrite.html.en index d11985fbc4a..8d4e047ad90 100644 --- a/docs/manual/mod/mod_rewrite.html.en +++ b/docs/manual/mod/mod_rewrite.html.en @@ -26,7 +26,8 @@

Apache Module mod_rewrite

-

Available Languages:  en  | +

Available Languages:  edited  | + en  |  fr 

RewriteRule directives that substitute a relative path.

This directive is required when you use a relative path - in a substitution in per-directory (htaccess) context unless either + in a substitution in per-directory (htaccess) context unless any of the following conditions are true:

  • The original request, and the substitution, are underneath the @@ -1043,22 +1044,23 @@ RewriteRule "^/$" "/homepage.std.html" [L]

    Pattern is a perl compatible regular - expression. On the first RewriteRule, it is matched against - the (%-decoded) URL-path - of the request, or, in per-directory context (see below), the URL - path relative to that per-directory context. Subsequent patterns - are matched against the output of the last matching RewriteRule.

    + expression. What this pattern is compared against varies depending + on where the RewriteRule directive is defined.

    What is matched?

    In VirtualHost context, The Pattern will initially be matched against the part of the - URL after the hostname and port, and before the query string (e.g. "/app1/index.html").

    + URL after the hostname and port, and before the query string (e.g. "/app1/index.html"). + This is the (%-decoded) URL-path.

    In Directory and htaccess context, - the Pattern will initially be matched against the - filesystem path, after removing the prefix that led the server - to the current RewriteRule (e.g. "app1/index.html" - or "index.html" depending on where the directives are defined).

    + the Pattern is matched against the trailing portion of the currently + mapped filesystem path with the rules own directory path removed from the beginning + (up to and including a trailing slash). Directives such as DocumentRoot and Alias, or even the + result of previous RewriteRule substitutions, determine + the currently mapped filesystem path. The net result of this per-directory + prefix stripping is that rules in this context only match against the portion + of the currently mapped path "below" where they are defined.

    If you wish to match against the hostname, port, or query string, use a RewriteCond with the @@ -1086,13 +1088,7 @@ administrator has disabled override of FollowSymLinks for a user's directory, then you cannot use the rewrite engine. This restriction is required for security reasons.

  • -
  • When using the rewrite engine in .htaccess files the -per-directory prefix (that is, the URI path that leads to the directory -containing this .htaccess file) -is removed for the RewriteRule pattern matching -and added after any relative (not starting with a -slash or protocol name) substitution encounters the end of a rule set. -See the RewriteBase +
  • See the RewriteBase directive for more information regarding what prefix will be added back to relative substitutions.
  • @@ -1520,7 +1516,8 @@ redirection
    -

    Available Languages:  en  | +

    Available Languages:  edited  | + en  |  fr 

    top

    Comments

    Notice:
    This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our mailing lists.
Description:Provides a rule-based rewriting engine to rewrite requested @@ -123,7 +124,7 @@ URLs on the fly