All Help Topics

• Install Instructions
• Latest Release Notes

This set of options will change an 'old' DNN friendly Url like this:
mysite.com/MyTestPage/tabId/65/MyParam/MyValue/default.aspx
to this:
mysite.com/My_Test_Page/MyParam/MyValue.aspx

This set of options is a good starting point for most websites.

Step 6: Change the entry for <friendlyUrl defaultProvider="DNNFriendlyUrl"> to <friendlyUrl defaultProvider="iFinity.FriendlyUrl">

Step 7: Try it out! Note that you may have to restart your application to get the Friendly Url provider working properly.  Also note you must have your 'Friendly Urls' option in the Host Settings page switched On.

Want More Features?

The Url Master module is the premium offering from ifinity.com.au.  Here's what you get:

• all the great features of the iFinity Friendly Url Provider
• Installs through the DNN Module Installer
• Gives you the ability to define any Url for a DNN page
• Allows you to create custom Urls for your DNN pages
• Gives you the tools to create custom redirects for DNN pages, so that you can redirect from any other Url to a chosen DNN page
• Can generate short, simple urls for the User Profile pages of your site, like http://domain.com/user_name instaed of domain.com/user-profile/user/3.aspx
• Provides an interactive interface for changing and updating settings

Download a free trial and try it out : http://www.ifinity.com.au/Products/Url_Master_DNN_SEO_Urls/

