click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Moritz Kammerer (JIRA)" <j...@apache.org>
Subject [jira] Created: (CLK-727) Use real RFC-1738 encoding, don't rely on the URLEncoder/URLDecoder class.
Date Thu, 04 Nov 2010 09:57:43 GMT
Use real RFC-1738 encoding, don't rely on the URLEncoder/URLDecoder class.
--------------------------------------------------------------------------

                 Key: CLK-727
                 URL: https://issues.apache.org/jira/browse/CLK-727
             Project: Click
          Issue Type: Bug
          Components: core
            Reporter: Moritz Kammerer


The URLEncoder/URLDecoder used by click to encode parameters of links etc. doesn't produce
valid urls according to RFC-1738 [1].

When adding a parameter to a link that contains the char รถ, it isn't encoded to %F6.
I've tried to manually encode the parameter, but unfortunatelly the URLEncoder encodes my
% sign to %25 (so it is double encoded).

Btw, the URLEncoder encodes a space to a plus sign, and not, as stated in the click documentation,
to %20.

Please change the encoding/decoding to a RFC-1738 compliant encoder. I can provide an implementation,
if needed.

[1] http://www.faqs.org/rfcs/rfc1738.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message