You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@beehive.apache.org by "Rich Feit (JIRA)" <be...@incubator.apache.org> on 2005/02/22 07:41:49 UTC

[jira] Resolved: (BEEHIVE-190) The prevent double submit feature does not work if the back button is not using the cached page

     [ http://issues.apache.org/jira/browse/BEEHIVE-190?page=history ]
     
Rich Feit resolved BEEHIVE-190:
-------------------------------

     Resolution: Fixed
    Fix Version: V1Beta

Addressed with revision 154801.

This is due to page-caching behavior in some browsers.  To mitigate this, I added the ability to configure action/page caching (i.e., the headers that are sent to the browser to configure caching).  The default behavior now is *not* to prevent caching on pages, which fixes this bug in your case.  If you *do* still want to prevent caching of pages, you can add either of the following snippets to netui-config.xml:

    <pageflow-config>
        <prevent-cache>always</prevent-cache>
    </pageflow-config>

        -or-

    <pageflow-config>
        <prevent-cache>inDevMode</prevent-cache>
    </pageflow-config>

The "always" value always prevents caching, and the "inDevMode" value prevents caching when the server is not in production mode.

I also added a 'disableOnClick' attribute to the Anchor, ImageAnchor, and Button tags.  When this is set to true, the button/link can't be clicked twice -- this eliminates the need for server-side checking in cases where JavaScript is enabled.

> The prevent double submit feature does not work if the back button is not using the cached page
> -----------------------------------------------------------------------------------------------
>
>          Key: BEEHIVE-190
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-190
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>     Reporter: John Rohrlich
>     Assignee: Rich Feit
>      Fix For: V1Beta

>
> The prevent double submit feature has browser and server specific behavior that is related to page reloading. If using the back button reloads the page a new token is generated and the PageFlowRequestProcessor does not detect the double submit.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira