[ 
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.1.4.zip

Changes in version 1.5.1.4:
1. getHeader, getHeaders calls are not case sensitive (workaround for GateIn 
Portal)
2. Parameters added by Javascript (not in the resourceId) are part of the 
queryString, so they are not treated as Post parameters anymore.
3. Portlet bridge should detect Ajax redirects and correct the URL.
4. All Wicket request parameters (that are properly namespaced) are stripped 
from the generated resourceUrl (as they belong to the request and should not 
affect the generated URL).
                
> 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-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.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