Re: Forwarded buckets' lifetime (was: [Bug 58503] segfault in apr_brigade_cleanup()...)

2015-10-20 Thread Yann Ylavic
On Tue, Oct 20, 2015 at 10:42 AM, Stefan Eissing wrote: > >> Am 20.10.2015 um 09:44 schrieb Plüm, Rüdiger, Vodafone Group >> : >> >>> -Original Message- >>> From: Yann Ylavic [mailto:ylavic@gmail.com] >>> Sent: Montag, 19.

Re: Forwarded buckets' lifetime (was: [Bug 58503] segfault in apr_brigade_cleanup()...)

2015-10-20 Thread Stefan Eissing
> Am 20.10.2015 um 09:44 schrieb Plüm, Rüdiger, Vodafone Group > : > > > >> -Original Message- >> From: Yann Ylavic [mailto:ylavic@gmail.com] >> Sent: Montag, 19. Oktober 2015 22:30 >> To: dev@httpd.apache.org >> Subject: Fwd: Forwarded buckets'

Re: Forwarded buckets' lifetime (was: [Bug 58503] segfault in apr_brigade_cleanup()...)

2015-10-20 Thread Stefan Eissing
Let's do this. I will review and think about changes from the h2 angle... > Am 20.10.2015 um 11:24 schrieb Yann Ylavic : > > On Tue, Oct 20, 2015 at 10:42 AM, Stefan Eissing > wrote: >> >>> Am 20.10.2015 um 09:44 schrieb Plüm, Rüdiger,

Re: Forwarded buckets' lifetime (was: [Bug 58503] segfault in apr_brigade_cleanup()...)

2015-10-20 Thread Graham Leggett
On 20 Oct 2015, at 10:42 AM, Stefan Eissing wrote: >> So if at all a change for trunk only that requires a very deep review of all >> brigade usages. > > As I learned, bucket brigades are very optimized for the common HTTP/1 case: > appearing during one >

RE: Forwarded buckets' lifetime (was: [Bug 58503] segfault in apr_brigade_cleanup()...)

2015-10-20 Thread Plüm , Rüdiger , Vodafone Group
> -Original Message- > From: Yann Ylavic [mailto:ylavic@gmail.com] > Sent: Montag, 19. Oktober 2015 22:30 > To: dev@httpd.apache.org > Subject: Fwd: Forwarded buckets' lifetime (was: [Bug 58503] segfault in > apr_brigade_cleanup()...) > > [Meant for dev@...] > > Thoughts? > > >

Re: Forwarded buckets' lifetime (was: [Bug 58503] segfault in apr_brigade_cleanup()...)

2015-10-20 Thread Jim Jagielski
Sorry for not being on-list a bit lately... I've been a bit swamped. Anyway, I too don't want httpd to go down the 'systemd' route: claim something as broken to explain, and justify, ripping it out and re-creating anew. Sometimes this needs be done, but not very often. And when stuff *is* broken,