From: Marc Slemko Date: Wed, 2 Jul 1997 03:09:24 +0000 (+0000) Subject: HTML cleanups. weblint is your friend, and it is even right sometimes. X-Git-Tag: dg_last_1_2_doc_merge~1 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=44be91c6445e68b1dc80165b5519ee17a082564e;p=apache HTML cleanups. weblint is your friend, and it is even right sometimes. Reviewed by: Submitted by: Obtained from: git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@78494 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_rewrite.html b/docs/manual/mod/mod_rewrite.html index 8d432e4c4e..4cb6c83b85 100644 --- a/docs/manual/mod/mod_rewrite.html +++ b/docs/manual/mod/mod_rewrite.html @@ -44,7 +44,6 @@ substitution. It operates on the full URLs (including the PATH_INFO part) both in per-server context (httpd.conf) and per-dir context (.htaccess) and even can generate QUERY_STRING parts on result. The rewritten result can lead to internal sub-processing, external request redirection or to internal proxy throughput. -

The latest version can be found on
@@ -147,7 +146,7 @@ with a slash ('/') then it is assumed to be relative to the config.

- +
To disable the logging of rewriting actions it is not recommended to set Filename @@ -161,7 +160,7 @@ To disable logging either remove or comment out the

- +
SECURITY: See the Apache Security @@ -198,7 +197,7 @@ To disable the logging of rewriting actions simply set Level to 0. This disables all rewrite action logs.

- +
Notice: Using a high value for Level will slow down your Apache server dramatically! Use the rewriting logfile only for debugging or at least @@ -289,7 +288,7 @@ RewriteMap real-to-host txt:/path/to/file/map.real-to-user
  • DBM Hashfile Format

    This is a binary NDBM format file containing the - same contents as the Plain Text Format files. You can create + same contents as the Plain Text Format files. You can create such a file with any NDBM tool or with the dbmmanage program from the support directory of the Apache distribution.

    @@ -346,7 +345,7 @@ context it is of course possible to use this map in per-directory context.

    - +
    For plain text and DBM format files the looked-up keys are cached in-core until the mtime of the mapfile changes or the server does a @@ -384,7 +383,7 @@ will be usually be wrong! There you have to use the RewriteBase directive to specify the correct URL-prefix.

    - +
    So, if your webserver's URLs are not directly related to physical file paths, you have to use RewriteBase in every @@ -424,7 +423,7 @@ In the above example, a request to /xyz/oldstuff.html gets correctly rewritten to the physical file /abc/def/newstuff.html.

    - +
    For the Apache hackers:
    @@ -437,10 +436,10 @@ Request: /xyz/oldstuff.html Internal Processing: - /xyz/oldstuff.html -> /abc/def/oldstuff.html (per-server Alias) - /abc/def/oldstuff.html -> /abc/def/newstuff.html (per-dir RewriteRule) - /abc/def/newstuff.html -> /xyz/newstuff.html (per-dir RewriteBase) - /xyz/newstuff.html -> /abc/def/newstuff.html (per-server Alias) + /xyz/oldstuff.html -> /abc/def/oldstuff.html (per-server Alias) + /abc/def/oldstuff.html -> /abc/def/newstuff.html (per-dir RewriteRule) + /abc/def/newstuff.html -> /xyz/newstuff.html (per-dir RewriteBase) + /xyz/newstuff.html -> /abc/def/newstuff.html (per-server Alias) Result: /abc/def/newstuff.html @@ -471,7 +470,7 @@ sure the design and implementation is correct.

    The RewriteCond directive defines a rule condition. Precede a -RewriteRule directive with one or more RewriteCond +RewriteRule directive with one or more RewriteCond directives. The following rewriting rule is only used if its pattern matches the current @@ -562,7 +561,7 @@ IS_SUBREQ

    - +
    These variables all correspond to the similar named HTTP MIME-headers, C variables of the Apache server or struct tm fields of the Unix @@ -770,7 +769,7 @@ for special cases where it is better to match the negative pattern or as a last default rule.

    - +
    Notice! When using the NOT character to negate a pattern you cannot have grouped wildcard parts in the pattern. This is impossible because when @@ -814,7 +813,7 @@ conjunction with the C (chain) flag to be able to have more than one pattern to be applied before a substitution occurs.

    - +
    Notice: There is a special feature. When you prefix a substitution field with http://thishost[:thisport] then @@ -962,7 +961,7 @@ comma-separated list of the following flags: typical example is the use of mod_alias and mod_rewrite..

    - +
    - -
    For the Apache hackers:
    @@ -995,7 +994,7 @@ comma-separated list of the following flags:

    - +
    Remember: Never forget that Pattern gets applied to a complete URL in per-server configuration files. But in per-directory configuration @@ -1012,7 +1011,7 @@ external redirect or proxy throughput (if flag P is used!) is forced!

    - +
    Notice! To enable the rewriting engine for per-directory configuration files you need to set ``RewriteEngine On'' in these files and @@ -1120,10 +1119,6 @@ request ``GET /somepath/localpath/pathinfo'':
    -

    -

    Example:

    diff --git a/docs/manual/mod/mod_userdir.html b/docs/manual/mod/mod_userdir.html index 50ac784465..fb0a201c89 100644 --- a/docs/manual/mod/mod_userdir.html +++ b/docs/manual/mod/mod_userdir.html @@ -66,15 +66,15 @@ treated as a filename pattern, and is used to turn the name into a directory specification. A request for http://www.foo.com/~bob/one/two.html will be translated to: 

    -UserDir public_html     -> ~bob/public_html/one/two.html
-UserDir /usr/web        -> /usr/web/bob/one/two.html
-UserDir /home/*/www     -> /home/bob/www/one/two.html
+UserDir public_html     -> ~bob/public_html/one/two.html
+UserDir /usr/web        -> /usr/web/bob/one/two.html
+UserDir /home/*/www     -> /home/bob/www/one/two.html
    The following directives will send redirects to the client: 
    -UserDir http://www.foo.com/users   -> http//www.foo.com/users/bob/one/two.html
-UserDir http://www.foo.com/*/usr   -> http://www.foo.com/bob/usr/one/two.html
-UserDir http://www.foo.com/~*/     -> http://www.foo.com/~bob/one/two.html
+UserDir http://www.foo.com/users   -> http//www.foo.com/users/bob/one/two.html
+UserDir http://www.foo.com/*/usr   -> http://www.foo.com/bob/usr/one/two.html
+UserDir http://www.foo.com/~*/     -> http://www.foo.com/~bob/one/two.html