Forum Discussion

Techgeeeg_28888's avatar
Icon for Nimbostratus rankNimbostratus
Feb 04, 2012

Oracle Server Redirection Problem

Hi everyone,


I am using Oracle E-business suite 12 and currently I am trying to do the load balancing over my two servers using the F5 LTM . I am using https offloading for the Oracle setup on LTM units. Now a user tries to access the oracle application using http and it redirects the user initially to https and then there is a automatic redirection which gives the user browser direct communication between the Oracle server and the user browser as i can see the Https turning to http and there is no counter movement for any further traffice on LTM. I tried looking for everything but I can't figure out what is the problem is there anything I have to do on the Oracle servers as well??? Any help in this matter will be highly appreciated. If any one has faced such issue and knows the solution please help me out.





3 Replies

  • do you have any http analyzer tool such as httpfox to see whether it is redirected by header or payload? i think it might be embedded in payload. if nothing can be done on server-side, you may have to use stream profile/irule to modify it.




  • Hi Nitass,


    The server as a single platform has nothing to do with redirection as soon as the LTM hits the pool member it tries to redirect the traffic. Why this is happening... I will try to use this tool to find out thanks...



  • Verify your configuration.



    Unless you need to protect the traffic going from your F5 to your oracle boxes you should set the oracle boxes to serve http.



    Then in your F5 you setup the port for https (TCP443 if you use default) which the F5 will do its ssl magic for. So the flow client <-> F5 is HTTPS (SSL) over TCP443 (or whatever port you choosed) and then the F5 will use HTTP for the flow F5 <-> Oracleboxes.



    For this to you work I think you need to enable snatpool or snat automap. I also think you can in the http profile of F5 setup if it should redirect client to https (so the F5 listens on both TCP80 and TCP443 but then redirects any clients accessing TCP80, but this is often not needed for internal networks).