Consider this scenario:
Customer goes to my force.com site. Ex: www.mysitename.com
Customer logs in to authenticated force.com site with custom URL. Domain.secure.force.com
Customer closes window/tab, goes anywhere else. Customer comes back to the public URL.
Here's the problem...to them, the site appears like they aren't logged in. If they do try to log in, they will get a visualforce error page because they're already logged in.
Ideal scenario...public page recognizes they're still the same user and shows them logged in.
Decent hack...we catch the "already logged in" error and do a redirect to the secure site without telling the user. OR, kill the previous session and start a new one...as long as the user isn't impacted.
How can I make the site do one of these "smarter" behaviors?