Forum Discussion
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
header is included in a HTTP redirect response which specifies theConnection: Close
header (use Chrome or FF DevTools)Location: https://the.sameapp.com/new-path
Yes, a new TCP connection, however your persistence (session sticky is the name used by Cisco ACE and others Cisco stuff) is based in layer 7 information. If the request made to follow the redirect uses the same sessionid, that new connection will persist to the same server (so no new load balance decision).