HTTP connection limit + cookie insert from BigIP

The log entry is just printing out the URI the client requested. That's not the URI that the client is being redirected to.

 

 

I'm not sure why it's happening, but it looks like LTM is setting the cookie, but the client doesn't always present it in subsequent requests. I'm assuming the cookie is being set with no path or other options that would tell the client to not send the cookie. If that's the case it looks like an issue with the client. I'm not sure there is a perfect iRule fix. You could account for this by raising the global limit.

 

 

Anyone else have ideas on why a client would get a cookie, make another request after the cookie was set, but not include the cookie in that subsequent request? This seems to violate the protocol for cookie handling.

 

 

Aaron