Cookie Persistence Issue with Default Setting in LTM V10

The default parent cookie profile uses the HTTP cookie insert method and session expiration. Disabling the checkboxes in the child profile doesn't disable these default settings. So assuming you used the default parent profile's insert method, can you confirm if "session cookie" was checked in the working version?

session cookie expiration was checked( enabled) in default Cookie persistence and the view format of the graphs were not coming.

Upon editing the custom profile( disabling Cookie Method, Cookie Name, Expiration, Override Connection Limit), by doing this the application graph came up

Thanks and Regards Parveez

You cannot disable the cookie method. One of the 4 options must be chosen. By disabled I assume you mean unchecking the check boxes on the far right. Those are simply edit controls. With these check boxes unchecked, the greyed out values are the values that are used for that profile. So then let's also assume that the greyed out cookie method still says "HTTP cookie insert", the cookie name is blank, the "Always send cookie" option is unchecked, and the "Override connection limit" option is also unchecked. If this is all true, is the greyed out "Session cookie" option checked, or is it unchecked?

Hi Kevin,

Sorry for the confusion, if you use default Cookie Persistence method,the default Cookie Method will be HTTP cookie insert with Expiration Session Cookie enabled, correct. In this case, the graph not coming.

While editing the customer profile we have:

Name TEST-COOKIE

Configuration: Custom( All options unchecked:so below options are greyed)

Cookie Method: Cookie Name: Expiration Override Connection Limit

All above unchecked including Session Cookie value.And the above setting worked, why ? Is that still taking the default values , and what will be the role here for Session Cookie expiration.

Thanks and Regards Parveez

The direction I've been going with this is to determine if you're using session-based cookies. It's a pretty common problem with APM when a browser initiates an external process and that process can't pass through the same authenticated policy. The most prominent reason for this is that the external process cannot use the session cookies that are in the browser's memory space. When you enable the session expiration option in the cookie persistence profile, you're telling LTM to set a session cookie, one that has no expiration and that will live in browser memory only. If you uncheck that value, and optionally enter date/time values below it, it'll create a file-based cookie, one that is probably accessible to the external process. If you look at client side captures, you'll most likely see that the Set-Cookie header coming from the LTM has an "expires" tag.