G
Guest
Hi. I have an ASP.NET (in C#) application. Most of the application works the
way they usually do: an .aspx is requested and the code for that .aspx
processes the request, etc.
But undere one (and ONLY one) of my directories inside the application
(site), I need to parse the requesting Url BEFORE IIS (or is it ASP.NET)
attempts to open the requested resource. This is because the request resource
will actually NOT EXIST. Instead, a redirect will be performed OR the
response will just dynamically be generated.
EXAMPLE:
URL 1: http://site.com/NormalStuff/Default.aspx: This will be handled
completely normally and "Default.aspx must exist, etc.
URL 2: http://site.com/ParseIt/XYZ-PDQ.LMNOP: In this case, anything under
the "ParseIt" directory will be "intercepted" and the URL will be parsed by
my code to figure out what to do.
HOW DO I DO THIS IN ASP.NET? Is it something I have to insert in Global.asax?
Help?
Thanks.
Alex Maghen
way they usually do: an .aspx is requested and the code for that .aspx
processes the request, etc.
But undere one (and ONLY one) of my directories inside the application
(site), I need to parse the requesting Url BEFORE IIS (or is it ASP.NET)
attempts to open the requested resource. This is because the request resource
will actually NOT EXIST. Instead, a redirect will be performed OR the
response will just dynamically be generated.
EXAMPLE:
URL 1: http://site.com/NormalStuff/Default.aspx: This will be handled
completely normally and "Default.aspx must exist, etc.
URL 2: http://site.com/ParseIt/XYZ-PDQ.LMNOP: In this case, anything under
the "ParseIt" directory will be "intercepted" and the URL will be parsed by
my code to figure out what to do.
HOW DO I DO THIS IN ASP.NET? Is it something I have to insert in Global.asax?
Help?
Thanks.
Alex Maghen