Eelco Hillenius wrote: > > On Nov 18, 2007 2:55 AM, mfs <[EMAIL PROTECTED]> wrote: >> >> Yeah that scenario still makes sense where the user goes to the form page >> itself, but i was refering to the scenario where the user goes to the >> page >> (with the back button) which got shown after form submission, as in that >> case the browser would be submitting the request to the server >> (implicitly >> in case of a GET) and hence a double form submit OR the other scenario >> where >> user presses the refresh button on that previous page. > > That doesn't happen with redirect-after-post. > > Eelco >
I read the javadoc for IRequestCycleSettings -- I have a question about it: Lets say that we wanted to do "sophisticated clustering", so we use the ONE_PASS_RENDER option. However, we still want to avoid the double-submit problem. Is it possible? Is there a way the application can prevent it from happening in this case? Or is the only way to prevent the double-submit problem to use the REDIRECT_TO_RENDER or REDIRECT_TO_BUFFER options (and therefore require sticky load balancing)? -- View this message in context: http://www.nabble.com/double-form-submission-handling---tf4829048.html#a13851209 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
