5 Feb
2023
5 Feb
'23
10:55 p.m.
This should apply not only to UDP and SCTP, but also to WebSockets:
https://www.rfc-editor.org/rfc/rfc7118.html#section-5
Because the WebSocket transport preserves message
boundaries, the use of the Content-Length header in SIP messages is not necessary when
they are transported using the WebSocket subprotocol.
This simplifies the parsing of SIP messages for both
clients and servers. There is no need to establish message boundaries using
Content-Length headers between messages. Other SIP transports, such as UDP and the Stream
Control Transmission Protocol (SCTP) [[RFC4168](https://www.rfc-editor.org/rfc/rfc4168)],
also provide this benefit.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3359#issuecomment-1418250206
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3359/c1418250206(a)github.com>