[HTTPCLIENT-2064] MultipartEntityBuilder should support preamble and epilog

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0
• Fix Version/s: 5.3-alpha1
• Component/s: HttpClient (classic)
• Assignee: Unassigned
• Reporter: Michael Osipov
• Created: 17/Mar/20 20:34
• Updated: 01/Apr/23 07:07
• Resolved: 01/Apr/23 07:07

Description

According to RFC 2046, section 5.1.1 one can augment the multipart message with a preamble and an epilog. Both may consist of:
 

     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.

text is defined in RFC 822, section 3.3 as:

    text =  <any CHAR, including bare   ; => atoms, specials,
            CR & bare LF, but NOT       ;  comments and
            including CRLF>             ;  quoted-strings are
                                        ;  NOT recognized.

CHAR is 0 to 127.

This could be added as

MultipartEntityBuilder#addPreamble()
MultipartEntityBuilder#addEpilog()