Forum Discussion
Reverse Proxy - POST redirecting to another port
Hi All,
Finally I got my BIG-IP set as a reverse proxy (for those who are interested please see case ‘reverse proxy’ for details). In my setup I use REWRITE profile linked to the VS (rewriting incoming external URIs to proper internal URIs) and POLICY redirecting https requests to the proper POOLs of servers based on incoming URI. That works fine.
However one of the webservers (‘server-001’ in simple example below) runs 2 web engines – IIS on port 443, which works fine with today’s setup, and a Tomcat running on port 8443 – which doesn’t work.
Tomcat engine is used for the feature of attaching files via Upload Servlet.
The scenario looks as follows:
-
I log to ISS webserver via BIG-IP / reverse proxy -works fine
-
Once I want to upload a file to that IIS webserver, the webserver tries redirecting my request to port 8443 – and here I get an error on the client on the external side
oUnable to connect - and that is correct since host server-002 is not known/reachable on external side of BIG-IP
o In other words it looks like the last rule in my REWRITE profile doesn’t work as it should – I expected to get link on my client translated to https://test.com:8443/ and that link would be then redirect to the other VS that listens on port 8443
oPlease see simple drawing below for details
Do you have any thoughts about it? Not sure if my question is clear enough. Also note that redirecting to port 8443 comes from webserver with a POST METHOD – could it be that POST is not cached by the REWRITE profile?
Many thanks
Michal
Reverse Proxy logical setup and REWRITE profile:
screen shot from client:
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com