For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Jacob_SLY_26625's avatar
Jacob_SLY_26625
Icon for Nimbostratus rankNimbostratus
Nov 30, 2016

Keep the existing connections to the same Tomcat server

we have session sticky configured based on a parameter of sessionid attached in http url in F5. we want to keep the existing connections to the same Tomcat server even when health check on it is fai...
application delivery
BIG-IP
Hannes_Rapp's avatar
Hannes_Rapp
Icon for Nimbostratus rankNimbostratus
Nov 30, 2016

I think the interesting part lies within: - "but when HTTP Redirect happens in the client , the F5 will treat it as new connection?"

Answer is no. Normally, a teardown of the existing TCP connection does not occur upon a HTTP redirect EXCEPT when the redirect response has a "Connection: Close" header. Assuming it's an App that uses modern version of HTTP (HTTP/1.1 or Speedy), then multiple HTTP redirects can occur on top of the same TCP session.

What to do?

  • Verify if the 
    Connection: Close
    header is included in a HTTP redirect response which specifies the 
    Location: https://the.sameapp.com/new-path
    header (use Chrome or FF DevTools)
Jacob_SLY_26625's avatar
Jacob_SLY_26625
Icon for Nimbostratus rankNimbostratus
Dec 01, 2016

Thanks for the answer; we did a tcpdump on the client, and found that when redirect happened, the TCP port used by the client changed, would it be identified by F5 as a new TCP connection?