Search Engine friendly urls using IIS and ASP.NET

Apache has a look-back feature that lets it scan back down the URL if it
doesn't find what it is looking for.
For example: http://www.domain.com/article.php/999/12
In this above case there is no directory or file called 12, so it looks at
999. There is no directory or file called 999 so Apache looks down the URL
and sees article.php, which does exist, and calls up that script. Apache
also has a global variable called $PATH_INFO that is created on every HTTP
request. What this variable contains is the script being called and
everything to the right of that information in the URL. So in the example we
have been using $PATH_INFO will contain article.php/999/12.

How could we implement such behaviour in IIS and ASP.NET?
Could anybody provide some useful links to similar techniques?

Thanks

[Cowboy (Gregory A. Beamer) - MVP]

vbpj.com had a sidebar on Hierarchical URLs a few years ago which describes
how to take a friendly, mappable URL (human readable) and make it a URL that
conforms to model-view-controller. It is not 100% identical to what you are
looking for, but the basic theory will solve your issue.

---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

*************** ************
Think Outside the Box!
*************** ************

"ja***@docUSA.c om" wrote:

Apache has a look-back feature that lets it scan back down the URL if it
doesn't find what it is looking for.
For example: http://www.domain.com/article.php/999/12
In this above case there is no directory or file called 12, so it looks at
999. There is no directory or file called 999 so Apache looks down the URL
and sees article.php, which does exist, and calls up that script. Apache
also has a global variable called $PATH_INFO that is created on every HTTP
request. What this variable contains is the script being called and
everything to the right of that information in the URL. So in the example we
have been using $PATH_INFO will contain article.php/999/12.

How could we implement such behaviour in IIS and ASP.NET?
Could anybody provide some useful links to similar techniques?

Thanks

[Scott Allen]

You can do tricks like this with URL rewriting.

Scott has a good article here:
http://msdn.microsoft.com/library/de...lrewriting.asp

--
Scott
http://www.OdeToCode.com/blogs/scott/

Apache has a look-back feature that lets it scan back down the URL if
it
doesn't find what it is looking for.
For example: http://www.domain.com/article.php/999/12
In this above case there is no directory or file called 12, so it
looks at
999. There is no directory or file called 999 so Apache looks down the
URL
and sees article.php, which does exist, and calls up that script.
Apache
also has a global variable called $PATH_INFO that is created on every
HTTP
request. What this variable contains is the script being called and
everything to the right of that information in the URL. So in the
example we
have been using $PATH_INFO will contain article.php/999/12.
How could we implement such behaviour in IIS and ASP.NET? Could
anybody provide some useful links to similar techniques?

Thanks