On Thu, Jun 2, 2022 at 4:17 PM Ruediger Pluem <rpl...@apache.org> wrote: > > > > On 6/2/22 10:15 PM, Ruediger Pluem wrote: > > > > > > On 6/2/22 6:54 PM, Yann Ylavic wrote: > >> On Thu, Jun 2, 2022 at 1:04 PM <rpl...@apache.org> wrote: > >>> > >>> Author: rpluem > >>> Date: Thu Jun 2 11:04:13 2022 > >>> New Revision: 1901554 > >>> > >>> URL: http://svn.apache.org/viewvc?rev=1901554&view=rev > >>> Log: > >>> * Test returns 200, but content is !!!ERROR!!! > >> > >> On my machine it returns 400 (hitting the mem limit) with html content.. > > > > This is quite strange. On mine it does not and this is also what reading > > the code of echo_post_handler > > in c-modules/echo_post/mod_echo_post.c tells me as ap_get_client_block > > fails. > > Error messages: > > [Thu Jun 02 22:00:57.445702 2022] [sed:error] [pid 253311:tid > 139929220736768] (12)Cannot allocate memory: [client > 127.0.0.1:47366] AH10395: error evaluating sed on input > [Thu Jun 02 22:00:57.445714 2022] [:debug] [pid 253311:tid 139929220736768] > mod_echo_post.c(85): [client 127.0.0.1:47366] > [mod_echo_post] ap_get_client_block got error > [Thu Jun 02 22:00:57.445715 2022] [:debug] [pid 253311:tid 139929220736768] > mod_echo_post.c(96): [client 127.0.0.1:47366] > [mod_echo_post] done reading 0 bytes, 12582912 bytes remain
Sorry for the headache. I think ap_get_client_block() is not expected to fail here. Maybe it's some perl issue. The sed line limit is what should make this test give up, not a generic body limit. I think we should just comment it out.
