No, from a cookie perspective, http://mysite.com and https://mysite.com are 2 different domains, so you need to send the session tokens across the gap. Any of a number of approaches can work, but here's the quick and dirty:
<cflocation url="https://#mySecureURL#"; addtoken="yes" /> Or, if you are using some other redirection, you can append the following to the URL: &cfid=#cookie.cfid#&cftoken=#cookie.cftoken# (Note that the nomenclature is different if you're using Java session IDs.) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:332508 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
