On Mon, 31 Mar 2014, Xavi Artigas wrote:

> Now I have a report from our client, saying that sometimes it receives
> corrupted data. He recently updated to libCurl 7.32, and I can reproduce
> the issue, using libCurl 7.36.
>
> I found out that a major revamp of the pipelining code in libCurl was made
> in 7.30, so the numbers seem to fit. But given the effort that libCurl puts
> in maintaining a stable API and ABI, it seems strange.

Why is that strange? We rewrite internals and (try to) maintain API and ABI.
The promise to the world is in the backards compatible ABI and API, not that
we don't rewrite code.

Obviously we introduce bugs every now and then when we modify code but they
are bugs and we should hunt them down and exterminate them!

> So, anyone has any idea I can try?

Well, to start with to reproduce the problem with an as small source code as
possible against a public server and then show that code to us. It is hard for
us to help out fixing a problem we cannot reproduce. And we do have pipelining
test cases in the test suite that work fine - albeit not terribly many.

Then, a more detailed description with lots of details of exactly what goes
wrong would be helpful.

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html