Differences between Open Url Rewriter and DNN Core Advanced Url Rewriter
Open Url Rewriter
The url is cutted in 3 parts : portal (portal alias), page (page url), module (module url)
Each url part use a generic mapping table between query (tabid=123) parameters and url part (/mypage) for pages and modules
- less work to write a provider because de database layer is generic and out of the box
- the mapping table is automatic cached out of the box
- the mapping table is used to generate a sitemap for search engines out of the box
- the mapping table is used to manage enhanced 404 handling out of the box (optional)
- the mapping table is used to know all urls existing in the past and make a redirection for old urls with respecting of all urls from all pages and modules
Core Advanced Rewriter
Each provider have to create a mapping table and db table or generate it on the fly and manage his redirections and 404 status.
In addition to the url provider, a sitemap provider have be created for each module.
Additional differences of Open Url Rewriter :
- www.mysite.com is not redirected to www.mysite.com/en-us for multi language website
- Module rewrite can be done by patern
- Module rewrite can be done by SQL queries
- Many module providers are available
- Custom redirection rules
- Simple to implement module provider (1 method to implement)
- Adding a second language to your website, do not change the urls of the first existing language urls (needs special alias configuration).
Extended 404 management
Open Url Rewriter
Thanks to the generic url mapping table Open Url Rewriter knows all urls of the website.
This true for the urls generated by providers (pages, modules with a provider).
In the 404 enhanced mode all urls not present in the mapping table are not rewriter automatically (like dnn those by default).
This results in some urls exist with query parameters, for admin urls, this is not a problem, because search engine don’t see them.
For others you have the possibility, in google webmaster tools, to tell google witch query parameters, represent different content, and have to be indexed.
The result of this is that all non existing urls, generates a proper 404 (page not found) status code, which results in not generating duplicate content.
Core Url Rewriter
Non existing sub pages don't return 404 status
Each Url provider have to manage the 404 status for all his non existing urls.
Additional tools of the Open Url Rewriter
- W3C output filter : to make your website pass the W3C compatibility check
- Disable entire website indexing by search engines (adding robots noindex to all pages)
- http Status logging : to find all hyperlinks which results in 404 (page not found), 301, 302 (redirections)
More info about open url rewriter :