I'm having a problem with sessions persisting via cookies going from standard http to https SSL mode. The problem is that my website gets surfed with
http://www.mydomain.com. But then when going into SSL mode, my website becomes
https://secure.mydomain.com. Because of the change of subdomain, the session gets completely lost from that point on. Is there a way the .NET framework can handle wildcard subdomain cookies for sessions?? The only alternatives I see is to get a wildcard SSL certificate which is 10 times the price, or the ugly session ID in the URL. I'm hoping .NET cookie sessions can understand the concept of wildcard subdomains.
Start Free Trial