DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14716>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14716 Add a method putToken() to Action class [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2002-11-20 22:48 ------- Let me explain it more clearly. If you want to prevent a form from double submit, you need to have a transaction token in session before forwarding to the jsp (which has <html:form transaction="true">). This is done by calling saveToken() in your action class before forwarding. Now the following situation. I have two pages like this. The user gets first page (got its token), input half way, and click a link which has url getSecondPageAction.do?. So the 2nd page is loaded through an action and saveToken() is again called. This changes token so when the user goes back to the first page with back button, the page is treated as doing a double submit even if it has never been submitted. This is rare but in our app user is allowed to do that. With a new method putToken() (or has a flag in saveToken()), the 2nd page will not save a new token but using the existing one. So user can still proceed with submitting the 1st page. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
