CF Registry Disabled - Applicaiton Problem Fix

[hatton]

According to Yash, the CFRegistry tag was recently disabled. On CFMX this affects the CFApplication tag *if* client storage is left to it's default or set to "Registry".

At default, the CFApplicaiton tag has a parameter of clientstorage with a default value of Registry. By disabling the CFRegisty tag, this creates a conflit. To resolve the problem, the CFApplicaiton tag MUST include the clientstorage="Cookie" or clientstorage="Datasource_Name" to ensure that CFMX does not try to access the registry.

Here is an example of a good CFApplication tag.

<cfapplication name="Your_App_Name"
clientmanagement="yes"
sessionmanagement="yes"
setclientcookies="yes"
setdomaincookies="yes"
sessiontimeout="#createTimeSpan(0,8,0,0)#"
applicationtimeout="#createTimeSpan(0,8,0,0)#"
Clientstorage="Cookie"
loginstorage="session">

 

[Harrison]

Hatton if the clientstorage for a user key is cookie where on the server is the cookie stored?

 

[hatton]

Hatton if the clientstorage for a user key is cookie where on the server is the cookie stored?

The variables are housed in the session memory for the duration of the visit and referenced by the cookies that are stored on the client's browser.

http://en.wikipedia.org/wiki/HTTP_cookie

Hatton

 

[Harrison]

Ive went ahead and did some reading on <cflogin> sounds like it might make more sense for me. Thanks

atomi