Forum Discussion

Ski_Kacoroski_2's avatar
Ski_Kacoroski_2
Icon for Nimbostratus rankNimbostratus
Apr 04, 2017

Redirect and forward for LTM policies v12.2

My app has this logon URL (http://kronosF5.nsd.org/wfc/applications/wtk/html/ess/logon.jsp. I have a redirect set up as a irule and also as a LTM policy, but what I really want is to forward all the traffic from the F5 so the entire connection is secure. How would I do this with LTM policies in v12.2? I have looked at using the Replace option in the LTM policy to perhaps replace http://timecard1.nsd.org/ with http://kronosf5.nsd.org/, but cannot get this to work.

 

application delivery
LTM

3 Replies

Sort By
  • Ski_Kacoroski_2's avatar
    Ski_Kacoroski_2
    Icon for Nimbostratus rankNimbostratus
    Apr 05, 2017

    Yes, the kronos URL is insecure and they have no plans to fix it for at least a year. So the URL is http://kronosf5.nsd.org/wfc/applications/wtk/html/ess/logon.jsp. What I would like is for the F5 to sit in front of the Kronos system and offload the SSL stuff so instead of a redirect which I am doing now, I want a forward (or something). The problem with a forward is I cannot figure out how in a policy to do a forward and rewrite '/' to '/wfc/applications/wtk/html/ess/logon.jsp' for the initial logon and then have all other URLs just get passed through the F5 with the F5 dealing with the SSL part between the client machine and itself. Hope this helps to clarify the problem. Thanks for responding.

     

  • Andreas_Dahlber's avatar
    Andreas_Dahlber
    Icon for Nimbostratus rankNimbostratus
    Aug 16, 2019

    Did you solve this problem?

    For your forwarding, it should be possible with an irule;

    when HTTP_REQUEST {
if { [HTTP::uri] equals "/" or [HTTP::uri] equals "" }{
     HTTP::redirect https://[HTTP::host]/<new URI>/
     }
}

    I am into configuring our F5 to do SSL offload to a Kronos application server. We have the problem that Kronos replies http:// links back to the client, which should be https..

    Problem is that i think the links are embedded in the application, and not a HTTP Location header that we could rewrite.

    Thought of asking if you also dumped into this issue?