[
https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187826#comment-15187826
]
Thiago H. de Paula Figueiredo commented on TAP5-1803:
-----------------------------------------------------
I'm also against skipping checks for decoding. For simplicity, consistency and
bug avoidance, the encoding and decoding should always lead to the same results
(if I decode and then encode then decode the same string, it should match the
original value), all that IMHO, of course.
On the other hand, having a first language with accents :D, I'm not against of
making the safe character set bigger, including more characters, and/or making
it configurable.
> URL encoding in ActivationRequestParameter is very strict
> ---------------------------------------------------------
>
> Key: TAP5-1803
> URL: https://issues.apache.org/jira/browse/TAP5-1803
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.3.1, 5.4
> Reporter: David Canteros
> Labels: @ActivationRequestParameter, InvalidaArgumenteException,
> URLEncoder,
>
> The URLEncoder that perform the URL encoding process does not include the
> following "unreserved characters" :
> ! ~ * ' ( )
> (see rfc2396 Uniform Resource Identifiers (URI): Generic Syntax, item 2.3)
>
> Because the fix of TAP5-1768, from v5.3.1 the @ActivationRequestParameter
> requires this enconding, which becomes incompatible with the standard.
> Thus, any URL which contains those symbols will throw an
> InvalidaArgumenteException. Tapestry should consider that the
> ActivationRequestParameter is a standar way of parameter sending, and the
> parameters sent in this way probably not have the "strict" coding process of
> the URLEncoder.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
