Hi, Thank you for the response.
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? Thanks, HB On Sat, Jun 9, 2018 at 1:24 AM, Yann Ylavic <ylavic....@gmail.com> wrote: > Hi, > > On Fri, Jun 8, 2018 at 9:07 PM, Herb Burnswell > <herbert.burnsw...@gmail.com> wrote: > > > > That being said I did test with modifying the ProxyPass and > ProxyPassReverse > > as you suggested, and it does work if an ending forward slash is added to > > the end of the URL: > > > > https://vanity.example.com/frontpage/ > > > > Given that bit of information, is there a way to get it to work without > > needing to add the '/frontpage/' path to the URL? > > Possibly: > ProxyPass /frontpage balancer://applicationcluster ... > or: > ProxyPassMatch ^/frontpage(/.*)?$ balancer://applicationcluster$1 ... > ? > > With: > ProxyPassReverse /frontpage balancer://applicationcluster > this time. > > Regards, > Yann. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > >