Re: [users@httpd] mod_proxy_http rewrite problem

It works It works with the ProxyPassReverse included. Yann - Thank you very much for all of your help, it's greatly appreciated.. Best, HB On Wed, Jun 20, 2018 at 7:54 AM, Yann Ylavic wrote: > On Tue, Jun 19, 2018 at 11:26 PM, Herb Burnswell > wrote: > > > > Attached is the error_log

Re: [users@httpd] mod_proxy_http rewrite problem

On Tue, Jun 19, 2018 at 11:26 PM, Herb Burnswell wrote: > > Attached is the error_log (scrubbed, may be some replace oddities, but you > can see the progression..). OK, it seems that the ProxyPass(es) order matters actually. How about: ProxyPass /frontpage/

Re: [users@httpd] mod_proxy_http rewrite problem

On Fri, Jun 15, 2018 at 9:33 PM, Herb Burnswell wrote: >> What if you remove the ProxyPassReverse, leaving the 2 ProxyPass only? > > Unfortunately no, without the ProxyPassReverse directive the behavior is the > same, it just loops. The 302's are in the access log over and over: > > 10.24.3.10

Re: [users@httpd] mod_proxy_http rewrite problem

> Or if you want to masquerade /frontpage completetly, you could use > mod_proxy_html to rewrite response URLs on the fly. Anybody have suggestions on how to masquerade /frontpage to rewrite responses? On Fri, Jun 15, 2018 at 12:33 PM, Herb Burnswell < herbert.burnsw...@gmail.com> wrote: > >

Re: [users@httpd] mod_proxy_http rewrite problem

> What if you remove the ProxyPassReverse, leaving the 2 ProxyPass only? Thanks Yann. Unfortunately no, without the ProxyPassReverse directive the behavior is the same, it just loops. The 302's are in the access log over and over: 10.24.3.10 - - [15/Jun/2018:12:16:40 -0700] "GET

Re: [users@httpd] mod_proxy_http rewrite problem

On Fri, Jun 15, 2018 at 12:34 AM, Herb Burnswell wrote: > >> If you accept that /frontpage path going up to the client/browser once >> the first / works, then you can: >>ProxyPass / balancer://applicationcluster/frontpage/ ... >>ProxyPass /frontpage/

Re: [users@httpd] mod_proxy_http rewrite problem

Thanks. > If you accept that /frontpage path going up to the client/browser once > the first / works, then you can: >ProxyPass / balancer://applicationcluster/frontpage/ ... >ProxyPass /frontpage/ balancer://applicationcluster/frontpage/ ... >ProxyPassReverse /

Re: [users@httpd] mod_proxy_http rewrite problem

On Thu, Jun 14, 2018 at 9:16 PM, Herb Burnswell wrote: > Community, > > Is this issue that I'm struggling with really that large of a challenge? If > it is, that's fine, I'm trying to judge if it's something that I should > abandon or if it can be done at all.. Not that much challenging I

Re: [users@httpd] mod_proxy_http rewrite problem

Community, Is this issue that I'm struggling with really that large of a challenge? If it is, that's fine, I'm trying to judge if it's something that I should abandon or if it can be done at all.. Thanks, HB On Sun, Jun 10, 2018 at 9:23 PM, Herb Burnswell wrote: > Thanks again Yann. > > >

Re: [users@httpd] mod_proxy_http rewrite problem

Thanks again Yann. > 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? You are

Re: [users@httpd] mod_proxy_http rewrite problem

Hi HB, On Sun, Jun 10, 2018 at 5:05 PM, Herb Burnswell 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

Re: [users@httpd] mod_proxy_http rewrite problem

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

Re: [users@httpd] mod_proxy_http rewrite problem

Hi, On Fri, Jun 8, 2018 at 9:07 PM, Herb Burnswell 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

Re: [users@httpd] mod_proxy_http rewrite problem

Yann, Thank you for the response. I should have added to my post that we need the proxy to work without requiring adding a path to the vanity URL as: https://vanity.example.com/frontpage That being said I did test with modifying the ProxyPass and ProxyPassReverse as you suggested, and it does

Re: [users@httpd] mod_proxy_http rewrite problem

Hello, On Thu, Jun 7, 2018 at 9:36 PM, Herb Burnswell wrote: > > RewriteEngine On > RewriteRule "^/frontpage(.+)" "$1" [R,L] What about this instead of the above: ProxyPass /frontpage/ balancer://applicationcluster/ stickysession=JSESSIONID ProxyPassReverse

[users@httpd] mod_proxy_http rewrite problem

All, I'm facing what seemingly is a very difficult challenge, tyring to set up a proxy to a backend application. I say 'seemingly very difficult' because I have reached out to the HTTPD community, codementor.io (offering money for help), as well as consultants who say they really are not skilled