Unable to send NUL frame to the remote peer when automatic MIME header addition is turned off

[GoogleCodeExporter]

What steps will reproduce the problem?
- I disabled automatic MIME header addition using the API
"vortex_profiles_set_automatic_mime". Now I am not able to send NUL frame to 
the remote peer.

What is the expected output? What do you see instead?
- Application should be able to send NUL frames when automatic MIME header 
addition is disabled. But currently the application crashes. Please find more 
information below in the last section.

What version of the product are you using? On what operating system?
- I am using Vortex 1.1.8 on Win32 platform

Please provide any additional information below.

I debugged vortex code to find the reason. Here is what I found out.
I invoke "vortex_channel_finalize_ans_rpy" API that internally invokes
"__vortex_channel_common_rpy" with message size as zero, message as NULL and 
feeder also as NULL. Because automatic MIME header addition is disabled the 
following condition in "__vortex_channel_common_rpy" function fails.
"if (feeder == NULL && (message != NULL || data->message_size > 0))"
So it enters the ELSE where it finds that feeder is NULL. Hence the
application crashes.

Thanks
Subrahmanya

Original issue reported on code.google.com by sum.sa...@gmail.com on 28 Jun 2011 at 12:19

[GoogleCodeExporter]

Hi Subrahmanya,

I've disabled issue tracking because we handle bug reporting at 
http://bugzilla.aspl.es

Sorry for the inconvenience. Please, fill a bug report there. Bug body 
definition is perfect. 

Regards,

Original comment by francis....@gmail.com on 28 Jun 2011 at 6:29