Hi Sudhir, I guess this is correct behavior.
18.3 Framing In the case of message-oriented transports (such as UDP), if the message has a Content-Length header field, the message body is assumed to contain that many bytes. If there are additional bytes in the transport packet beyond the end of the body, they MUST be discarded. If the transport packet ends before the end of the message body, this is considered an error. If the message is a response, it MUST be discarded. If the message is a request, the element SHOULD generate a 400 (Bad Request) response. If the message has no Content-Length header field, the message body is assumed to end at the end of the transport packet. In the case of stream-oriented transports such as TCP, the Content- Length header field indicates the size of the body. The Content- Length header field MUST be used with stream oriented transports. Regards, Amit Goyal >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:sip-implementors- >[EMAIL PROTECTED] On Behalf Of Sudhir Sharma >Sent: Tuesday, August 28, 2007 2:55 PM >To: [email protected] >Subject: [Sip-implementors] Proxy behavior for Content-Length > >Hello, > >Could anybody tell me about the behavior of Proxy when value of >Content-Length header field is less than the actual length of the body? >Currently in such scenario my sip proxy juts forwards the body of the >size mentioned in Content-Length and discards the remaining body. >Is this the correct behavior? > >I could not find relevant information for such case in any SIP RFCs. > >Appreciate your prompt response. > >Thanks, >Sudhir > > > >_______________________________________________ >Sip-implementors mailing list >[email protected] >https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
