ColdFusion session management

ColdFusion session management is enabled by default. It utilizes CFID and CFToken as session identifiers. It sends them to the browser as persistent cookies with every request. If cookies are disabled, developers must pass these values in the URL. Session variables are automatically cleared when the session timeout is reached—but not when the browser closes.

Table 1: Default session scope variables:

Pros:

1. It is compatible with all versions of ColdFusion.
2. It uses same session identifiers as ColdFusion’s client management.
3. It is enabled by default.

Cons:

1. CFID and CFToken are created as persistent cookies.
2. You can only use one unnamed application per server instance.
3. Sessions persist when the browser closes.
4. ColdFusion session scope is not serializable.

Tags : CFID, CFToken, ColdFusion, ColdFusion session management, session identifiers, session management, session timeout, Session variables

If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.