struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Huber (Jira)" <j...@apache.org>
Subject [jira] [Commented] (WW-5026) Double-submit of TokenSessionStoreInterceptor broken since 2.5.16
Date Thu, 27 Aug 2020 08:58:00 GMT

    [ https://issues.apache.org/jira/browse/WW-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185730#comment-17185730
] 

Greg Huber commented on WW-5026:
--------------------------------

With this change, it is now not allowing me to debug my class, it seems to be doing the what
the action would have done bypassing the actual class.  ie it does not break on my beakpoint.

If I go back to STRUTS_2_5_20, on the invalid token, it calls the "original" class ie stops
on the break point, so I can see what it is doing.

Does this make sense?

 

> Double-submit of TokenSessionStoreInterceptor broken since 2.5.16
> -----------------------------------------------------------------
>
>                 Key: WW-5026
>                 URL: https://issues.apache.org/jira/browse/WW-5026
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Core Interceptors
>    Affects Versions: 2.5.16, 2.5.20
>         Environment: Tomcat 7.0.x (but should reproduce on any application server)
>            Reporter: James Chaplin
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.5.22, 2.6
>
>
> With recent fixes to the Showcase application it was discovered that the 3rd Token example
(for TokenSessionStoreInterceptor) is failing upon the double-submit with Struts versions
2.5.16 - 2.5.20 (and 2.5.21 snapshot).  Steps to reproduce:
> 1) Launch Struts 2.5.21-snapshot showcase application
> 2) Open the Examples, Token, Example 3.
> 3) Click on submit (wait for completion), back button in browser, then submit again.
> 4) Application container returns a response code 500.
> The issue appears to have been introduced with fixes for WW-4873.  A proposed fix for
this issue will be provided in a PR shortly.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message