[
https://issues.apache.org/jira/browse/MIME4J-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563693#action_12563693
]
Oleg Kalnichevski commented on MIME4J-34:
-----------------------------------------
Robert, et al
Many browsers indeed use content charset to encode multipart header values, so
we will have to provide a browser compatible mode in HttpClient. However, as
far as the strict interpretation of the MIME standard is concerned only ASCII
characters seem permissible and non-ASCII are expected to be escaped using
BASE64 or Quoted-Printable encodings.
====
field = field-name ":" [ field-body ] CRLF
field-name = 1*<any CHAR, excluding CTLs, SPACE, and ":">
field-body = field-body-contents
[CRLF LWSP-char field-body]
field-body-contents =
<the ASCII characters making up the field-body, as
defined in the following sections, and consisting
of combinations of atom, quoted-string, and
specials tokens, or else consisting of texts>
====
If you like I can implement two modes for Header#writeTo and Multipart#writeTo
methods: strict (ASCII) and lenient (content charset). We'll need this feature
in HttpClient anyways.
Oleg
> o.a.j.m.message.Header#writeTo violates RFC 822
> -----------------------------------------------
>
> Key: MIME4J-34
> URL: https://issues.apache.org/jira/browse/MIME4J-34
> Project: Mime4j
> Issue Type: Bug
> Affects Versions: 0.3
> Reporter: Oleg Kalnichevski
> Attachments: mimeheader.patch
>
>
> The Header#writeTo method uses the content charset instead of US-ASCII
> required by the RFC 822. Same problem exists in the Multipart#writeTo.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
