Does anyone have any sample code on how to set up IIS to handle a friendly PURL? Also, a suggestion for hosts that support this would be great as well.
Ok, so IIS will provide a 404. The link provided looks like it is just replacing one URL with another.
So the easiest way would be to:
1. Trap the 404
2. Parse the friendly part of the URL
3. Redirect to an ASP file that does a database lookup on the PURL part of the URL and build the personalized web page
Ex. - test.com/swiler
Will return a 404 as page does not exist
Break of swiler
Redirect to asp page passing swiler as a querystring
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.