struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (WW-5026) Double-submit of TokenSessionStoreInterceptor broken since 2.5.16
Date Mon, 25 Mar 2019 05:04:00 GMT


ASF GitHub Bot commented on WW-5026:

JCgH4164838Gh792C124B5 commented on pull request #342: Proposed fix for WW-5026 (TokenSessionStoreInterceptor
double-submit failure)
   Fix issue introduced with earlier WW-4873 fix:
   - Fixes error 500 processing failures for double-submit results with TokenSessionStoreInterceptor
   - Fix to InvocationSessionStore, new unit test confirming fix in InvocationSessionStoreTest
   - Minor whitespace fix to TokenSessionStoreInterceptor
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Double-submit of TokenSessionStoreInterceptor broken since 2.5.16
> -----------------------------------------------------------------
>                 Key: WW-5026
>                 URL:
>             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.21
> 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

View raw message