J
Jon Maz
Hi All,
I've been looking into options for URL Rewriting in .net, and to be honest,
I haven't seen anything that's easier than the old Classic Asp solution with
an ISAPI filter redirecting to an .asp page with responsibility for handling
the redirect.
I'm now planning to use this solution with my next .net project, and was
wondering if anyone else out there has done this already, and what problems
(if any) arise. Hopefully the news is that the solution works just as
easily as before.
I *am* aware that there is a dotnet alternative to an ISAPI filter. I found
a decent Scott Mitchell article
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/htm
l/urlrewriting.asp) on a URL Rewriting using Http modules, but I have some
reservations about using this method:
(a) it seems a lot more complex than the ISAPI solution.
(b) if you want to be able to handle URL's of the form
"www.apple.com/products", you still have to create a physical "products"
folder AND put an empty Default.aspx file in it, neither of which are true
of the ISAPI solution.
(c) depending how you implement the .net solution, Forms or Windows
Authentication may cease to work.
(d) to solve a postback issue you have to use an Actionless Server-side Form
instead of the standard .net one throughout your site.
So, does anyone have experience using an ISAPI Filter with .net, and was it
a good, bad or indifferent experience?
TIA,
JON
PS First posted to aspmessageboard:
http://www.aspmessageboard.com/forum/ASPPlus.asp?M=731069&T=731069&F=36&P=1
I've been looking into options for URL Rewriting in .net, and to be honest,
I haven't seen anything that's easier than the old Classic Asp solution with
an ISAPI filter redirecting to an .asp page with responsibility for handling
the redirect.
I'm now planning to use this solution with my next .net project, and was
wondering if anyone else out there has done this already, and what problems
(if any) arise. Hopefully the news is that the solution works just as
easily as before.
I *am* aware that there is a dotnet alternative to an ISAPI filter. I found
a decent Scott Mitchell article
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/htm
l/urlrewriting.asp) on a URL Rewriting using Http modules, but I have some
reservations about using this method:
(a) it seems a lot more complex than the ISAPI solution.
(b) if you want to be able to handle URL's of the form
"www.apple.com/products", you still have to create a physical "products"
folder AND put an empty Default.aspx file in it, neither of which are true
of the ISAPI solution.
(c) depending how you implement the .net solution, Forms or Windows
Authentication may cease to work.
(d) to solve a postback issue you have to use an Actionless Server-side Form
instead of the standard .net one throughout your site.
So, does anyone have experience using an ISAPI Filter with .net, and was it
a good, bad or indifferent experience?
TIA,
JON
PS First posted to aspmessageboard:
http://www.aspmessageboard.com/forum/ASPPlus.asp?M=731069&T=731069&F=36&P=1