On Sat, Mar 28, 2020 at 11:24 AM Graham Leggett wrote:
>
> On 27 Mar 2020, at 14:01, Yann Ylavic wrote:
>
> >> We need to find the reason that in a non-async case, data is being
> >> setaside, and we need to fix it.
> >
> > Connection and network output filters shouldn't care about async or
> >
On 3/26/2020 7:50 AM, Daniel Ruggeri wrote:
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this
candidate tarball as 2.4.43:
[X] +1: It's not just good, it's
On Thu, Mar 26, 2020 at 10:50 AM Daniel Ruggeri wrote:
>
> Hi, all;
>Please find below the proposed release tarball and signatures:
> https://dist.apache.org/repos/dist/dev/httpd/
>
> I would like to call a VOTE over the next few days to release this
> candidate tarball as 2.4.43:
> [ ] +1:
Le 26/03/2020 à 15:50, Daniel Ruggeri a écrit :
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this
candidate tarball as 2.4.43:
[X] +1: It's not just good,
On 27 Mar 2020, at 14:01, Yann Ylavic wrote:
>> We need to find the reason that in a non-async case, data is being setaside,
>> and we need to fix it.
>
> Connection and network output filters shouldn't care about async or
> not, they just feed the pipe as much as possible, and setaside what
>
