[
https://issues.apache.org/jira/browse/HTTPCLIENT-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061861#comment-17061861
]
Michael Osipov commented on HTTPCLIENT-2064:
--------------------------------------------
I am quite happy with HttpMime. It covers all of my needs. Having both would be
a nice bonus. Mime4J looks like overkill in my case. I need to see how good
HttpMime scales and will add improvements as I go with a new service. I don't
think that preamble or epilog are anything special here. I might pick this up
when I get bored during the working ban.
> MultipartEntityBuilder should support preamble and epilog
> ---------------------------------------------------------
>
> Key: HTTPCLIENT-2064
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2064
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient (classic)
> Affects Versions: 5.0
> Reporter: Michael Osipov
> Priority: Major
>
> According to RFC 2046, section 5.1.1 one can augment the multipart message
> with a preamble and an epilog. Both may consist of:
>
> {noformat}
> multipart-body := [preamble CRLF]
> dash-boundary transport-padding CRLF
> body-part *encapsulation
> close-delimiter transport-padding
> [CRLF epilogue]
> preamble := discard-text
> epilogue := discard-text
> discard-text := *(*text CRLF) *text
> ; May be ignored or discarded.
> {noformat}
> {{text}} is defined in RFC 822, section 3.3 as:
> {noformat}
> text = <any CHAR, including bare ; => atoms, specials,
> CR & bare LF, but NOT ; comments and
> including CRLF> ; quoted-strings are
> ; NOT recognized.
> {noformat}
> {{CHAR}} is 0 to 127.
> This could be added as
> {code}
> MultipartEntityBuilder#addPreamble()
> MultipartEntityBuilder#addEpilog()
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
