@@ -953,7 +953,10 @@ expressions</description>
953953 <p >When used inside a <directive type =" section" module =" core"
954954 >Location</directive > section, the first argument is omitted and the local
955955 directory is obtained from the <directive type =" section" module =" core"
956- >Location</directive >. The same will occur inside a
956+ >Location</directive >. When used outside a <directive type =" section"
957+ module =" core" >Location</directive > or <directive type =" section"
958+ module =" core" >LocationMatch</directive > section, the
959+ <var >path</var > argument is required. The same will occur inside a
957960 <directive type =" section" module =" core" >LocationMatch</directive > section;
958961 however, ProxyPass does not interpret the regexp as such, so it is necessary
959962 to use <directive >ProxyPassMatch</directive > in this situation instead.</p >
@@ -1620,7 +1623,10 @@ ProxyPassMatch "^/(.*\.gif)$" "http://backend.example.com/$1"
16201623 <p >When used inside a <directive type =" section" module =" core"
16211624 >LocationMatch</directive > section, the first argument is omitted and the
16221625 regexp is obtained from the <directive type =" section" module =" core"
1623- >LocationMatch</directive >.</p >
1626+ >LocationMatch</directive >. When used outside a <directive type =" section"
1627+ module =" core" >Location</directive > or <directive type =" section"
1628+ module =" core" >LocationMatch</directive > section, the
1629+ <var >regex</var > argument is required.</p >
16241630
16251631 <p >If you require a more flexible reverse-proxy configuration, see the
16261632 <directive module =" mod_rewrite" >RewriteRule</directive > directive with the
@@ -1741,7 +1747,10 @@ ProxyPassReverseCookiePath "/" "/mirror/foo/"
17411747 <p >When used inside a <directive type =" section" module =" core"
17421748 >Location</directive > section, the first argument is omitted and the local
17431749 directory is obtained from the <directive type =" section" module =" core"
1744- >Location</directive >. The same occurs inside a <directive type =" section"
1750+ >Location</directive >. When used outside a <directive type =" section"
1751+ module =" core" >Location</directive > or <directive type =" section"
1752+ module =" core" >LocationMatch</directive > section, the
1753+ <var >path</var > argument is required. The same occurs inside a <directive type =" section"
17451754 module =" core" >LocationMatch</directive > section, but will probably not work as
17461755 intended, as ProxyPassReverse will interpret the regexp literally as a
17471756 path; if needed in this situation, specify the ProxyPassReverse outside
0 commit comments