Mailing List Archive

Typically, the solution is to avoid adding the double slashes to begin
with. If you show us your Proxy* directives, we can comment further.

On Mon, 11 Jul 2022 at 15:45, <jonmcalexander@wellsfargo.com.invalid> wrote:

> I am not an HTTPD expert and am running into issues where double-slashes
> are being added to the end of the ProxyPass and/or ProxyPassReverse
> statements in our mod_proxy configuration. What is the proper way to handle
> this issue with RewriteRules?
>
>
>
> Thanks,
>
>
>
> *Dream * Excel * Explore * Inspire*
>
> Jon McAlexander
>
> Senior Infrastructure Engineer
>
> Asst. Vice President
>
> He/His
>
>
>
> Middleware Product Engineering
>
> Enterprise CIO | EAS | Middleware | Infrastructure Solutions
>
>
>
> 8080 Cobblestone Rd | Urbandale, IA 50322
> MAC: F4469-010
>
> Tel 515-988-2508 | Cell 515-988-2508
>
>
>
> jonmcalexander@wellsfargo.com
>
> This message may contain confidential and/or privileged information. If
> you are not the addressee or authorized to receive this for the addressee,
> you must not use, copy, disclose, or take any action based on this message
> or any information herein. If you have received this message in error,
> please advise the sender immediately by reply e-mail and delete this
> message. Thank you for your cooperation.
>
>
>

Here you go. This is after converting from mod_jk to mod_proxy

<IfModule proxy_module>

SSLProxyEngine On
SSLProxyVerify off
SSLProxyCheckPeerName on
SSLProxyCheckPeerCN on
SSLProxyVerifyDepth 5
SSLProxyCACertificateFile caintermediate.pem
SSLProxyMachineCertificateFile Client.pem
ProxyRequests Off
BalancerPersist On

<Proxy balancer://ilocluster>
BalancerMember https://<myserver>:8305

ProxySet lbmethod=bybusyness
ProxySet stickysession=JSESSIONID
ProxySet scolonpathdelim=On

Order Deny,Allow
Deny from none
Allow from all
</Proxy>

ProxyPass /ilo balancer://ilocluster/ilo
ProxyPassReverse /ilo balancer://ilocluster/ilo

ProxyPass /ild balancer://ilocluster/ild
ProxyPassReverse /ild balancer://ilocluster/ild

</IfModule>

Ending up with double-slashes after ilo and ild in the URLs reported on the Tomcat side..

Now, we also have an SMSESSION cookie that needs to pass, but not sure you to get it into the mix as well as the JSESSION cookie.

Thank you,

Dream * Excel * Explore * Inspire
Jon McAlexander
Senior Infrastructure Engineer
Asst. Vice President
He/His

Middleware Product Engineering
Enterprise CIO | EAS | Middleware | Infrastructure Solutions

8080 Cobblestone Rd | Urbandale, IA 50322
MAC: F4469-010
Tel 515-988-2508 | Cell 515-988-2508

jonmcalexander@wellsfargo.com<mailto:jonmcalexander@wellsfargo.com>
This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.

From: Frank Gingras <thumbs@apache.org>
Sent: Monday, July 11, 2022 3:11 PM
To: users@httpd.apache.org
Subject: Re: [users@httpd] rewrite rule with ProxyPass and ProxyPassReverse

Typically, the solution is to avoid adding the double slashes to begin with. If you show us your Proxy* directives, we can comment further.

On Mon, 11 Jul 2022 at 15:45, <jonmcalexander@wellsfargo.com.invalid> wrote:
I am not an HTTPD expert and am running into issues where double-slashes are being added to the end of the ProxyPass and/or ProxyPassReverse statements in our mod_proxy configuration. What is the proper way to handle this issue with RewriteRules?

Thanks,

Dream * Excel * Explore * Inspire
Jon McAlexander
Senior Infrastructure Engineer
Asst. Vice President
He/His

Middleware Product Engineering
Enterprise CIO | EAS | Middleware | Infrastructure Solutions

8080 Cobblestone Rd | Urbandale, IA 50322
MAC: F4469-010
Tel 515-988-2508 | Cell 515-988-2508

jonmcalexander@wellsfargo.com<mailto:jonmcalexander@wellsfargo.com>
This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.