On Wed, Feb 3, 2016 at 11:53 AM, Plüm, Rüdiger, Vodafone Group <[email protected]> wrote: > >> -----Original Message----- >> From: Yann Ylavic [mailto:[email protected]] >> Sent: Mittwoch, 3. Februar 2016 11:41 >> To: httpd-dev >> Subject: Re: HTTPS connections lock-up with 2.4.18 >> >> On Wed, Feb 3, 2016 at 11:29 AM, Plüm, Rüdiger, Vodafone Group >> <[email protected]> wrote: >> > Which MPM is used? Event or something different? >> > There a differences on how c->data_in_input_filters is handled by >> different MPM's. >> > On sync MPM's like worker there is an explicit flush if c- >> >data_in_input_filters is zero, >> > the event MPM though only relies on WRITE_COMPLETION. >> >> Hmm, ap_process_request() really checks for c->data_in_input_filters >> to determine whether it should flush or not. >> So I don't see it depending on the MPM. > > It does, because ap_process_request is only called by sync MPMs. > Event calls ap_process_async_request only. See ap_process_http_connection in > http_core.c
Oh right, sorry, I completely misread your message and thought you were saying that sync MPMs do flush unconditionally :/ But still event should (try to) flush pending data when in WRITE_COMPLETION while c->data_in_output_filters (calling the core_output_filter() with NULL brigade). So I don't see why the response is not flushed on the network before entering READ_REQUEST_LINE or CHECK_REQUEST_LINE_READABLE states. Regards, Yann.
