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

SourceForge.net noreply at sourceforge.net
Tue Nov 28 14:46:56 CET 2006


Bugs item #1604485, was opened at 2006-11-28 13:46
Message generated for change (Tracker Item Submitted) made by Item Submitter
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: None
Priority: 5
Private: No
Submitted By: chris (chrisrobson)
Assigned to: Nobody/Anonymous (nobody)
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.

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

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



More information about the Devel mailing list