Multipart module bug? Lack of \r\n within the "multipart_print_body" function

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Benny,

I'm working with multiparts and I might found a bug in the multipart module.
I am using PJSIP version 1.10.

The function "multipart_print_body" of the "pjsip/src/pjsip/sip_multipart.c"
file does not print well the optional headers contained in the "pjsip_hdr
*hdr" variable.

This is the patch :
--- sip_multipart.c.original 2011-10-11 07:00:48.210547786 -0900
+++ sip_multipart.c.modified 2011-10-11 07:00:21.946540744 -0900
@@ -86,6 +86,8 @@
  return -1;
     p += printed;
     hdr = hdr->next;
+    *p++ = '\r';
+    *p++ = '\n';
  }

  /* Automaticly adds Content-Type and Content-Length headers, only


Checking the SIP Message multipart body,
Before the patch:
Encapsulated multipart part:
Content-ID: this-is-my-content-idContent-Type: application/xml\r\n
 Content-Length:   937\r\n\r\n
Data (937 bytes)

After the path:
Encapsulated multipart part:  (application/xml)
Content-ID: this-is-my-content-id\r\n
Content-Type: application/pxml\r\n
 Content-Length:   937\r\n\r\n


Hope I am right.

Best,
Luis Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20111011/f9899007/attachment.html>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux