Privacy and Security / X3

X3.DnnUrlManagement.Portal

The 404 Error Page for your site. Users will be redirected to this page if the URL they are navigating to results in a 'Page Not Found' error.
404 Error Page
The 500 Error Page for your site. Users will be redirected to this page if the URL they are navigating to results in an unexpected error.
<None Specified>
Check this box if you want old 'non-friendly' URLs to be redirected to the new URLs.
Check this box to enable character replacement. This automatically replaces all spaces in page names.
Select the replacement character to use.
When the characters in this list appear in a page name, will be replaced with the value specified as the ‘replacement’ character (- or _). To replace any other character, append it to the end of the list. To stop any character from being replaced, remove it from the list.



[NOTE: The list shown in the ‘replace characters with supplied characters’ is actually the default for this one]
To replace a character in a URL with another character, use a comma delimited pair of characters where the first value in the pair is the ‘find’, and the second is the ‘replace’. f,r will find any ‘f’ in a URL and replace it with ‘r’. This can be used for replacing æ with ‘ae’ and similar. This only applies to Page and User Profile URLs and any URLs controlled through URL providers. You can only replace single characters - the 'find' character can only be a single value, while the 'replace' can be a string of one or more characters.
Check to hide the page extensions. This can be useful for SEO and also for masking the underlying technology to make it more difficult for hackers.
Specify the extension to use on the end of every page URL. The default value is .aspx. Note: using a custom page extension also requires configuring IIS to handle the custom extension. If you don't know what this means, leave it alone.
Select the behavior that should occur when a user browses to a deleted, expired or disabled page.

When checked, any URL generated by dNN will be converted to all lowercase. ie. Menus, breadcrumbs, module controls, etc.
When checked, any URL that is not in lower case will be redirected to the lower case version of that URL.
This character is used to replace any spaces in a generalized URL path where parameters with spaces have been supplied.
When checked, any accented (diacritic) characters such as å and è will be converted to their plain-ascii equivalent. Example : å -> a and è -> e.
When checked, the Custom URL Provider functionality of this site is enabled. When unchecked, no custom URL providers will be loaded.
When checked, any duplicate URLs found in this site will be reported in the event log. The system will choose which of the duplicate URLs to show.
The Ignore URL Regex pattern is used to stop processing of URLs by the URL Rewriting module. This should be used when the URL in question doesn’t need to be rewritten, redirected or otherwise processed through the URL Rewriter. Examples include images, css files, pdf files, service requests and requests for resources not associated with DotNetNuke.
The Do Not Rewrite URL regular expression stops URL Rewriting from occurring on any URL that matches. Use this value when a URL is being interpreted as a DotNetNuke page, but should not be.
The Site URLs Only regular expression pattern changes the processing order for matching URLs. When matched, the URLs are evaluated against any of the regular expressions in the siteURLs.config file, without first being checked against the list of friendly URLs for the site. Use this pattern to force processing through the siteURLs.config file for an explicit URL Rewrite or Redirect located within that file.
The Do Not Redirect URL regular expression pattern prevents matching URLs from being redirected in all cases. Use this pattern when a URL is being redirected incorrectly.
The Do Not Redirect https URL regular expression is used to stop unwanted redirects between http and https URLs. It prevents the redirect for any matching URLs, and works both for http->https and https->http redirects.
The Prevent Lowercase URL regular expression stops the automatic conversion to lower case for any matching URLs. Use this pattern to prevent the lowercase conversion of any URLs which need to remain in mixed/upper case. This is frequently used to stop the conversion of URLs where the contents of the URL contain an encoded character or case-sensitive value.
The Do Not Use Friendly URLs regular expression pattern is used to force certain DotNetNuke pages into using a longer URL for the page. This is normally used to generate behaviour for backwards compatibility.
The Keep in Querystring regular expression allows the matching of part of the friendly URL Path and ensuring that it stays in the querystring. When a DotNetNuke URL of /pagename/key/value is generated, a ‘Keep in Querystring Regular Expression’ pattern of /key/value will match that part of the path and leave it as part of the querystring for the generated URL; e.g. /pagename?key=value.
The URLs with no Extension regular expression pattern is used to validate URLs that do not refer to a resource on the server, are not DotNetNuke pages, but can be requested with no URL extension. URLs matching this regular expression will not be treated as a 404 when a matching DotNetNuke page can not be found for the URL.
This pattern is used to determine whether the characters that make up a page name or URL segment are valid for forming a friendly URL path. Characters that match the pattern will be removed from page names
Select a page from the list to edit the page URLs.
Select A Web Page
URLs that have been created for the selected page.
The default URL generated by DNN using all applied settings.

X3.DnnUrlManagement.Host

Check this box if you want old 'non-friendly' URLs to be redirected to the new URLs.
Check this box to enable character replacement. This automatically replaces all spaces in page names.
Select the replacement character to use.
When the characters in this list appear in a page name, will be replaced with the value specified as the ‘replacement’ character (- or _). To replace any other character, append it to the end of the list. To stop any character from being replaced, remove it from the list.



[NOTE: The list shown in the ‘replace characters with supplied characters’ is actually the default for this one]
To replace a character in a URL with another character, use a comma delimited pair of characters where the first value in the pair is the ‘find’, and the second is the ‘replace’. f,r will find any ‘f’ in a URL and replace it with ‘r’. This can be used for replacing æ with ‘ae’ and similar. This only applies to Page and User Profile URLs and any URLs controlled through URL providers. You can only replace single characters - the 'find' character can only be a single value, while the 'replace' can be a string of one or more characters.
Check to hide the page extensions. This can be useful for SEO and also for masking the underlying technology to make it more difficult for hackers.
Specify the extension to use on the end of every page URL. The default value is .aspx. Note: using a custom page extension also requires configuring IIS to handle the custom extension. If you don't know what this means, leave it alone.
Select the behavior that should occur when a user browses to a deleted, expired or disabled page.

When checked, any URL generated by dNN will be converted to all lowercase. ie. Menus, breadcrumbs, module controls, etc.
When checked, any URL that is not in lower case will be redirected to the lower case version of that URL.
This character is used to replace any spaces in a generalized URL path where parameters with spaces have been supplied.
When checked, any accented (diacritic) characters such as å and è will be converted to their plain-ascii equivalent. Example : å -> a and è -> e.
When checked, the Custom URL Provider functionality of this site is enabled. When unchecked, no custom URL providers will be loaded.
When checked, any duplicate URLs found in this site will be reported in the event log. The system will choose which of the duplicate URLs to show.
The Ignore URL Regex pattern is used to stop processing of URLs by the URL Rewriting module. This should be used when the URL in question doesn’t need to be rewritten, redirected or otherwise processed through the URL Rewriter. Examples include images, css files, pdf files, service requests and requests for resources not associated with DotNetNuke.
The Do Not Rewrite URL regular expression stops URL Rewriting from occurring on any URL that matches. Use this value when a URL is being interpreted as a DotNetNuke page, but should not be.
The Site URLs Only regular expression pattern changes the processing order for matching URLs. When matched, the URLs are evaluated against any of the regular expressions in the siteURLs.config file, without first being checked against the list of friendly URLs for the site. Use this pattern to force processing through the siteURLs.config file for an explicit URL Rewrite or Redirect located within that file.
The Do Not Redirect URL regular expression pattern prevents matching URLs from being redirected in all cases. Use this pattern when a URL is being redirected incorrectly.
The Do Not Redirect https URL regular expression is used to stop unwanted redirects between http and https URLs. It prevents the redirect for any matching URLs, and works both for http->https and https->http redirects.
The Prevent Lowercase URL regular expression stops the automatic conversion to lower case for any matching URLs. Use this pattern to prevent the lowercase conversion of any URLs which need to remain in mixed/upper case. This is frequently used to stop the conversion of URLs where the contents of the URL contain an encoded character or case-sensitive value.
The Do Not Use Friendly URLs regular expression pattern is used to force certain DotNetNuke pages into using a longer URL for the page. This is normally used to generate behaviour for backwards compatibility.
The Keep in Querystring regular expression allows the matching of part of the friendly URL Path and ensuring that it stays in the querystring. When a DotNetNuke URL of /pagename/key/value is generated, a ‘Keep in Querystring Regular Expression’ pattern of /key/value will match that part of the path and leave it as part of the querystring for the generated URL; e.g. /pagename?key=value.
The URLs with no Extension regular expression pattern is used to validate URLs that do not refer to a resource on the server, are not DotNetNuke pages, but can be requested with no URL extension. URLs matching this regular expression will not be treated as a 404 when a matching DotNetNuke page can not be found for the URL.
This pattern is used to determine whether the characters that make up a page name or URL segment are valid for forming a friendly URL path. Characters that match the pattern will be removed from page names