U
UT-BadBoy
I've just recently encountered a problem and don't understand the cause
of the behaviour and would like some input on why ASP.NET or the IIS is
causing this problem.
My project entails me to dynamically generate a new aspx page when a
new account is setup. This page is basically a new homepage for the
user, which is created within it's own directory. The problem that I
am encountering is that the session seems to time out whenever any
changes are made to the homepage. Example, when the user wants to
change the name of the homepage ( this modifies the homepage url ),
upon saving, the session comes back indicating that it has timed out.
Is this the general behavior or do I need to do something additional so
that IIS doesn't try to recycle the current session?
Thanks in Advance.
Kevin
of the behaviour and would like some input on why ASP.NET or the IIS is
causing this problem.
My project entails me to dynamically generate a new aspx page when a
new account is setup. This page is basically a new homepage for the
user, which is created within it's own directory. The problem that I
am encountering is that the session seems to time out whenever any
changes are made to the homepage. Example, when the user wants to
change the name of the homepage ( this modifies the homepage url ),
upon saving, the session comes back indicating that it has timed out.
Is this the general behavior or do I need to do something additional so
that IIS doesn't try to recycle the current session?
Thanks in Advance.
Kevin