Hi Dave

Sorry about the delay in answering this one, the Url work has been monopolising my time of late.

The answer is : it's a 'feature' introduced into DNN 4.8.1.  Here is the offending piece of code in the standard DNN Url Rewriting Http Module:

'exit if a request for a .net mapping that isn't a content page is made i.e. axd
If Request.Url.LocalPath.ToLower.EndsWith(".aspx") = False _
   AndAlso Request.Url.LocalPath.ToLower.EndsWith(".asmx") = False _
   AndAlso Request.Url.LocalPath.ToLower.EndsWith(".ashx") = False Then
   Exit Sub
End If

You don't need to be much of a programmer to see what is going on here. From 4.8.1, anything but a .aspx/.asmx/.ashx extension is going to meet with problems when processing, because such requests get an early exit from the Url Rewriting code. That's OK for the most part, because a .axd handler doesn't need to get a /tabId/55/ rewritten to ?tabid=55, but the Url rewriter does more than that - it determines which portal alias the request was made under, and loads up the current portal settings, so that the rest of the request 'knows' which portal it is operating under.

The Google site map handler uses this information as well, so the problem you are seeing is because the Url Rewriter yanked the rug from underneath the Google sitemap handler by not setting up PortalSettings in the current application context. This shows up well down the track in an obscure (localization) section.

The good news is, I have fixed it by incorporating the bit of code the Url Rewriter should be running into the Google Sitemap Handler, if it hasn't already been run

.

The new version is avaialable from the Free Downloads page. The assemblies shoudl be stamped 1.2.2.