• urlFormat (HumanFriendly,omitted) - ''humanFriendly'' when using Url values without the standard tabid/nn path. If omitted, will use standard DNN-style friendly Urls
• doNotRewritePage - regex string for excluding incoming requests. If the incoming request matches the regex, no rewriting will be attempted. This is used to handle exceptions, such as direct calls to pages/controls in the DesktopModules path.
• checkForDupURls (true/false) - true means an exception will be logged if duplicate urls are found while building the tab dictionary. Duplicate url''s are urls where the combination of portalAlias/tabpath from two different portals match. Preference is always given to the ''first'' portal / tab path combo, so the second and suqsequent combos will never resolve properly.
• redirectUnfriendly (true/false) - whether to issue 301 redirect status codes if an incoming url does not match the friendly url for that page. Also redirects requests to the site root (mydomain.com/) to the home page of the site (mydomain.com/home.aspx - assuming 'home.aspx' is the home page name)
• doNotRedirect - semicolon delimited list of tab paths where a 301 redirect should never be issued. Use when a particular page should use ?key=val type parameters, or unwanted results are occuring. This is only used when redirectUnfriendly = true
• doNotRedirectRegex - a regex expression which, when evaluated against the incoming url, will not redirect if the result is a match. In the example, the /logoff.aspx page will never 301 redirect. This is only used when redirectUnfriendly = true
• triggerDictionaryRebuildRegex  - a regex expression which will clear out the page index and refresh it on the next request.  This allows tailoring of when the page index gets rebuilt.  By default it contains a regex expression which recognises the DNN 'new page' control so that new pages are included in the index after being added.  If this behaviour is not wanted for performance reasons, a blank expresssion "" should be included.  Apart from that, any valid regex expression will cause the behaviour.  Note that the Regex expression is applied to the rewritten Url, not the requested Url. (ie default.aspx?tabId=nn, not /pagename.aspx)  This setting can be omitted for the majority of installations.
• parameterHandling (ordered, firstlast) - ordered means key/value pairs are kept in order, and placed after the tab path. ie mypage/mykey1/myvalue1/mykey2/myvalue2. firstlast means take the key of the first parameter and place it last, at the end of the string. mypage/myvalue1/mykey2/myvalue2/mykey1. Default : firstlast
• pageExtensionUsage (never, pageonly or always) - three options on whether to use page extensions (ie .aspx) for the pages. never = don''t use page extensions, pageonly = only use page extensions when the page path does not include parameter key/value pairs (ie mysite/mypage.aspx but not mysite/mypage/mykey/myvalue), always = .aspx is appended to all urls. Default : alwaysUse. If using pageonly or never, the iis setup must have wildcard mapping to the aspnet_isapi.dll (instructions below)
• ignoreFileTypeRegex (Regex string) - when mapping wildcard requests to aspnet_isapi.dll, the asp.net url rewriting function will be called for all types of iis resources on the page. This means unnecessary file handling for jpeg, gif, css,axd and other file types. By entering a regex string, any match found will bypass the url rewriting code and be passed back to iis.
• pageExtension - allows the use of a page extension other than .aspx if required. (ie .page, .content - whatever)
• forceLowerCase (true, false or omitted) - if set to true, all generated Url's will be set to lower case.
• forceLowerCaseRegex - this regex pattern (omitted by default) will prevent the forceLowerCase option from being used for any Urls that match the regex pattern.  This should be used in cases where there is a case-sensitive parameter in the querystring.  Usually this is when a module case a base64 encoded value which is case sensitive for the decryption.
• redirectWrongCase (true, false or omitted) - if set to true, all requests sent to the page with the incorrect case will be 301 redirected to the correct case of the Url.
• replaceSpaceWith (any valid character, omitted) - if a valid character is supplied, any spaces in the page name will be replaced with this character for generated Urls.   If omitted, the standard DNN behaviour (spaces removed from page name) is used.  When 'replaceSpaceWith' is used, any requests for the non-spaces version of that request (ie for mypage instead of my_page) will be 301 redirected, unless there is another page called the same name (ie a valid mypage exists as well as my page)
• spaceEncodingValue (any valid characters, omitted) - by default, any spaces in the url path will be encoded with a '+'.  However, IIS7 by default does not allow for '+' in the path.  If this is the case, then use %20 as a space encoding value.  Note that this is separate from the replaceSpaceWith value, which only works on the DNN page names.  The space encoding value applies to other parts of the querystring that get incorporated into the url - generally this is third party module options where a space is included in the path.
• useBaseFriendlyUrls (list of ; delimited tab paths, with a single / for separating path levels) - if a page path is included in this list, it will not have a 'humanFriendly' url generated for it.  This list is an exclusion list, and any page that is listed will have the 'standard' DNN friendly Url generated.  This option is normally used when a particular module on a page uses proprietary query string handling, and is inoperable against the Friendly Url Provider.  You can exclude this page and maintain standard operations, while using human friendly Urls for the rest of the site. Note: to get the page paths, look at the dnn_Tabs.TabPath table.
• triggerDictionaryRebuildRegex(Regex String) - when supplied, any Rewritten Url that matches this regex will result in the Page index for the DNN installation being rebuilt. The Page index is cached between requests for performance, but any new page or page change that is performed on the site will need the page index to be rebuilt. It is not required for most installations, and if a new value is added, it should also include the following regex (for page add/edit, portal add/edit) - the recommended value is triggerDictionaryRebuildRegex="&amp;ctl=tab|/ctl/tab|/Admin/Tabs/"
• allowDebugCode (true, false, or omitted) - allows debug response headers to be output when a request param or query string param of _fpdebug=true is added to the request.  This is used for debugging in html trace programs like Microsoft Fiddler.
• redirectDefaultPath (true, false or omitted) - redirects the /default.aspx url to the site root.  Can only be used when running with no page extensions, otherwise puts the site root requests into a terminal loop due to IIS.
• forwardExternalUrls (Redirect301, Redirect302, NoRedirect) - each value determins what to do when a page is requested in a url, and that page has an external Url specified.  The redirect values forward the visitor to the external page.
• deletedTabHandling  (301RedirectToHome, Output404) - specifies what to do when a page which is deleted (but not removed from the recycle bin) is requested.
• rebaseClientPath (true, false, omitted (true)) - the value passed to the context.Rewrite(url, rebaseClientPath) call that the underlying asp.net rewriting uses.
• usePortalAlias="0,www.domain.com;1,www.anothername.com"  - a delimited list of portalid/ portal alias pairs.  This list specifies which of the portal aliases a particular portal shoudl use.  Any request to an alias for that portal which isn't the specified one will result in a 301 redirect to the specified alias.  Use to push non-www to www requests, and to migrate domain names for sites.
• sslClientRedirect (true, false, omitted (true)) - if true, uses a javascript redirect to send a visitor to the http version of a https request, if the site settings say to do so.  If false, uses a server-based 301 redirect.  Use true to avoid a browser warning.
• cachePersistRestart (true, false) - if true, the page index cache will be preserved throughout an app restart.  If false, it will be rebuilt on app restart.
• logCacheMessages (true, false, omitted (true)) - if true, a message will be inserted into the site log every time the page index is rebuilt.  Recommended to use 'false' unless debugging.
• cacheTime="1000" - any positive integer, specifying the number of minutes the page index is requested to be cached for.  Note that if the web server has insufficient resources to maintain this cache, the page index will be flushed earlier.
• doNotRedirectSecureRegex - regex match pattern.  When a match is found, the standard SSL redirect code will be ignored, and the request will be completed on the http:// scheme.  This is often used for allowing search engines to index a page without having the page forward to https://.

• * - Requires modification of the IIS settings to remove page extensions, this option may not be possible on shared hosts.  Check with your website host.
• ** - Requires modification of the IIS settings to set a custom page extension, this option may not be possible on shared hosts.  Check with your website host.