On Wed, 17 Jan 2007, Jason Pump wrote:

> An alternative path, which seems to be working but probably shouldn't, is to
> simply open ANOTHER file with fmemopen pointing at the same buffer, but
> specify the precise size of the jpeg. This works, but curl still reports
> error code 18, even though the uploaded file is precisely the same size as
> the encoded jpeg data, and appears to be correct.
>
> I think this should work, and should not return 18. Maybe there's an
> off-by-one error somewhere?

It sounds weird. Are you *sure* that off-by-one is really within libcurl and
not in the app end? There are a few users of libcurl already, and some of them
do in fact use uploads and none has reported this problem.

Not to mention that we have a test suite too that tests uploads.

But of course, it might be a bug lurking in there.

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