geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-3638) should allow URL encoding with custom encoding charset other than the default
Date Wed, 28 Nov 2007 21:44:43 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546418
] 

Sangjin Lee commented on GERONIMO-3638:
---------------------------------------

Hmm, I swear I remember seeing the RFCs (2616 and 2396 which supplants 1738) mention different
*URL* encoding than us-ascii (e.g. utf-8), but I cannot find it at the moment...

At minimum, shouldn't we use "ISO-8859-1" or "US-ASCII" explicitly instead of using Charset.defaultCharset()?
 If the JVM is running on a non-US box, Charset.defaultCharset() would return a different
charset than ascii, no?  Thanks.

> should allow URL encoding with custom encoding charset other than the default
> -----------------------------------------------------------------------------
>
>                 Key: GERONIMO-3638
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3638
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: AsyncHttpClient
>    Affects Versions: 1.x
>            Reporter: Sangjin Lee
>         Attachments: patch.zip
>
>
> Currently AsyncHttpClient uses Chartset.defaultCharset() when it encodes the query string.
 However, applications may want to use a different encoding than the machine default charset;
e.g. UTF-8.  It needs to provide a way to specify an encoding that AHC should use to encode
the query string.

-- 
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