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] Updated: (GERONIMO-3638) should allow URL encoding with custom encoding charset other than the default
Date Wed, 28 Nov 2007 18:51:43 GMT

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

Sangjin Lee updated GERONIMO-3638:
----------------------------------

    Attachment: patch.zip

A suggested fix.  It appears the charset variable in HttpMessage is unused, and it seems to
be intended for the content charset.  The only place this charset is used is when we URL encode
the form/query.


> 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