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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
