You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2016/07/14 11:59:20 UTC

[jira] [Updated] (TAP5-1803) URL encoding in ActivationRequestParameter is very strict

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

Jochen Kemnade updated TAP5-1803:
---------------------------------
    Labels: @ActivationRequestParameter InvalidaArgumenteException URLEncoder, desired_for_5.5  (was: @ActivationRequestParameter InvalidaArgumenteException 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)