![]() Note: You can prevent ColdFusion from sending client information to the browser as cookies by setting tClientCookies variable in Application.cfc or the setClientCookies attribute of the cfapplication tag to No. ColdFusion creates a new session each time the user requests a page directly in the browser, because the new request contains no state information to indicate the session or client.You can then save user-specific information in a database with the user's ID as a key. To retain client information without cookies, require users to login with a unique ID. Therefore, do not use client variables, if you allow users to disable cookies. If you clear the Purge Data for Clients that Remain Unvisited option in the ColdFusion Administrator, ColdFusion never deletes this data. Any information about the user from a previous session is not available, but remains in client data storage until ColdFusion deletes it. Client variables are effectively the same as session variables, except that they leave unusable data in the client data store.īecause the client's system does not retain any identification information, the next time the user logs on, ColdFusion cannot identify the user with the previous client and must create a new client ID for the user.However, this technique has significant limitations, as follows: You can use client or session variables without using cookies, by passing the client identification information between application pages. ![]() In this case, ColdFusion cannot maintain the client state automatically. Often, users disable cookies in their browsers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |