From e18ab1713d44f4523af7f97438d24dab249763a3 Mon Sep 17 00:00:00 2001
From: "Ralf S. Engelschall" <rse@apache.org>
Date: Thu, 10 Feb 2000 16:43:57 +0000
Subject: [PATCH] Make sure we don't receive another PR where a user tried to
 take the solutions exactly as written down without noticing that they usually
 always have to be adjusted for local contexts.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@84605 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/misc/rewriteguide.html | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/manual/misc/rewriteguide.html b/docs/manual/misc/rewriteguide.html
index bfc6bbd5c0..48d0e88228 100644
--- a/docs/manual/misc/rewriteguide.html
+++ b/docs/manual/misc/rewriteguide.html
@@ -57,12 +57,14 @@ collected from other peoples solutions in the past. Feel free to learn the
 black magic of URL rewriting from these examples.
 
 <P>
+<TABLE BGCOLOR="#FFE0E0" BORDER="0" CELLSPACING="0" CELLPADDING="5"><TR><TD>
 ATTENTION: Depending on your server-configuration it can be necessary to
 slightly change the examples for your situation, e.g. adding the [PT] flag
 when additionally using mod_alias and mod_userdir, etc. Or rewriting a ruleset
 to fit in <CODE>.htaccess</CODE> context instead of per-server context. Always try
 to understand what a particular ruleset really does before you use it. It
 avoid problems.
+</TD></TR></TABLE>
 
 <H1>URL Layout</H1>
 
-- 
2.50.1