[Devel] [ openser-Bugs-1604485 ] NOTIFY Message missing Content-Length TCP

[SourceForge.net]

Bugs item #1604485, was opened at 2006-11-28 15:46
Message generated for change (Comment added) made by bogdan_iancu
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1604485&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: ver 1.1.x
Status: Open
>Resolution: Accepted
Priority: 5
Private: No
Submitted By: chris (chrisrobson)
>Assigned to: Bogdan (bogdan_iancu)
Summary: NOTIFY Message missing Content-Length TCP

Initial Comment:
The NOTIFY message sent via TCP is missing the "Content-Length" field which is required based on RFC3261 paragraph 20.14 which states: "If a stream-based protocol (such as TCP) is used as transport, the header field MUST be used."  This is agravating message header processing errors within applications such as Gaim which assume the field is present.

Suggest OpenSER check for transmitted NOTIFY messages and assure the Content-Length field is inserted and valid for tcp packets.

To test:  Use Gaim 2.0 Beta 5 and OpenSER 1.2.0-dev6-notls have to clients establish a chat session.  Problem will ocure when the first OpenSER NOTIFY is sent to the clients.

----------------------------------------------------------------------

>Comment By: Bogdan (bogdan_iancu)
Date: 2006-11-28 16:45

Message:
Logged In: YES 
user_id=1275325
Originator: NO

Even if the RFC says it is not mandatory in all cases, I think the best
approach is to have the Content-Length all the time. 
I will fix it soon.

bogdan

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1604485&group_id=139143