I'll use your terminology of "Web Server" and "Apache Reverse Proxy" to refer to the two entities of interest here.
>But after adding apache reverse proxy, when the client hits the F5 URL - all >the subsequent requests are going to Web Server on 8080 port and getting >served from there instead of going via Apache Reverse Proxy. In brief, your "Apache Reverse Proxy" has to dynamically modify the content sent to the client, with references that point back at your "Apache Reverse Proxy". E.g. your "Web Server" will serve pages containing hrefs that point back at it, e.g. href=https://webserver:8080/f5-url. The "Apache Reverse Proxy" must substitute the href to point at itself instead, e.g. href="https://proxy-server:80/webserver/f5-url";. You configure the reverse proxy so that when it sees a HTTP request for a page containing "/webserver", it knows to proxy that request to https://webserver:8080. (There are many ways to configure this.) There is a lot more to this, since these substitutions have to happen *everywhere* an action would cause the client-browser to open a page to the "Web Server" or send content referencing the "Web Server". So, you have to perform substitutions in the html, css, javascript, http headers (e.g. cookies), etc. Getting all the substitutions correct for your web-application is quite the art. It will have to be validated each time you upgrade your backend web-application too. You are in for a journey. Start small, preferably with a simple web-app and grow in complexity from there. Some of these reverse-proxy scripts become quite complex and have dependencies on ordering of substitutions and a bunch of other challenges that you will only discover through trial-and-error. There are also many ways to substitute things, so that also requires experimenting to learn what works best for your application. There is a lot more to configuring an application to use the reverse-proxy than what I say here. Be meticulous and patient. Good luck. Matt. From: Sontakke, Sachin (NonEmp) <sachin.sonta...@kroger.com> Sent: Thursday, 23 January 2020 8:07 AM To: users@httpd.apache.org Subject: [users@httpd] query on apache reverse proxy I have a question regarding apache reverse proxy setup. We have a web application running on WebLogic; it's a typical 3 tier application. Flow is as follows:- Client=> F5 load balance=> Web Server listening on 80=> WebLogic App=> Oracle DB. Due to certain requirement we need to introduce Apache reverse proxy in front, so now flow will look like:- Client=> F5 load balance=> Apache Reverse Proxy listening on 80=> Web Server listening on 8080=> WebLogic App=> Oracle DB. But after adding apache reverse proxy, when the client hits the F5 URL - all the subsequent requests are going to Web Server on 8080 port and getting served from there instead of going via Apache Reverse Proxy. NOTE: Apache reverse proxy and Web server both are running on the same Host. May I know what could have gone wrong or any way I can troubleshoot this issue? Thanks, Sachin ________________________________ This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is confidential and protected by law from unauthorized disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
