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
--- 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 bin
contained within this transmission.
> Date: Fri, 5 Sep 2008 13:52:31 -0300
> From: [EMAIL PROTECTED]
> To: user@struts.apache.org
> Subject: Re: Stream Windows Executable From Linux Machine
>
> Interesting.
> Never used myself the contentLength parameter before.
>
ist
> Subject: Re: Stream Windows Executable From Linux Machine
>
> filename= setup.exe
> is there an space there? (try removing it)
>
> what you mean by corrupt?
>
> 2008/9/5, Geffrey Caruso <[EMAIL PROTECTED]>:
> > Quick question for anyone who's tried this bef
Subject: Re: Stream Windows Executable From Linux Machine
filename= setup.exe
is there an space there? (try removing it)
what you mean by corrupt?
2008/9/5, Geffrey Caruso <[EMAIL PROTECTED]>:
> Quick question for anyone who's tried this before.
>
>
>
> I've got a w
filename= setup.exe
is there an space there? (try removing it)
what you mean by corrupt?
2008/9/5, Geffrey Caruso <[EMAIL PROTECTED]>:
> Quick question for anyone who's tried this before.
>
>
>
> I've got a windows executable created using NSIS from a wrapped jar file.
>
>
>
> I've got the follow
6 matches
Mail list logo
