C
Chuck
I have a forms authentication website that has a page where users spend a
lot
of time on. So somebody spends an hour on the page and then presses submit
and gets redirected to the logon page. Followed by a redirect back to where
they were minus all the data they typed in.
Is their a way to handle time outs without loosing data on the redirect.
Maybe popup a logon page versus a redirect or something.
I already have a httpmodule looking at the authenticate and endrequest
events. To fix problems associated with the basic forms authentication
design. So I don't mind coding low level stuff.
I can not violate security associated with ticket time outs by disabling the
timeout or doing javascript postbacks.
lot
of time on. So somebody spends an hour on the page and then presses submit
and gets redirected to the logon page. Followed by a redirect back to where
they were minus all the data they typed in.
Is their a way to handle time outs without loosing data on the redirect.
Maybe popup a logon page versus a redirect or something.
I already have a httpmodule looking at the authenticate and endrequest
events. To fix problems associated with the basic forms authentication
design. So I don't mind coding low level stuff.
I can not violate security associated with ticket time outs by disabling the
timeout or doing javascript postbacks.