D
doug
I support several intranet sites one of which had NO STATE. Even though
content has ASP extensions, it was all rendered HTML. Site had NO session or
application variables being managed. Site had no global.asa. IIS Manager
had site timeout set to 20 minutes.
We had to add an ASP include to pages, and that ASP include contained our
first session variable. Users then started complaining of timeouts and being
redirected to logout pages because session variable evaporated. Users
requested a 4 hour - 240 minute timeout. This was set in IIS Manager on
site, and it didn't work. We added global.asa with timeout set in session
on_start routine, and even though we could display the timeout variable at
240 minutes, if we wait 30 minutes and pressed refresh on page displayed, it
took logic path indicating session variable no longer set.
Anyone know why we are experiencing this behavior?
content has ASP extensions, it was all rendered HTML. Site had NO session or
application variables being managed. Site had no global.asa. IIS Manager
had site timeout set to 20 minutes.
We had to add an ASP include to pages, and that ASP include contained our
first session variable. Users then started complaining of timeouts and being
redirected to logout pages because session variable evaporated. Users
requested a 4 hour - 240 minute timeout. This was set in IIS Manager on
site, and it didn't work. We added global.asa with timeout set in session
on_start routine, and even though we could display the timeout variable at
240 minutes, if we wait 30 minutes and pressed refresh on page displayed, it
took logic path indicating session variable no longer set.
Anyone know why we are experiencing this behavior?