[Bug 66537] large request serving times logged since upgrade to 2.4.56

2023-05-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66537 --- Comment #6 from Teodor Milkov --- With changes from https://github.com/icing/mod_h2/pull/254 logging is working as expected for me. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 60681] Increase severity of "request failed: error reading the headers"

2023-05-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60681 --- Comment #21 from alishakihn --- You have to tap the screen so that the bird flaps its wings, trying to keep a steady rhythm in order to pass through the pipes scattered through its path. https://flappy-bird.io -- You are receiving this

[Bug 66597] HTTP/2 chunk requests conflict with proxy-sendcl option in mod_proxy_fcgi

2023-05-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66597 --- Comment #9 from Yann Ylavic --- Sorry this patch is broken. I tried to reproduce (with httpd-2.4.57) but couldn't. Using HTTP/1 or HTTP/2, with or without proxy-sendcl, the body is never sent "chunked" to the fcgi server (I'm using

[Bug 66597] HTTP/2 chunk requests conflict with proxy-sendcl option in mod_proxy_fcgi

2023-05-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66597 --- Comment #8 from dreamt_catsup403 --- tested the 2nd attachment, got a seg fault: [Tue May 16 14:30:54.129226 2023] [core:notice] [pid 1561030:tid 140704993326976] AH00052: child pid 1564094 exit signal Segmentation fault (11) [Tue May 16

[Bug 66601] coredump at apr_pool_destroy in mod

2023-05-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66601 --- Comment #6 from Ruediger Pluem --- (In reply to chengyechun1 from comment #3) > (In reply to Ruediger Pluem from comment #2) > > The pool should not be NULL here and just checking for NULL would probably > > hide the underlying bug. It

[Bug 66601] coredump at apr_pool_destroy in mod

2023-05-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66601 --- Comment #5 from chengyech...@huawei.com --- Created attachment 38558 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38558=edit debug info -- You are receiving this mail because: You are the assignee for the bug.

[Bug 66601] coredump at apr_pool_destroy in mod

2023-05-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66601 --- Comment #4 from Yann Ylavic --- Could you please post the content of: (gdb) thread apply all bt ? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 66601] coredump at apr_pool_destroy in mod

2023-05-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66601 --- Comment #3 from chengyech...@huawei.com --- (In reply to Ruediger Pluem from comment #2) > The pool should not be NULL here and just checking for NULL would probably > hide the underlying bug. It looks like that the pool was already

[Bug 66601] coredump at apr_pool_destroy in mod

2023-05-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66601 --- Comment #2 from Ruediger Pluem --- The pool should not be NULL here and just checking for NULL would probably hide the underlying bug. It looks like that the pool was already destroyed before. -- You are receiving this mail because: You

[Bug 66601] coredump at apr_pool_destroy in mod

2023-05-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66601 --- Comment #1 from Ruediger Pluem --- Can you reproduce the issue? Can you provide the error logfile at best at level debug? -- You are receiving this mail because: You are the assignee for the bug.