[
https://issues.apache.org/jira/browse/MIME4J-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565541#action_12565541
]
robertburrelldonkin edited comment on MIME4J-34 at 2/4/08 1:36 PM:
---------------------------------------------------------------------
"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."
This sounds good to me. Probably 4 modes would be good (but i can patch any you
miss):
standard-strict should be ASCII+ERROR (when a string contains non-ASCII
characters, the operation fails)
standard-lenient would be ASCII+REPLACE (or IGNORE?)
international-strict would content+ERROR
international-lenient would content+REPLACE (or IGNORE?)
AIUI current default is international-lenient
Robert
was (Author: robertburrelldonkin):
"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."
This sounds good to
Robert
> 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, 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]
