From: Rich Bowen Date: Tue, 14 Apr 2026 19:23:12 +0000 (+0000) Subject: Wrap module names in X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=eddc2be2a070118344446cc1e4279ebb957f0e11;p=thirdparty%2Fapache%2Fhttpd.git Wrap module names in git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1933060 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/rewrite/access.xml b/docs/manual/rewrite/access.xml index e214ea7a4e..dceb672bab 100644 --- a/docs/manual/rewrite/access.xml +++ b/docs/manual/rewrite/access.xml @@ -31,7 +31,7 @@ reference documentation. It describes how you can use mod_rewrite to control access to various resources, and other related techniques. -This includes many examples of common uses of mod_rewrite, +This includes many examples of common uses of mod_rewrite, including detailed descriptions of how each works.

Note that many of these examples won't work unchanged in your @@ -118,7 +118,7 @@ RewriteRule "\.(gif|jpg|png)$" "http://other.example.com/image.gif" [R,NC]

If all you wish to do is deny access to the resource, rather than redirecting that request elsewhere, this can be - accomplished without the use of mod_rewrite:

+ accomplished without the use of mod_rewrite:

SetEnvIf Referer example\.com localreferer @@ -150,7 +150,7 @@ SetEnvIf Referer example\.com localreferer

Note that there are methods of accomplishing this which do - not use mod_rewrite. Note also that any technique that relies on + not use mod_rewrite. Note also that any technique that relies on the clients USER_AGENT string can be circumvented very easily, since that string can be changed.

@@ -179,7 +179,7 @@ RewriteRule "^/secret/files/" "-" [F]

- Rather than using mod_rewrite for this, you can accomplish the + Rather than using mod_rewrite for this, you can accomplish the same end using alternate means, as illustrated here:

diff --git a/docs/manual/rewrite/avoid.xml b/docs/manual/rewrite/avoid.xml index 2dab02fefe..5ae7a6c379 100644 --- a/docs/manual/rewrite/avoid.xml +++ b/docs/manual/rewrite/avoid.xml @@ -156,7 +156,7 @@ server.

Virtual Hosting

Although it is possible to handle virtual hosts -with mod_rewrite, it is seldom the right way. Creating individual +with mod_rewrite, it is seldom the right way. Creating individual VirtualHost blocks is almost always the right way to go. In the event that you have an enormous number of virtual hosts, consider using diff --git a/docs/manual/rewrite/index.xml b/docs/manual/rewrite/index.xml index b7403198a3..444ad90231 100644 --- a/docs/manual/rewrite/index.xml +++ b/docs/manual/rewrite/index.xml @@ -52,13 +52,13 @@ passthrough, depending on what flags you attach to the rules.

-

Since mod_rewrite is so powerful, it can indeed be rather +

Since mod_rewrite is so powerful, it can indeed be rather complex. This document supplements the reference documentation, and attempts to allay some of that complexity, and provide highly annotated examples of common scenarios that you may handle with - mod_rewrite. But we also attempt to show you when you should not - use mod_rewrite, and use other standard Apache features instead, + mod_rewrite. But we also attempt to show you when you should not + use mod_rewrite, and use other standard Apache features instead, thus avoiding this unnecessary complexity.