I noticed a few weeks ago that DotNetNuke links are taking out the "www" from within the URLs of our links. For example, when you type "www.portalname.com/subpage" it takes you to "portalname.com/subpage" instead. It appears to take out the "www" from embedded links within the HTML module, within the Links module, throughout the main menu, and from the login button. In other words, if effects every link within our DNN website.

We have created redirects in IIS to alleviate the problem throughout most of the website. However, we cannot create a redirect for the secure page, because we need to add the "https" in the redirect, which IIS does not allow you to do. This is causing a problem for our SSL certificate on our login page, because the certificate was issued WITH the "www" included in the common name and the login link takes you to a URL WITHOUT the www. So, for example, if the login page was suppose to be: https://www.portalname/securelogin/, DotNetNuke is taking you to: https://portalname/securelogin/.   Our server team will not allow us to purchase Wild Card certificates, or reissue the certificates without the "www" in the common name.

So, my question is, does anyone know why DNN would be taking out the "www" from our links within our website? If so, do you know how we can fix this within DNN?   Any help would be greatly appreciated!

You're saying that if you add a link in a Text/HTML module to www.dotnetnuke.com it changes the actual code so that when you look at the source it has removed the www?  Or is is just that a link to your site with the www redirects to the site without it?

Jeff

I'm saying just the links within our website are removing the "www"- not when you type it into the URL or access it from another site.

Changing the default alias in the database seems to have fixed the problem - for the most part. However, for some reason the Login/Logout link is still removing the "www".  Do you know how the login/logout function works and how we can change the link to refer to the defaul alias in the db?

The login/logout link appears to be taking out the "www" when the login page is secure AND when teh login page is NOT secure. So, it has  nothing to do with "https" redirects. It also appears to be occuring on a "per portal" basis.