Persistence using Http cookie insert

Hi Aaron, thanks for your response. I am a Network guy who specialises in routing and switching so please ignore my ignorance in regards HTTP 1.1. I will give you a little history to the issue. Initially the Virtual server was configured as a Performance HTTP to allow for cookie persistance, however it was found that the end server connection count with OneConnect enabled (as is by default on PerformanceHTTP) ramped up exponentally with each new connection and then got stuck in TCP Time_Wait. we reconfigured the profile as a Standard profile with HTTP and again with Cookie Persistance - this took away the issue with the large number of connections on the server and them not clearing down.

 

 

I have been told that the Application server (Apache) POSTing/Calling HTTP requests to the VIP is using HTTPClient with a pool of connections (connection manager) but maintains cookies and conversational state in the core HttpClient object. HTTPClient also uses 1.1 persistance which I believe also does not work with OneConnect (is this correct?). http://hc.apache.org/httpclient-legacy/performance.html

 

 

The user is now complaining that when this particular "pool" configuration is used on the HTTPClient the connections made from within the pool to the VIP does not maintain the cookie persistancy expected.

 

 

Due to the massive amounts of traffic targetting this VIP I'm finding it extremely difficult to find the individual instances.