Are there standard techniques for preventing a user from using the back button
in the
browser and modifying and re-submitting a form? This issue has caused us serious
problems
in the past and we are wondering how other people handle this.
i'm not so sure we should be worried about the Back Button as much as how to
handle the situation if someone did try that by mistake.
i guess not caching the page could be one quasi-solution? but what other
techniques are used?
what about something in the session that indicates that the page has been
processed already??
we also have concerns about a user bringing up 2 different browsers at the same
time OR 2 browser windows and working on seperate parts of the app at the same
time.
our app is heavily workflow intensive and these issues have caused problems in
the past.
thanks,
frank
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
For JSP FAQ, http://www.esperanto.org.nz/jsp/jspfaq.html
