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

chip_78360's avatar
chip_78360
Icon for Nimbostratus rankNimbostratus
Jan 14, 2010

BigIP and ASP.NET_SessionID issues.

We are moving our current application off of Cisco LB to a an F5 device. It is a .NET app which uses stateful sessions so we need to use the ASP.NET_SessionID to get back to the appropriate server. ...
application delivery
dev
devops
iRules
hoolio's avatar
hoolio
Icon for Cirrostratus rankCirrostratus
Jan 14, 2010
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