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

David Canteros edited comment on TAP5-1803 at 10/11/12 2:12 PM:
----------------------------------------------------------------

Probably because the framework developer's did not have to deal with this 
problem yet. In recent times the reports have been increased so I hope we will 
have a solution soon...
                
      was (Author: dcanteros):
    Probably because the framework developer's did not have to deal with this 
problem yet, but in recent times the reports have been increased so 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

Reply via email to