> Please don't top-post.
Sorry.

> There are a lot more stuff you can do. For example firing up a debugger,
> set a few break-points in the lib and trying to figure out why you get
what you get.
I did try that but couldn't see anything other than the
Curl_pgrsSetUploadCounter (in transfer.c) wasn't being called on smaller
posts except for the first one which sets/initialises it to 0, but on larger
posts it gets called multiple times.

> And my example should be very easy to get to build and try on windows too.
I will give it a go when I get a moment.

> Decreasing the internal buffer size with CURLOPT_BUFFERSIZE is also a
> kind of work-around for it too.
I just tried that and it didn't make any difference.

However, I did some narrowing down and a post with 102380 bytes produces a
progress "0 of 0", but a post with 102381 bytes produces some progress
results ... so it would be interesting to know if this is a Windows specific
issue or can others reproduce it on other platforms.

Dan
Received on 2008-03-15