I need to perform url rewriting to convert this (for example):
/blogs/feeds/popular/posts/
to this:
/blogs/feeds.aspx?type =popular&type2= posts
What I did was the following:
1. Created an http handler that parses the url and based on it will execute
another aspx page using Server.Execute
2. In the IIS I added ".*" to the ISAPI handler to be handled by .net
3. In web.config I added this so that it handles all urls coming in:
<httpHandlers >
<add verb="*" path="*/" type="MyHandler .FeedsHandler, FeedsHandler" />
</httpHandlers>
My question is: Is this a proper practice or are there any down sides to
using "server.execute " and "Setting the ISAPI handler to handle .* as .net
pages"?
Following is my handler code:
using System;
using System.Web;
using System.Configur ation;
namespace MyHandler
{
/// <summary>
/// Summary description for FeedsHandler.
/// </summary>
public class FeedsHandler : IHttpHandler
{
#region Implementation of IHttpHandler
public void ProcessRequest( System.Web.Http Context context)
{
HttpResponse objResponse = context.Respons e;
string myPath = context.Request .Path;
if (myPath.Contain s("/feeds/"))
{
string[] mySplitPath = myPath.Split('/');
string myType2 = mySplitPath[mySplitPath.Len gth - 2];
string myType = mySplitPath[mySplitPath.Len gth - 3];
HttpContext.Cur rent.Server.Exe cute("/feeds/feeds.aspx" +
"?type=" + myType + "&type2=" + myType2);
}
else
{
HttpContext.Cur rent.Server.Exe cute(myPath + "Default.aspx") ;
}
}
public bool IsReusable
{
get
{
return false;
}
}
#endregion
}
}
