On 3/23/20 1:49 AM, Graham Leggett wrote:
> On 06 Mar 2020, at 10:30, Ruediger Pluem <rpl...@apache.org> wrote:
>
>> Anyone found time to check
>>
>> https://github.com/apache/httpd/pull/88
>>
>> regarding the async filter bug?
>
> Do these PRs come through on a mailing list anywhere? If there is no
> notification, they’ll never get seen.
>
> I immediately trip over "Ensure that we always pass on all we have” - that’s
> the exact opposite of what we’re trying to do.
>
> All the async filter stuff is, is generalising the algorithm that has long
> existing in the core network filter, allowing any filter to take advantage of
> the same pattern.
>
> As soon as we try “pass all we have”, that would break the event MPM, which
> relies on small writes in turn to work.
>
> Can you explain the problem you’re trying to solve?
>
In short: The async filter code currently corrupts responses in certain
situations. For the whole story please look here:
https://lists.apache.org/thread.html/r94fc303b3d2d8d0a057c150cbbcf8841b313e4de9a97b79203ac62a5%40%3Cdev.httpd.apache.org%3E
I know that my proposal is not the final solution, but at least it avoids
response corruption until a better solution is
available. Maybe Yann already has a better one in his latest post to the
original thread.
Regards
Rüdiger
