Hi Please give more details what you try to avoid exactly by making changes in this area. [MH] Hello again, [MH] Well, I'm trying to avoid Double Submit through repeatedly button clicking (or submitting a form). We're currently [MH] porting all our web applications to Wicket. We have had to include a veil function around the Next button [MH] to block subsequent clicks explicitly as Wicket's Double Submit prevention (we are using the default RENDER_TO_BUFFER render strategy) [MH] is allowing repeated requests through. I've stepped through WebPageRenderer::respond() and noticed that there's a call [MH] to getAndRemoveBufferedResponse() and stopped looking since I could see that responses were being discarded. I just assumed that I am misunderstanding [MH] the full intent of the Double Submit treatment in Wicket. Hope that makes sense. I'm not wanting to *change* Wicket here, I'm chasing clarification only given what [MH] what I've stepped through and hear that from the maintainers directly. I guess I'm confused about what happens when there's more than one duplicate request when [MH] clearly the implementation is discarding (by design) the buffered response to an identical earlier request. [MH] [MH] Many thanks
> Hello, > > I just wanted to know what the impact of removing the buffered > response (referring to javadoc below for REDIRECT_TO_BUFFER) for a > request is if there's presumably a bunch of other duplicate requests > following it on solving the Double Submit problem. > ( > http://ci.apache.org/projects/wicket/apidocs/6.x/org/apache/wicket/set > tings/IRequestCycleSettings.html > ) > > I'm puzzled about throwing a response away when I would have thought > it's buffered and reused to service the (duplicate) requests following? > > Many thanks > > cheers. > -m. > > > ---------------------------------------------------------------------- > - This email, and any attachments, may be confidential and also > privileged. > If you are not the intended recipient, please notify the sender and > delete all copies of this transmission along with any attachments > immediately. You should not copy or use it for any purpose, nor > disclose its contents to any other person. > ---------------------------------------------------------------------- > - > ----------------------------------------------------------------------- This email, and any attachments, may be confidential and also privileged. If you are not the intended recipient, please notify the sender and delete all copies of this transmission along with any attachments immediately. You should not copy or use it for any purpose, nor disclose its contents to any other person. -----------------------------------------------------------------------
