|
Hi,
I just downloaded the source code for the URL Rewriter. I've hacked the source a bit to make it possible that when a user enters an URL like http://www.prietveld.com/thailand.aspx and the page "thailand.aspx" doesn’t exist the URL rewriter redirects the user to a search page presenting him a search result based on Thailand. This is handy when a page has moved or changed and the user hits the page via Google. (use the link above to see demo). For me it's importent that the user never sees a page not found message. The above example is one part of the solution. the other part is to make sure that a 404 page redirects to the search page, for this I don't have a nice solution yet, because it seems that IIS can only redirect a 404 error to a HTML page. If this is the case then I would have to write JavaScript to redirect the user to the search page, but then I'm not sure if I can retrieve the original URL request. I would like to know if anyone has done something like this and maybe has a better cleaner solution. I don't like the fact that I have altered the core.
I'm a senior software developer/architect with a small company in the Netherlands specialized in e-commerce. We use DotNetNuke as our platform for building the presentation layer for our solutions. |