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

Peter Pastrnak updated WICKET-4019:
-----------------------------------

    Attachment: wicket-portlet-1.5.5.1.zip

Little 'hack' to fix the problem with form submit, when there is a parameter, 
that needs an URL encoding. Now parameters, that are added by javascript to the 
URL, but not to the "_wu" parameter, will become part of the query parameters 
only in case of a GET request. There is no perfect solution for this, as we do 
not have control over the javascript library, to force it to add parameters to 
the _wu parameter instead of adding a new parameter. This way for GET requests 
we merge the URL parameters with the _wu parameter and for all other HTTP 
methods we use only the query parameters, that are contained in the _wu url. 
('standalone' parameters added by javascript will be accessible still 
accessible as POST parameters.)
                
> Portlet Support 1.5
> -------------------
>
>                 Key: WICKET-4019
>                 URL: https://issues.apache.org/jira/browse/WICKET-4019
>             Project: Wicket
>          Issue Type: New Feature
>          Components: wicket
>    Affects Versions: 1.5-RC7
>            Reporter: Peter Pastrnak
>         Attachments: PortletServletRequestWrapper.java, ResponseState.java, 
> Wicket - Portlet.htm, wicket-1.5.2.1.zip, wicket-portlet-1.5.0.zip, 
> wicket-portlet-1.5.1.1.zip, wicket-portlet-1.5.1.2.zip, 
> wicket-portlet-1.5.1.3.zip, wicket-portlet-1.5.1.4.zip, 
> wicket-portlet-1.5.1.5.zip, wicket-portlet-1.5.1.zip, 
> wicket-portlet-1.5.2.2.zip, wicket-portlet-1.5.2.4.zip, 
> wicket-portlet-1.5.2.zip, wicket-portlet-1.5.5.0.zip, 
> wicket-portlet-1.5.5.1.zip, wicket-portlet-1.5.RC7.zip, with bind(this).jpg, 
> without bind(this).jpg
>
>
> 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.
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

        

Reply via email to