[
https://issues.apache.org/jira/browse/TAPESTRY-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543767
]
Howard M. Lewis Ship commented on TAPESTRY-1911:
------------------------------------------------
At first I put this down to a misunderstanding on my part of the servlet API.
However, when I remove the explicit URL decoding logic, existing tests break.
Specifically, tests for cases where there are URL encoded characters inside the
context. These are Selenium tests, which means that the full servlet API stack
from Jetty, unchanged, is in charge ... and that brings into question the
thought that it is servlet containers job to URL decode.
> Context unnecessarley decoded in PageRenderDispatcher and
> ComponentActionDispatcher
> -----------------------------------------------------------------------------------
>
> Key: TAPESTRY-1911
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1911
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.3, 5.0.4, 5.0.5, 5.0.6
> Reporter: Ted Steen
> Fix For: 5.0.7
>
>
> In PageRenderDispatcher, these two lines will result in a
> TapestryInternalUtils.urlDecode() on
> the context.
> 069 String[] context = atEnd ? new String[0] :
> convertActivationContext(path
> 070 .substring(nextslashx + 1));
> It seems that this is already done by the servlet, so the decoding is
> done twice, and results in malformed contexts.
> This also applies to the ComponentActionDispatcher
> Look here for previous discussions,
> http://mail-archives.apache.org/mod_mbox/tapestry-users/200706.mbox/[EMAIL
> PROTECTED]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
