I have somewhat older ASP application that is running on a client's web
server and is in the process of being written as .net. However, in the
meantime, due to the authentication interface that the client has in place we
were forced to create one ASP.net web page that interfaces to this
authentication program, and then redirects back to the older ASP application.
So the user logs in to the ASP.net app, gets authenticated and then we
response.redirect back to the existing ASP pages. This all takes place on the
same server. Every once in a while this login process "hangs" and no one can
login. A manual recycle of the AppPool clears things up, but my question
basically involves our approach to doing this. The .net authentication code
never really displays a page, but redirects to the old ASP pages. Are there
any "gotchas" with doing this? Should we be cleaning up the program
variables, etc.? Does a redirect automatically close out the .net program and
free resources, or is there something we should be doing to make sure
resources don't run out? Any thoughts would be appreciated.

Hello MarkR,

> I have somewhat older ASP application that is running on a client's
> web server and is in the process of being written as .net. However, in
> the meantime, due to the authentication interface that the client has
> in place we were forced to create one ASP.net web page that
> interfaces to this authentication program, and then redirects back to
> the older ASP application. So the user logs in to the ASP.net app,
> gets authenticated and then we response.redirect back to the existing
> ASP pages. This all takes place on the same server. Every once in a
> while this login process "hangs" and no one can login. A manual
> recycle of the AppPool clears things up, but my question basically
> involves our approach to doing this. The .net authentication code
> never really displays a page, but redirects to the old ASP pages. Are
> there any "gotchas" with doing this? Should we be cleaning up the
> program variables, etc.? Does a redirect automatically close out the
> .net program and free resources, or is there something we should be
> doing to make sure resources don't run out? Any thoughts would be
> appreciated.

If programmed well, there should be o problem on the ASP.net side. But it
sounds like you might have a problem with somethign as simple as a database
connection not closing properly or a connection to a webservice failing.

How is this Authentication system implemented is the question that probably
needs answering before we can help you further.

--
Jesse Houwing
jesse.houwing at sogeti.nl