> From: [email protected] [[email protected]] > > I have some doubts about the use of the Content-Length when a sip > message contains a multi-part body. A previous and quite old discussion > on this mailing list has clarified that the Content-Length associated > with the "Content-Type = multipart/mixed" tells the length of the > complete body of the sip message. > > https://lists.cs.columbia.edu/pipermail/sip-implementors/2008-March/0187 > 89.html > > However, I have recently eared different opinions as to whether > additional Content-Length header fields may also be associated to > individual parts of the multi-part body and inserted between the > different parts. > I don't see any need for adding such fields but I'm wondering whether > doing that should even be > considered an error?
The syntax and semantics of a multipart body is governed by RFC 1521. The relevant part seems to be section 7.2. Within RFC 1521, the "Content-Length" header is not defined. Section 7.2 says that only a very few headers on body parts are meaningful (and Content-Length is not among them). The section implies that other, meaningless headers are expected to be see and should be ignored. > Meantime I have also noticed that some of the examples in section 12.2.2 > of RFC6086 contain multiple content-length header fields and I'm > therefore wondering whether this should be considered an error! Since there is no defined meaning for such a Content-Length header, it seems to be incorrect that the header was shown in the examples. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
