2009/2/13 Della Betta Filippo <filippo.dellabe...@telecomitalia.it>: > I noticed some strange behavior in extract_first of msg_parser.c. It > seems that a request line that begins with LWS, or ends after CRLF is a valid > request line. > The followings are all valid according sofia-sip parser (double quote > excluded). > > " INVITE sip:a...@b.c SIP/2.0" > > "INVITE sip:a...@b.c SIP/2.0 > " > > I also noticed that you have tests for that (test1.txt and test1a.txt). > According to RFC3261, request line is > Request-Line = Method SP Request-URI SP SIP-Version CRLF > and Method cannot begin with SP. Also Request-Line ends with CRLF. > Headers have HCOLON that could span multiple line (but always begin at the > start of the line), but not Request-Line. > Also I noticed that in RFC 4475 (SIP Torture Test Messages), the 3.1.1.1 > message (that recalls test1.txt very much) has not spaces before the To > header. > What do you think ? > Is there any reason for that implementation ?
According RFC 2543 empty lines should be ignored, and the whitespace after first line but before first header is in some of the 2543bis drafts (which much later become RFC3261). The torture message is from around 2001. Is there a reason to be more conservative when receiving? -- Pekka.Pessi mail at nokia.com ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
