PR46665 workaround docs: remove ambiguity about how it will fail if an

expression is rejected.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@808499 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml
index dded018d46d693eb067bdd927d287052faa7e85d..09e29da066d579767050ce6af4f61131ad26b2eb 100644 (file)
--- a/docs/manual/mod/mod_proxy.xml
+++ b/docs/manual/mod/mod_proxy.xml
@@ -951,9 +951,9 @@ expressions</description>
       <example>
         ProxyPassMatch ^(/.*\.gif)$ http://backend.example.com:8000$1
       </example>
-      <p>in our previous example, it would fail.  This is a bug
-      (PR 46665 in the ASF bugzilla), and the workaround is to
-      reformulate the match, so the above will work if expressed as</p>
+      <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>