My client is changing the shop part of their site from .asp files to .asp.net (.aspx) (it's a given, live with it or find another client is my status there) and I have some parts of the .cfm area of the site where I have to accept the login they do in the shop. (i.e. they pay for access in the shop, then can go to anywhere in the site, including my .cfm areas)
We don't want them to log in again just for the .cfm files, so I have to pass the login status back and forth between the .cfm and .aspx areas. Up till now, when they log in on the .asp area, the action page there passes them to a .cfm template where we create a cold fusion session, then pass them back to the .asp page they were originally looking for. Then when they eventually come to a .cfm page they're already logged in. With the change to .aspx, (and I don't know diddley about .aspx!) is there an easier and/or more reliable way to handle this login status? They're still going to be logging in at the new .aspx shop, and I still have to be able to tell when they come to my secured .cfm pages if they're logged in or not. But I do know that .aspx pages handle a number of things differently. Cheers, Michael Kear Windsor, NSW, Australia AFP Webworks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
