from the AD: content-length is invalid within multipart

(this is with my AD hat on)

The MIME multipart definition, for better or worse, is set in stone.

The end of a component of a multipart is specified by its boundary
marker.  Any Content-Length field in a component of a multipart is
nonstandard, irrelevant, and must be ignored.

It is always possible to define a new length-delimited multi-component
content-type if there is a need for one.  But HTTP can't change the
definition of an existing and well-established content-type.

Keith Moore

p.s this is somewhat redundant with a statement that I made a couple
of days ago, but an editing glitch made that statement somewhat muddy.

Received on Wednesday, 7 May 1997 09:31:12 UTC