I have a new DNN install using 4.9 and the latest Friendly URL Provider and Engage Publish installed. These are my Friendly URL Provider settings in the web.config:
<add name="DNNFriendlyUrl" type="iFinity.DNN.Modules.FriendlyUrl.DNNFriendlyUrlProvider, iFinity.FriendlyUrlProvider" includePageName="true" regexMatch="[^\+a-zA-Z0-9 _-]"
urlFormat="HumanFriendly"
redirectUnfriendly="true"
doNotRewriteRegex="(\.axd)|(/DesktopModules/)"
doNotRedirect="SearchResults;"
doNotRedirectRegex="[.]*(/logoff.aspx)"
pageExtensionUsage="always"
pageExtension=".aspx"
parameterHandling="ordered"
ignoreFileTypesRegex="(\.gif)|(\.css)|(\.js)|(\.jpg)|(\.html)|(\.htm)"
checkForDupUrls="true"
forceLowerCase="true"
redirectWrongCase="true"
redirectToSubDomain=""
replaceSpaceWith="-"
/>
In testing the friendly URLs I have come across the following:
If redirectToSubDomain is an Empty String, when you come into the home page through www.xxxx-dev.org you get redirected to http://xxxx-dev.org. Click on any menu item and you get redirected appropriately (i.e.http://xxxx-dev.org/programming.aspx)
However if you enter as a url http://www.xxxx-dev.org/programming.aspx you get a 404 error. Take off the www. and you find the page.
Now for the flip side. If I have redirectToSubDomain = "www', I can get to the home page, but every other page comes up as a 404.
Any suggestions??? Something I missed? Is it because we have a "-" in the domain name? Right now I am telling the client that since we are early in development that its a bug on my list, but I need to be able to have URL's with the www in the front working.