Hi
I'm setting up an SSL certificate for a sub domain (something I've not done before).
For a standard domain (not sub), the CSR 'common name' would be www.domain.com. But for sub domains, I've read a lot of conflicting information suggesting to drop the 'www'.
Within the same research, the argument for keeping the 'www' is for cookie support. So my question here is, does anyone know if the ASP.NET authentication controls are affected if the user is accesses sub.domain.com, rather than www.sub.domain.com.
I've asked the SSL tech team, and they say drop the www - but I wanted to be sure ASP.NET login would not be affected.
Thanks as always
...
Go to the complete details ...