[ 
https://issues.apache.org/jira/browse/WW-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mitth'raw'nuruodo updated WW-4669:
----------------------------------
    Description: 
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.

  was:
As of Struts 2.5.1, 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.


> 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
>    Affects Versions: 2.5.1
>            Reporter: Mitth'raw'nuruodo
>
> 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)

Reply via email to