Forum Discussion

RobL216_235020's avatar
RobL216_235020
Icon for Nimbostratus rankNimbostratus
Jun 14, 2018

HTTP iApp persistence

We have a HTTP iApp running for one of our systems that uses 2 nodes to connect to.

 

We have identified an issue where a user is connecting to the VS on the BIG-IP and opening a session on a node but then as they continue to work the session connectes to the other node. (We can see this in the application logs) This is causing an issue where the user continues to enter information but does not realise they are not updating the same record due to the second connection.

 

When we created the iApp using the template there is an option for persitance with the recommendation to be cookie persistance which we have chosen. However in the actual iApp it shows as having cookie AND source address persitance. Is this casuing my problem?

 

Not sure what else couldbe making this happen.

 

application delivery
BIG-IP
iApps
  • youssef1's avatar
    youssef1
    Icon for Cumulonimbus rankCumulonimbus
    Jun 14, 2018

    Hi,

     

    If you use cookie persistence you have to make sure that you have set an http profile in your VS.

     

    If your VS is SSL and you don't intercept traffic (ssl decryption) you can't use "cookie persistence" only source address. You need to intercpt traffic (ssl client) in order to set an cookie persistence.

     

    You can also set cookie persistence and fallback as source address...

     

    Can you confirm this point.

     

    regards,