Re: [Anima] Content-Transfer-Encoding and HTTP 1.x in ANIMA BRSKI

On 13.06.2019 00:14, Michael Richardson wrote:
>
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>      >> There is no Content-Transfer-Encoding header field in HTTP. It is simply
>      >> not needed.
>
>      > Just as a matter of curiosity, what happened in HTTP1.1 to the fragment in
>      > RFC2616 that says (under Content-MD5):
>
>      > "The entity-body for composite
>      > types MAY contain many body-parts, each with its own MIME and HTTP
>      > headers (including Content-MD5, Content-Transfer-Encoding, and
>      > Content-Encoding headers)."
>
> yes, I was going to bring this up next :-)

That's about header fields in payloads of type multipart/*. The text is
gone in later specs, because Content-MD5 is.

> ...

Best regards, Julian