You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Michael Freedman (JIRA)" <de...@myfaces.apache.org> on 2012/08/02 01:37:04 UTC
[jira] [Resolved] (PORTLETBRIDGE-223) Bridge mishandles encodings
of urls with targets containing same prefix as contextpath
[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Freedman resolved PORTLETBRIDGE-223.
--------------------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
2.0.1
Code in ExternalContext now explicitly checks to make sure that string matches aren't inadvertently finding the name elsewhere in the path/target.
> Bridge mishandles encodings of urls with targets containing same prefix as contextpath
> --------------------------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-223
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-223
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Components: Impl
> Affects Versions: 1.0.0, 2.0.0, 3.0.0-alpha
> Reporter: Michael Freedman
> Assignee: Michael Freedman
> Fix For: 2.0.1, 3.0.0
>
>
> If a target is prefixed with the same name/string as the context path, the bridge mishandles encoding/decoding the URLs as portlet urls. For example if the contextpath is /simple and the path is /simple.jspx code in the bridge's ExternalContext will break as there are several locations where the bridge either needs to adds the ContextPath during encoding or strip the ContextPath during decoding. In both cases the bridge incorrectly recognizes the CP in the above example (/simple.jspx) when its not there. All tests for context path must therefore not only check that string startwith the CP but in fact ends with a /.
--
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