[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[ https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323473#comment-16323473 ] Rural Hunter commented on TAP5-1803: This problem still exists in Tapestry 5.4 > 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,, desired_for_5.5 > > 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.4.14#64029)
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[
https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176079#comment-16176079
]
Rural Hunter commented on TAP5-1803:
In our environment, we just did this in ActivationRequestParameterWorker:
change the line "clientValue = urlEncoder.decode(clientValue);" to this:
try
{
clientValue = urlEncoder.decode(clientValue);
}
catch(IllegalArgumentException ie)
{
}
if URLEncoderImpl can decode, we let it decode. If it cannot, we do nothing.
> 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,, desired_for_5.5
>
> 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.4.14#64029)
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[
https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947090#comment-15947090
]
Jochen Kemnade commented on TAP5-1803:
--
I was just about to change {{ActivationRequestParameterWorker}}, but that would
break old links, e.g. from the browser history, when people upgrade to 5.5.
> 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,, desired_for_5.5
>
> 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.15#6346)
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[ https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381042#comment-15381042 ] Kalle Korhonen commented on TAP5-1803: -- I agree with Jochen on both counts: I think we should remove the safe character check and change the request parameter handling to use URLEncoder. > 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,, desired_for_5.5 > > 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)
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[
https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376801#comment-15376801
]
Jochen Kemnade commented on TAP5-1803:
--
See TAP5-1768.
Maybe we should change {{ActivationRequestParameterWorker}} to use
{{java.net.URLEncoder.encode(String, String)}} instead.
Still, I think we should remove the safe character check to improve support for
links that were not generated by Tapestry.
> 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)
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[
https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15375842#comment-15375842
]
Thiago H. de Paula Figueiredo commented on TAP5-1803:
-
Hello, [~jkemnade] and [~kaosko]!
To be honest, in hindsight, I'm not sure why {{URLEncoder}} is used over
anything which goes into or comes from request parameters, making them not work
as anyone would expect. Regarding handling of empty string vs null, I don't
think Tapestry should do any encoding about it: if no query parameter with that
name, field receives null; if query parameter with that name but no value,
field receives whatever the contributed {{ValueEncoder}} is for its Java type.
{{URLEncoder}} usage makes sense for activation contexts, and query parameters
are most definitely *not* activation context.
Cheers!
> 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)
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[ https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15375006#comment-15375006 ] Jochen Kemnade commented on TAP5-1803: -- [~thiagohp], anything new to add here? > 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)
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[ https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15194095#comment-15194095 ] Kalle Korhonen commented on TAP5-1803: -- Replacing the URLEncoderImpl with a custom implementation has been one of the first tasks in most real world projects I've been involved in - the built-in one really doesn't give a reasonable default behavior IMHO. I agree with Jochen, just skipping the safe set check when decoding seem like a good, common sense improvement. > 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)
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[ https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1510#comment-1510 ] Jochen Kemnade commented on TAP5-1803: -- AFAICT, skipping the safe set check when decoding would not affect consistency. The encoding would still work in the same way that it does now and decoding of Tapestry-encoded strings would not be affected. However, it will allow us to use parameters that were not encoded by Tapestry. I think that we should not change the safe set. That will probably lead to inconsistencies between versions. At least it will make newer Tapestry versions create URLs that older versions wouldn't be able to decode. > 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)
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[ https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[ https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187049#comment-15187049 ] Jochen Kemnade commented on TAP5-1803: -- What if we just skip the check against the safe character set when *decoding*? We could still keep the special handling for blank and null values in place. But I don't see a need to enforce the dollar encoding for incoming URLs. > 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)
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[ https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703038#comment-14703038 ] Jochen Kemnade commented on TAP5-1803: -- Recent versions will return a HTTP 404 instead (see TAP5-2436), but the original problem is still there. Maybe we should really be a little more forgiving when *de*coding. 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 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)
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[ https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13474103#comment-13474103 ] Rural Hunter commented on TAP5-1803: I encounterred the same problem.why hasn't this been fixed yet? 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 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[ https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13474149#comment-13474149 ] David Canteros commented on TAP5-1803: -- Probably because the framework developer's did not have to deal with this problem, but in recent times has increased the reports of this problem. I hope we will have a solution soon... 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 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[ https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13445792#comment-13445792 ] Thomas Hackel commented on TAP5-1803: - Still no news here? This is a major issue not a simple feature request! It was reported over half a year ago an since then 4 Tapestry releases were made... 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 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[ https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13444697#comment-13444697 ] Christian Köberl commented on TAP5-1803: Nice - when you search the Exception with DuckDuckGo the third hit is the exception happening live: http://www.clio.se/klubb/cat/%C3%B6ver?a=first 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 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[ https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13209452#comment-13209452 ] Ulrich Stärk commented on TAP5-1803: we would loose automatic conversion from/to empty strings and null values then. 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 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[ https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13187139#comment-13187139 ] Jochen Frey commented on TAP5-1803: --- It would be nice if ActivationRequestEncoding would utilize the W3C standard encoding (%-encoding), so that Tapestry would compatible rest URLs with parameters generated by other tools. 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 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict
[ https://issues.apache.org/jira/browse/TAP5-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13175480#comment-13175480 ] Howard M. Lewis Ship commented on TAP5-1803: Can you give some real-world examples where Tapestry's behavior would be a problem? 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 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
