Double URL Issue

Jan 22, 2013 at 4:01 AM

Hi.  Here's my environment.  I'm running DNN 7.0.2 on IIS 7.5 (Windows 2008 R2) and SQL 2008 R2.  I also have iFinity URL Master 2.7.0 installed.  Additionally, I have the "SSL Enforced" option enabled and all of my public pages are set to use HTTPS.

My issue is that the SiteMap being generated has the non-encrypted portal alias appended to the front of the HTTPS URL, which gives a "Double URL" effect.

Here's an example.   The site is   Here are some of the URLs being generated within the sitemap:



Here are my settings from web.config:
    <searchEngineSitemap defaultProvider="BaseSitemapProvider">
        <add name="BaseSitemapProvider" type="DotNetNuke.Providers.SearchEngineSiteMapProvider.SiteMapProvider, DotNetNuke.Providers.SearchEngineSiteMapProvider" defaultPagePriority="0.5" defaultPageUpdateFrequency="daily" includeHiddenPages="false" />


I'm definitely scratching my head on this one.  Does anyone have any ideas?


See Ya!

Jan 22, 2013 at 4:20 AM

I uninstalled the module, and then the site gave the infamous "500 - Internal Server Error" error.  Luckily I had done a full site backup before installing the module, tonight.  To fix the error, I simply rolled back the original web.config.  I examined the faulty web.config and it looked like all of the entries created by the module installation process were still there.

I know that this common sense to everyone reading this post, but I want to reinforce the theme of making a complete site backup before installing any modules or before making any significant configuration changes.  Having a backup has saved my tuchus on more than one occasion.

See Ya!

Aug 28, 2013 at 5:25 PM
I am having this same issue. Does anyone know how to resolve it short of uninstalling the module? (I'd rather not, as to avoid the 500 error issue).
Aug 28, 2013 at 5:31 PM
Sorry, dsgreen30, but I've not come up with a solution yet. I have this same exact issue with another DNN 7 site that I setup since this post.

Bruce was going to take a look at the issue when he got some time, but it's a free module, and I'm sure that he has to take care of paying jobs first.

If you do end up with a solution, please post back.

See Ya!
Aug 29, 2013 at 8:15 PM
Tis a shame. I really want to use this instead of the normal DNN site map (stinks). Hopefully there will be some movement on it soon.

Sep 21, 2013 at 5:34 PM
OK, I narrowed it down further. As long as you reference the sitemap via http, you don't get the double-URL issue. If you reference the sitemap using HTTPS, this is when the double URL problem shows up.

For example, the following sitemap is fine:
While the following sitemap has the double-URL issue:
Dave, can you reference the sitemap via HTTP? If so, you can use it.

See Ya!

P.S. The built-in sitemap provider gives the same results via HTTP or HTTPS.

This sitemap is fine:
And this sitemap is fine:
Mar 27, 2014 at 5:03 PM
Something you should consider also is the primary portal Alias. In my case having more than one portal alias settled that was the issue. By changing the primary portal alias and refreshing the sitemap cache fixed the issue and the doubled domain within the Urls disappeared.

Jun 24, 2014 at 9:48 PM
I can only add that I have the same issue and it would be really great to have that resolved. I had the same issue with the previous old version from iFinity :-(