K
kennedystephen
I have a web app that allows a user to upload/submit a file. After
upload completes, the user is taken back to the same page
(upload.aspx) in order to upload another file. At that point, if the
user leaves the web application and goes to another web page, and then
hits the browser's back button expecting to return to the upload page,
they get "Webpage has expired" message back from IIS.
I'd like to be able to programmatically handle this error. Meaning, if
the page is expired, I'd like for it to just response.redirect back to
the original upload.aspx.
Alternatively, is it possible to create a custom HTTP error page in
IIS for the "Webpage has expired" page. If so, what filename/number is
it in IIS? I'll replace it with a custom page that response.redirects
back to upload.aspx.
Any help would be appreciated, as this thing is kicking me .... hard.
Thanks,
- Steve
upload completes, the user is taken back to the same page
(upload.aspx) in order to upload another file. At that point, if the
user leaves the web application and goes to another web page, and then
hits the browser's back button expecting to return to the upload page,
they get "Webpage has expired" message back from IIS.
I'd like to be able to programmatically handle this error. Meaning, if
the page is expired, I'd like for it to just response.redirect back to
the original upload.aspx.
Alternatively, is it possible to create a custom HTTP error page in
IIS for the "Webpage has expired" page. If so, what filename/number is
it in IIS? I'll replace it with a custom page that response.redirects
back to upload.aspx.
Any help would be appreciated, as this thing is kicking me .... hard.
Thanks,
- Steve