You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Kapep (JIRA)" <ji...@apache.org> on 2012/10/20 13:50:11 UTC
[jira] [Created] (TAP5-2015) Tomcat .war path is not decoded
properly
Kapep created TAP5-2015:
---------------------------
Summary: Tomcat .war path is not decoded properly
Key: TAP5-2015
URL: https://issues.apache.org/jira/browse/TAP5-2015
Project: Tapestry 5
Issue Type: Bug
Components: plastic
Affects Versions: 5.3.6
Reporter: Kapep
If an tapestry application is deployed to tomcat and the path to a webapp contains hash signs (#), org.apache.tapestry5.internal.plastic.PlasticInternalUtils.getStreamForPath tries to read files from a wrong directory: instead a hash sign, the path it tries to read contains the sequence %23.
This results in a FileNotFoundException and causes the app to fail starting.
getStreamForPath already replaces url encoded %20 space characters for tomcat, it should also replace hash signs - and maybe even more valid file name characters.
Background: Tomcat 6 uses hash signs in war file names as replacement for slashes, so that the file name can be used to construct the webapp's url. The war is unpacked to a directory which name is the war's file name without the .war extension and therefore can contain hash signs. Tomcat 7 uses two hash signs for the same purpose.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TAP5-2015) Tomcat .war path is not decoded
properly
Posted by "Kalle Korhonen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kalle Korhonen resolved TAP5-2015.
----------------------------------
Resolution: Duplicate
Fix Version/s: 5.4
5.3.7
Assignee: Kalle Korhonen
https://issues.apache.org/jira/browse/TAP5-1995
> Tomcat .war path is not decoded properly
> ----------------------------------------
>
> Key: TAP5-2015
> URL: https://issues.apache.org/jira/browse/TAP5-2015
> Project: Tapestry 5
> Issue Type: Bug
> Components: plastic
> Affects Versions: 5.3.6
> Reporter: Kapep
> Assignee: Kalle Korhonen
> Labels: tomcat
> Fix For: 5.3.7, 5.4
>
>
> If an tapestry application is deployed to tomcat and the path to a webapp contains hash signs (#), org.apache.tapestry5.internal.plastic.PlasticInternalUtils.getStreamForPath tries to read files from a wrong directory: instead a hash sign, the path it tries to read contains the sequence %23.
> This results in a FileNotFoundException and causes the app to fail starting.
> getStreamForPath already replaces url encoded %20 space characters for tomcat, it should also replace hash signs - and maybe even more valid file name characters.
> Background: Tomcat 6 uses hash signs in war file names as replacement for slashes, so that the file name can be used to construct the webapp's url. The war is unpacked to a directory which name is the war's file name without the .war extension and therefore can contain hash signs. Tomcat 7 uses two hash signs for the same purpose.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TAP5-2015) Tomcat .war path is not decoded
properly
Posted by "Kalle Korhonen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kalle Korhonen resolved TAP5-2015.
----------------------------------
Resolution: Duplicate
Fix Version/s: 5.4
5.3.7
Assignee: Kalle Korhonen
https://issues.apache.org/jira/browse/TAP5-1995
> Tomcat .war path is not decoded properly
> ----------------------------------------
>
> Key: TAP5-2015
> URL: https://issues.apache.org/jira/browse/TAP5-2015
> Project: Tapestry 5
> Issue Type: Bug
> Components: plastic
> Affects Versions: 5.3.6
> Reporter: Kapep
> Assignee: Kalle Korhonen
> Labels: tomcat
> Fix For: 5.3.7, 5.4
>
>
> If an tapestry application is deployed to tomcat and the path to a webapp contains hash signs (#), org.apache.tapestry5.internal.plastic.PlasticInternalUtils.getStreamForPath tries to read files from a wrong directory: instead a hash sign, the path it tries to read contains the sequence %23.
> This results in a FileNotFoundException and causes the app to fail starting.
> getStreamForPath already replaces url encoded %20 space characters for tomcat, it should also replace hash signs - and maybe even more valid file name characters.
> Background: Tomcat 6 uses hash signs in war file names as replacement for slashes, so that the file name can be used to construct the webapp's url. The war is unpacked to a directory which name is the war's file name without the .war extension and therefore can contain hash signs. Tomcat 7 uses two hash signs for the same purpose.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira