hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 30420] - [PATCH]character encoding handling is invalid at multipart
Date Mon, 02 Aug 2004 07:52:37 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30420>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30420

[PATCH]character encoding handling is invalid at multipart





------- Additional Comments From adrian@ephox.com  2004-08-02 07:52 -------
According to RFC 2388 (http://www.faqs.org/rfcs/rfc2388.html), section 3, the encoding of
header 
values is ASCII but non-ASCII characters may be encoded according to RFC2047 (http://www.faqs.org/
rfcs/rfc2047.html) which is MIME encoding.  So as far as I can tell this patch is incorrect
but we may 
want to consider having the capability for HttpClient to use RFC2047 encoding automatically
when 
required.

The current workaround is to simply specify the header values pre-encoded according to RFC2047.

Does that seem right to anyone else?

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org


Mime
View raw message