Hi White Meat and thank you so much for taking time to respond, and so promptly. I am still not sure (forgive me, I am no expert!) how to use your code for my specific scenario.
The original domain (that the user will browse to) - say www.customer.com is hosted only with Classic .ASP - no .NET support.
The new domain (to which I am looking to forward) - say www.myserver.com/customer is hosted somehwere else and DOES have .NET support.
This is part of the reason why the redirection is in place.
I am assuming the above Class somehow needs to go on the original site that the browser first hits? If so, is it possible using Classic .ASP? If I need to add .NET hosting on this domain, I may aswell move across the whole content and do without the redirection. But this is really, really going to cause me a lot of problems (and cost :-)) as other components exist too.
Sorry if I am asking the earth! Perhaps it isn't possible?
Main Topics
Browse All Topics





by: WhiteMeatPosted on 2009-01-08 at 06:45:34ID: 23325346
I guess you can't simply point the IIS site to the sub-folder, otherwise you would have done that already...
e.com/Prog ramming/La nguages/.N ET/ ASP.NET /Q_2399983 6.html
nor can you move the relevant ".aspx" (or at least the home page) to the root directory?
Another way is to create a custom HttpHandler. I posted info on how to create a handler here:
http://www.experts-exchang
I customized it in an attempt to make it work with your scenario:
Select allOpen in new window