Fresh install of DNN 7.1.2, on Win 2008 R2, IIS 7.5, SQL Server 2012, using the core url features, eg  <add name="DNNFriendlyUrl" type="DotNetNuke.Services.Url.FriendlyUrl.DNNFriendlyUrlProvider, DotNetNuke.HttpModules" includePageName="true" regexMatch="a-zA-Z0-9 _-" urlFormat="advanced"/> 

When urlFormat is set to advanced, the base url includes a language parameter (show language is unchecked in Admin > Languages, and only the en-US language is enabled) eg http://[redacted]:80/Default.aspx?TabId=102&language=en-US and page is generated in ~0.9 seconds

HOWEVER

When urlFormat is set to humanfriendly, the base url drops any language parameter eg http://[redacted]:80/Default.aspx?TabId=102 and page is generated in ~0.2 seconds - a huge performance improvement. 

The site did have other languages enabled, and is intended to be multi-lingual in the future, so removing the possibility for multi-lingual setup isn't desirable, but why is this happening? 

Hello,

I tried to look up some documentation about the DNN Friendly URL configuration, but found nothing. Maybe I did not search thoroughly enough... Please point me to a page where I can find info about "advanced" DNNFriendlyUrl configuration.

For example I have no idea what the "regexMatch" property is good for. I have a situation where the "advanced" url rewriter screws up my querystring by changing all "special characters" (question mark, equal sign and ampersand: ?=&) to slash signs (/). Including these characters in the "regexMatch" regular expression did not seem to help, but I guess that this is the place where ADVANCED mode can/should be configurable.

Thanks,
Zoldbogar

Thanks Leopold, in fact I was looking for fixing the QueryString rewrite and this page contains info that might have helped: http://www.dnnsoftware.com/wiki/page/...

I say, that it might have helped, because a colleague of mine came over another module (I think called OpenURL) which does the job just fine.

Have a good one,
Zoldbogar