|Anonymous | Login | Signup for a new account||2022-09-26 21:16 EEST|
|Main | My View | View Issues | Change Log | Roadmap | Docs|
|Viewing Issue Simple Details|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0000283||[Yate - Yet Another Telephony Engine] engine||major||always||2011-12-20 15:30||2012-01-05 11:58|
|Summary||0000283: Mime multipart boundary problem|
I am testing yate SIP features and in Mime parser I have found an error.
When message type is multipart/mixed in our cases is not correctly parsed
and first part of message is skipped and only parts behind it are put into message structures.
For example when yate recieved message with application/sdp and application/ISUP
parts, yate forwards message only with application/ISUP part.
It seems that this issue is an example of this problem
The problem is in function MimeMultipartBody::findBoundary in file
Variable boundary includes \r\n at begining (first two bytes).
But when is searchend first boundary in mime message, buffer with
message body does not have \r\n at beginig, so boundary not match
and all data from first part are skipped.
|Tags||No tags attached.|
|Attached Files||mime-fix.diff [^] (843 bytes) 2011-12-20 15:30|
Fixed in SVN Rev. 4793.
Patch not applied: it would accept subsequent boundary without CR/LF (not starting at new line) which is not correct.
|Thank you. Everything works fine.|
|Fix from SVN Rev. 4793 works.|
|2011-12-20 15:30||lojza||New Issue|
|2011-12-20 15:30||lojza||File Added: mime-fix.diff|
|2011-12-22 15:03||paulc||Assigned To||=> marian|
|2011-12-22 15:03||paulc||Status||new => acknowledged|
|2011-12-22 15:24||paulc||Relationship added||related to 0000279|
|2012-01-05 10:41||marian||Note Added: 0000400|
|2012-01-05 10:41||marian||Status||acknowledged => feedback|
|2012-01-05 11:18||cdmaua||Note Added: 0000402|
|2012-01-05 11:58||lojza||Note Added: 0000403|
|Copyright © 2000 - 2008 Mantis Group|