On Thu, 19 May 2005, bart wrote:

> One of the options I have when submiting the post to request the file is to
> have it returned as a file or on screen. When I select to have it on screen
> it all works correctly, when i select return a file curl never gives me the
> file.

Eh, let's not confuse terms here. curl gives you everything the server
responds with. So if you don't get the file you want, it isn't curl that hides
anything from you, it is the server.

> I have check live httpheaders and --trace and they match perfectly. I
> believe there is something wrong with how curls dealing with
>
> 0000: Content-disposition: inline; filename=CaseFiledRPT.txt
> 0000: Transfer-Encoding: chunked
> 0000: Content-Type: application/binary; name=CaseFiledRPT.txt

What makes you say that? And if so, in what way would curl do it wrong? Or
even, if you got to decide, what would you like curl to do with these?

> I have now also tried with the most recent version of curl with the same
> result.

I think you are focusing too much on the headers, while the magic you want is
much more likely to be in the body of the response.

The headers are the same you say, then the explantion to the mismatch is
likely not in there.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html