You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Mitth'raw'nuruodo (JIRA)" <ji...@apache.org> on 2016/07/28 23:37:20 UTC

[jira] [Comment Edited] (WW-4669) Struts 2.5.1 gives errors on unexpected action names

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

Mitth'raw'nuruodo edited comment on WW-4669 at 7/28/16 11:36 PM:
-----------------------------------------------------------------

We already know how to adjust the regex. The point is, previously the regex resulted in a warning and an attempt to clean up the URL, whereas now it results in an exception. We don't want this change, it wasn't in the changelog (which resulted in a release breaking a production system until we rolled it back) nor even associated with a JIRA issue, and what is the justification for it?


was (Author: thrawnca):
We already know how to adjust the regex. The point is, previously the regex resulted in a warning and an attempt to clean up the URL, whereas now it results in an exception. We don't want this change, it wasn't in the changelog (which resulted in a release breaking a production system until we rolled it back), and what is the justification for it?

> Struts 2.5.1 gives errors on unexpected action names
> ----------------------------------------------------
>
>                 Key: WW-4669
>                 URL: https://issues.apache.org/jira/browse/WW-4669
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Core Actions, Documentation
>    Affects Versions: 2.5.1
>            Reporter: Mitth'raw'nuruodo
>             Fix For: 2.5.3
>
>
> As of Struts 2.5.1 (specifically, commit 27ca165ddbf81c84bafbd083b99a18d89cc49ca7), URLs containing unexpected characters are rejected, instead of cleaned up. This breaks the interaction of one of our clients, who unfortunately is using braces in their URL (matched at our end by a wildcard).
> We want to keep specifying a strict list of allowed characters, for cleanup purposes, but we can't do that if it will break interactions with customers.
> What was the purpose of changing this behavior? I can't find anything about it in the changelog.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)