BigIP and ASP.NET_SessionID issues.

Hi Chip,

 

 

I don't think standard HTTP clients use pipelining on the first request to a site. How would the client know what the second HTTP request on the same TCP connection should be if they haven't received the response content from the first request? They could use keep-alives and make multiple HTTP requests on the same TCP connection. But in that case, they would have to wait for the first response (which has the Set-Cookie with the ASP session ID) and then send that cookie in the subsequent requests.

 

 

As a guess, you might try enabling a custom OneConnect profile. If you're using SNAT on the connection to the pool members, you can set the OneConnect source mask to 0.0.0.0. If you're not doing source address translation on the connection to the pool members, you can set the source mask to 255.255.255.255. See this wiki page for details on why you need to use OneConnect with cookie-based load balancing:

 

 

http://devcentral.f5.com/wiki/default.aspx/AdvDesignConfig/oneconnect

 

 

If that doesn't work, it would help to reproduce the loadrunner issue with HTTP 1.1 and capture a tcpdump to see exactly what is happening.

 

 

Aaron