Not sure if this is the best way, but I made a custom 404 like this:

            string query = Request.Url.Query;
            string path = query.Substring(query.IndexOf(":80") + 3);
            XPathNodeIterator iter = umbraco.library.GetXmlNodeByXPath(String.Format("//node[data[@alias='umbracoUrlAlias']='{0}']", path));
            // Iterate through the results. 
            while (iter.MoveNext())
            {
                XPathNavigator navCurrent = iter.Current;
                string strId = navCurrent.GetAttribute("id", "");
                if (strId != null)
                {
                    int id;
                    if (Int32.TryParse(strId, out id))
                    {
                        Response.StatusCode = 301;
                        Response.Status = "301 Moved Permanently";
                        Response.AddHeader("Location", umbraco.library.NiceUrl(id));
                        break;
                    }
                }
            }

1. The user tries to find "/somepage.php"
2. The page doesn't exists so you get this 404
3. The 404 searches the site for pages with the property "umbracoUrlAlias" for the content "/somepage.php" and redirects to that page with a 301

So all you then need is to fill in the old relate path/Url in the new pages umbracoUrlAlias-property.

Regards,
Magnus

Thanks Magnus, it looks good. Where do I need to put this piece of code to make it work? Also will this work for pages on an old domain name?

Not sure this is a lot of use but recently we coded up a HTTP module which compared the request URL to a dictionary of 301's (held in DB and cached on app start), if the request url matched we sent down a 301 and ended the processing for that request.

Nothing to do with Umbraco it was a pure .NET thing, but it sure helped the client deal with the migration from an old .html website.

Chris.

I don't have the full code available right now (I'll try and post it for you tomorrow) but it should work regardless of the domain, but as the code works now it wouldn't redirect from one domain to another, just from yourdomain.com/oldfolder/oldpage.php to yourdomain.com/newumbracopage. It should be quite easy to modify the code to switch/replace the old domain with the new domain.

Regards,
Magnus

The 301 URL Tracker only supports redirects for the domains bound to the website in IIS.

Right ok. When we go live we will be binding the old domains to the new website in IIS so that shouldnt be a problem. So if my old page was www.someolddomain.com/somepage.php and I'd like it to redirect to a new page I have created in Umbraco on our new site and domain, what value should I put in the custom mapping field for that Node? Should it just be /somepage.php without the www.someolddomain.com?

Yes, it should only be 'somepage.php' or '/somepage.php' (leading slash gets added automatically).
And if it's a multi-website umbraco installation, the 301 URL Tracker will 'listen' to the domains set on the root nodes ("Manage hostnames")

One last very important thing, you'll have to find a way to map '*.php' url's to the .NET handler (ISAPI). I haven't done that before and can't find a blog- or forumpost which describes how to do this...

The 301 URL Tracker would probably work for "*.php" if you have a wildcard mapping to the .NET handler then? I always use the wildcard mapping since I want directory URLs instead of ".aspx" in Umbraco.

As for my code, I made a custom 404-page (IIS setting) and put that code to run in Page_Init().

Regards,
Magnus

I don't know, I tried a bit yesterday. I had a mapping for *.php to .NET, which was working. But the request still doesn't hit umbraco, I don't know why...

Doug Mackay had a great suggestion in another topic, will work with .asp too I think:

I've been investigating the issue of getting it to work with .php/.cfm pages :-

I belive that the umbraco 404 handlers only work with .aspx or extensionless url's (this is hard coded into the umbraco requestModule).

As a workaround you can set-up the UrlRewritter to rewrite .php requests to a .aspx page that does't exist :-

<add name="phprewrite"
     virtualUrl="^~/(.*).php"
     rewriteUrlParameter="ExcludeFromClientQueryString"                 
     destinationUrl="~/php/$1.aspx"
     ignoreCase="true" />

This then enables you to use the custom mapping in the 301 URL Tracker

e.g.

Custom mappings :-

/php/oldpage.aspx

/php/olddir/oldpage.aspx

So /oldpage.php or /olddir/oldpage.php will get 301 redirected to the umbraco page that you've set the custom mapping on.

is working on a reply...