From 79f90cac62e6793e56b2054521a9606b73287165 Mon Sep 17 00:00:00 2001
From: Nick Kew <niq@apache.org>
Date: Sun, 30 Aug 2009 02:57:58 +0000
Subject: [PATCH] Fix up doc note on ProxyPassMatch quirks - this wording seems
 to have got accepted in 2.2.x.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@809241 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/mod/mod_proxy.xml | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml
index 371e2a5ca4..4a2f0b4157 100644
--- a/docs/manual/mod/mod_proxy.xml
+++ b/docs/manual/mod/mod_proxy.xml
@@ -959,10 +959,18 @@ expressions</description>
     <code>http://example.com/foo/bar.gif</code> to be internally converted
     into a proxy request to <code>http://backend.example.com/foo/bar.gif</code>.</p>
     <note><title>Note</title>
-      The URL argument must be parsable as a URL <em>before</em> regexp
+      <p>The URL argument must be parsable as a URL <em>before</em> regexp
       substitutions (as well as after).  This limits the matches you can use.
-      See <a href="https://issues.apache.org/bugzilla/show_bug.cgi">PR 46665</a>
-      for details and workaround ideas.
+      For instance, if we had used</p>
+      <example>
+        ProxyPassMatch ^(/.*\.gif)$ http://backend.example.com:8000$1
+      </example>
+      <p>in our previous example, it would fail with a syntax error
+      at server startup.  This is a bug (PR 46665 in the ASF bugzilla),
+      and the workaround is to reformulate the match:</p>
+      <example>
+        ProxyPassMatch ^/(.*\.gif)$ http://backend.example.com:8000/$1
+      </example>
     </note>
     <p>The <code>!</code> directive is useful in situations where you don't want
     to reverse-proxy a subdirectory.</p>
-- 
2.50.1