Why do you need to configure anything? Doesn't Request.Url give you all the information you need to determine the folder/path of the Request and appropriately redirect? (No, basic Forms Auth redirect won't work with this, but it's trivial to write yourself.)
∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Wed, Sep 30, 2009 at 5:29 AM, Gautam <[email protected]> wrote: > > > My application has 2 different modules separated in 2 different > folders, falling in same virtual folder The folder hierarchy is > something like this > > Parent folder. > - Child1 > - Child2 > > The url given to the virtual folder is something like this > https://abc.companyname.com. Once the user logs in he gets a drop down > selection box to login respective module. > > Now client came up with the requirement for creating separate URL > like > https://abc.companyname.com/child1 and > https://abc.companyname.com/child12 > > The navigation is fairly simple if I just punch the module name in the > url but the problem is with authentication. > My client wants absolute redirect to the default page of respective > folder. > > Im stuck with this issue wondering how to configure the absolute path > redirection by using the single authenticating page. > Note: I don’t want the login page to have any hard coding for > redirection. > > Guys Thanks in advance. > > > - Gautam >
