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

Peter Pastrnak edited comment on WICKET-4019 at 9/8/11 6:08 AM:
----------------------------------------------------------------

yes, but we would like to finish tests on one of our bigger projects first. 
this should take about 2 weeks. afterwards I can write what are differences 
between the old and the new version, that I know about. Because currently I 
f.e. removed the possibility to have shared resources, that are accessed 
directly, avoiding the portlet container. This behaviour was not desirable for 
us, as these are portlet resources, so we need to have them and their urls to 
be controlled by the portlet container. this type of urls used to be generated 
for all 'ISharedResourceRequestTarget'...

      was (Author: pasto):
    yes, but we would like to finish tests on one of our bigger projects first. 
this should take about 2 weeks. afterwards I can write what are differences 
between the old and the new version, that I know about. Because currently I 
f.e. removed the possibility to have shared resources, that are accessed 
directly, avoiding the portlet container. This behaviour was not desirable for 
us, as these are portlet resources, so we need to have them and their urls to 
be controlled by the portlet container. this type of urls used to by generated 
for all 'ISharedResourceRequestTarget'...
  
> UrlEncoder - question mark not encoded in parameter values
> ----------------------------------------------------------
>
>                 Key: WICKET-4019
>                 URL: https://issues.apache.org/jira/browse/WICKET-4019
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5-RC7
>            Reporter: Peter Pastrnak
>
> Url returned by the RequestMapper does not seem to be properly rendered, as 
> it does not encode question mark character in the Url parameter value (I 
> haven't checked the w3c spec, but at least Liferay Portal seems to require it 
> to be encoded) 
> The reason is this definition in the UrlEncoder: 
>                         case QUERY : 
>                                 // to allow direct passing of URL in query 
>                                 dontNeedEncoding.set('/'); 
>                                 // to allow direct passing of URL in query 
>                                 dontNeedEncoding.set('?'); 
> Currently URL "http://host/file?param=a?b"; would be encoded as 
> "http://host/file?param=a?b";, instead of "http://host/file?param=a%3Fb";

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to