Cookie persistence with source IP as fallback
Hi, I have an LB with cookie persistence as persistence profile for a HTTPS re-encrypted LB.
When viewing some specific PDFs, we have an iRule that disables HTTP for a specific path, because due to a bug in the app, there is a mismatch in content length compared to what tht eapp says it sends, and what it sends, which violates the http standard, and the LB drops the data. As mentioned, this is solved by disabling HTTP for a specific path with an iRule. The problem is then that the LB fails to stick sessions based on cookies, and connection is lost for clients upon refresh, because they are loadbalanced to next hop.
My thought is that I could enable Source IP as a fallback method, however my concern is that since all connections are coming from the same source IP, ALL connections will be sent to the same server as soon as the fallback method kicks in. Even when not accessing the documents, because it has already been triggered.
We can not use SSL session ID persistence either, due to TLS 1.3 not supporting it. Any suggestions?