You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2010/10/05 20:56:06 UTC
DO NOT REPLY [Bug 50048] New: ProxyPass(Match) within
Location(Match)
https://issues.apache.org/bugzilla/show_bug.cgi?id=50048
Summary: ProxyPass(Match) within Location(Match)
Product: Apache httpd-2
Version: 2.3-HEAD
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Documentation
AssignedTo: bugs@httpd.apache.org
ReportedBy: lmeyer@vmware.com
ProxyPass can get its first argument (the path) from a wrapping Location block.
ProxyPassMatch can get its first argument (the regex) from a wrapping
LocationMatch (or Location ~, which I won't mention again) block.
The ProxyPass docs are pretty clear about the first case. They don't really
mention the second case, and also don't describe what happens if you mix and
don't match - in particular, a ProxyPass within LocationMatch is probably not
going to do what the user hopes. And also, ProxyPassReverse is only discussed
in the context of Location.
For any who wonder - my understanding is that when these directives are used
inside a Location or LocationMatch block, the argument to the block is used
verbatim as the argument to the directive. When one is expecting a regex and
the other a path, results may be surprising, but httpd will not complain about
the syntax.
I propose changes to three sections:
1) http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypass
Mention that if you're trying to put this inside LocationMatch, you probably
want the ProxyPassMatch directive instead.
2) http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypassmatch
Explain that inside LocationMatch, the first argument comes from the block.
Currently the syntax marks the regex as optional, while not explaining where it
would come from.
3) http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypassreverse
Explain that inside Location or LocationMatch, the first argument comes from
the block, and that this is probably not desirable inside LocationMatch
(perhaps there should be a ProxyPassReverseMatch?).
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 50048] ProxyPass(Match) within Location(Match)
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=50048
--- Comment #1 from Luke Meyer <lm...@vmware.com> 2010-10-06 14:01:30 EDT ---
Created an attachment (id=26127)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=26127)
Proposed patch for the mod_proxy docs
Attaching proposed changes - would appreciate someone evaluating and applying
it.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 50048] ProxyPass(Match) within Location(Match)
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=50048
Eric Covener <co...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #2 from Eric Covener <co...@gmail.com> 2010-10-11 15:16:36 EDT ---
Thanks Luke -- committed and backported to 2.2.x in r1021471.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org