Hi HB, On Sun, Jun 10, 2018 at 5:05 PM, Herb Burnswell <herbert.burnswell@xxxxxxxxx> wrote: > > I need the proxy to work as: https://vanity.example.com > > I'm thinking this may require use of RewriteCond directives, however I may > be going about this wrong. > > Is there a way to define an 'active' request to avoid looping through the > same ProxyPass or ProxyPassMatch needed for an initial request? I'm not sure to understand, you want the request to be without "/frontpage" suffix between the browsers and the proxy (i.e. https://vanity.example.com) and with the suffix added between proxy and the backend (i.e. https://vanity.example.com/frontpage), right? If this is the case, maybe something like this then (the opposite rewrite of what I've told you so far :p ): ProxyPass / balancer://applicationcluster/frontpage/ ... ProxyPassReverse / balancer://applicationcluster/frontpage/ You would then remove the "/frontpage" suffix from the BalancerMember declarations. Since ProxyPass would do the rewrite from "/" => "/frontpage/", you don't need mod_rewrite here. There is no case where "/frontpage" (without the trailing '/') can arrive on the backend side since ProxyPass will always start the forwarded path with "/frontpage/", but I suppose "/frontpage" and "/frontpage/" work equally on the backend no? Hope that helps.. Regards, Yann. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx