wait, if you think that jetty is correct, then you can't use UrlEncoding to encode context parameters, since the bug shows up in jetty, but not tomcat.

Howard M. Lewis Ship (JIRA) wrote:
     [ 
https://issues.apache.org/jira/browse/TAPESTRY-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Howard M. Lewis Ship closed TAPESTRY-2187.
------------------------------------------

    Resolution: Incomplete
      Assignee: Howard M. Lewis Ship

I'm still of the opinion that Tapestry and Jetty are right and Tomcat is wrong, 
or that there's some other issue involved.  Please reopen if you have a 
definitive answer.

Context Parameter Encoding confuses Jetty Server, use non UrlEncoding.
----------------------------------------------------------------------

                Key: TAPESTRY-2187
                URL: https://issues.apache.org/jira/browse/TAPESTRY-2187
            Project: Tapestry
         Issue Type: Bug
         Components: tapestry-core
   Affects Versions: 5.0.11
           Reporter: Fernando
           Assignee: Howard M. Lewis Ship

TapestryInternalUtils.escapePercentAndSlash escapes the Percent and Slash 
characters using URL encoding.  This confuses Jetty, and could confuse browsers 
and other servers because of unknown times of encoding/decoding done by 
browsers and servers...
I propose to change the constants in TapestryInternalUtils:
    private static final String ENCODED_PERCENT = "%25";
    private static final String ENCODED_SLASH = "%2F";
to use a different escape character, maybe one of the unreserved characters: "-", "_", 
".", "~"; then make sure to encode that character as well..
so ENCODED_PERCENT would be ~25, ENCODED_SLASH would be ~2F
and we would add ENCODED_TILDE to be ~7E
http://en.wikipedia.org/wiki/Percent-encoding


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to