in our application we have 5 pages form, after filled the form the user can read form page by page. Suppose if the user in them middle of the form, if he clicks on browser back button it supposed to go back but our page expiring due to security. please see the following message that I get
Warning: Page has Expired
The page you requested was created using information you submitted in a form. This page is no longer available. As a security precaution, Internet Explorer does not automatically resubmit your information for you.
To resubmit your information and view this Web page, click the Refresh button.
when we refresh the page it goes back page, but I need to avoid this problem. how can I do this
This sounds like a browser setting issue. Sounds like IE is deciding to get the latest version of the screen rather than going with the cached copy. If you can dictate browser settings to your user base then you can tell them to use a setting that won't cause them to get the latest version of the screen. Better would be if there is a setting that would supress that warning, maybe by lowering thier security level.
If you can't dictate browser settings you can provide a back button in the application that can take the user back to the previous page through a struts action. In addition you could also disable the browser controlls to prevent the use of the IE back button if thats exceptable to your client.
posted 10 years ago
I think your suggestion is good to make back button in struts allowing user to use back button rather than browser back.
I can do it creating the back button functionality but I dont know how to disable the browser back button. could you please give me the suggestion on this.
I wouldn't worry too much about the browser Back button. If the user's use it and it don't work, then they will learn not to use it and will not use it any more.
However, you might confuse the user if you are able to disable their Back button. Some might even get annoyed that this web page changed the functionality of their browser.
... best to leave the browser Back button alone and make sure you make your Back button on the page visible and neat. [ October 22, 2008: Message edited by: James Clark ]
posted 10 years ago
Its true that taking away browser functionality may iritate some of your users. It depends on your situation. In my case the the application I'm working on was converted from a client server application to a web application, so our users were already used to accessing it in a window without browser controls. It depends on your situations. Development wise I do find it a little annoying to not have a back button and to have to jump through hoops to view the html source for a screen. Howerver, its very nice to not have to worry about bugs caused by users using back/forward/book mark to jump random screens in the app.
If you think it might be the right solution for your scenario, take a look at the sFeatures parameter of window.open method here. It lets you control which browser functions are available to a user.