|
I have used e-banking sites that will log you out whenever you navigate back/forward from the webpage (affects all GET requests, not just POST). From a user experience point of view, it sucks (very inconvenient). I would like to know if this is a valid security measure, a feature or some paranoid thing that e-banking sites put in place to get the "secure" feeling. Q: Should e-banking sites disable back button? |
|||
|
|
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, see the FAQ for guidance.
|
The browser navigation featuress (back button etc) has always been one of the big challenges in designing "stateful" web-delivered applications, because it enables people to get to screens in unexpected ways, which can cause data-corruption issues if actions are taken on the screen. As a general rule, people learn that if you're doing anything transactional that involves multiple screens(shopping, registeriing a domain name, banking, booking ticket), you need to keep away from the back button. Whether disabling the back button or not is necessary depends on the overall application design, I guess. But it's certainly one option. |
|||
|
|
