On 7/24/12 6:03 PM, tom ryan wrote:
On Wed, Jul 25, 2012 at 12:43 AM, Nick Kew <[email protected]> wrote:
On 25 Jul 2012, at 00:14, Leif Hedstrom wrote:
Yeah, the reverse maps are duplicated (you can't have two reverse maps for the
same URL, how would it know which one to pick?).
It would need to be context-sensitive.
It works in HTTPD without problems: just put each reverse_map
in its own <Location>, so the server knows which applies to a request.
Wouldn't that be achieved by appending a path to the URL used in the
example? Or equivalently, would that suggestion not fail for the root
path of two sites (or any identical path, for that matter)? HTTPD
Yes, if you provide more specific remap rules (with paths etc.) such that
the mapping is deterministic, it should work.
can't take two ReverseProxyPass statements for the same thing.
Anyway, It looks to me like the OP's examples will have the origin not
knowing which page to serve correctly in all cases, on the forward map
too - both map rules will end up with the origin serving content for
server1.myname.com, no?
I suspect he uses "pristine host header", which means he can distinguish the
requests based on normal vhost rules.
Cheers,
-- Leif
