I was actually intrigued by the fact that the content length in the stream result is actually setting the content-length HTTP header [1], which from the HTTP doc it represents the "message body length", but I'm not sure that the message body length is EXACTLY the same as the attached file size.
I wonder if all that MIME descriptive data in the HTTP response is part of the "message body", and if that's the case, I suppose it is better always NOT specify any content length at all in the stream result. [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.13 2008/9/6 Dave Newton <[EMAIL PROTECTED]>: > --- On Sat, 9/6/08, Martin Gainty wrote: >> Interested to know how you can make a windows binary work >> on linux is this a shared object that has been dos-compiled? >> Do you have an alias setup to associate .exe to shell to a >> mono environment? > > If I understood the original poster correctly the binary is being streamed > *from* a Windows or Linux machine. > > Dave > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
