Hi Mladen,
I don't full yunderstand this fix. From your other mail i though it's a
regression, but the code in this region is the same at least since
1.2.18 (more than a year). So I have the impression, that this is not a
regression. If so, I would prefer to not push 1.2.25 through with very
Rainer Jung wrote:
Hi Mladen,
I don't full yunderstand this fix. From your other mail i though it's a
regression, but the code in this region is the same at least since
1.2.18 (more than a year). So I have the impression, that this is not a
regression.
You can try 1.2.23 (it works). 1.2.24
OK, I'll go into it. I think I would propose a slightly different patch,
but I'll investigate, why 23 and 24 are different.
The reason why I started to pose querstions is, that I found it a little
strange to make an exception for exactly one status code.
My impression is: the code was
Rainer Jung wrote:
OK, I'll go into it. I think I would propose a slightly different patch,
but I'll investigate, why 23 and 24 are different.
The reason why I started to pose querstions is, that I found it a little
strange to make an exception for exactly one status code.
My impression is:
Update: The problem seems to be coming from a global change of AS400
defines, which unintentionally also hit two ifndefs, which were
transformed into ifdefs. As a result, we didn't flush any more, so small
responses were not flushed before we came to the line checking
sent_bodyct. That way the
