Re: mod_http2 and Frequent wake-ups for mpm_event

might this be a debian bug? i can't reproduce with apr-included. Am 20.01.2017 um 08:20 schrieb Yann Ylavic: > Hi, > > On Fri, Jan 20, 2017 at 8:03 AM, Stefan Priebe - Profihost AG > wrote: >> Hi Stefan, >> >> Am 19.01.2017 um 22:44 schrieb Stefan Eissing: >>> this seems

Re: svn commit: r1779578 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_http2.xml

> Am 20.01.2017 um 12:45 schrieb Luca Toscano : > > > > 2017-01-20 10:45 GMT+01:00 Stefan Eissing : > > > Am 20.01.2017 um 10:35 schrieb Luca Toscano : > > > > > > > > 2017-01-20 10:11 GMT+01:00 ste...@eissing.org

Re: mod_http2 and Frequent wake-ups for mpm_event

Will start retesting V6 patch. Should I use mod_http2 1.8.8 with or without patches? Greets, Stefan Excuse my typo sent from my mobile phone. > Am 20.01.2017 um 13:04 schrieb Stefan Eissing : > > Different apr versions? Might there have been a bugfix affecting

Re: Alternate versioning proposal: patch line releases

On 20 Jan 2017, at 2:15 AM, Jacob Champion wrote: > Ignore the versioning number then; that's not really the core of my proposal. > The key points I'm making are > > - introduce the concept of a low-risk release line We have always had this, the current low-risk release

Re: Reset out x.minor.z definition of 'minor' at httpd?

On Thu, Jan 19, 2017 at 6:05 PM, Jim Jagielski wrote: > Bill wrote: > >>I think one of our disconnects with 2.4 -> 2.6 is that in any other >>framework, there would be >> no ABI breakage in 2.6. That breakage would be deferred to and shipped as >> 3.0. > > Huh? For just one

Re: Reset out x.minor.z definition of 'minor' at httpd?

On Fri, Jan 20, 2017 at 4:04 AM, Graham Leggett wrote: > On 19 Jan 2017, at 11:43 PM, William A Rowe Jr wrote: > >> I think one of our disconnects with 2.4 -> 2.6 is that in any other >> framework, there would be no ABI breakage in 2.6. That breakage >>

Re: Reset out x.minor.z definition of 'minor' at httpd?

On Thu, Jan 19, 2017 at 6:46 PM, Eric Covener wrote: > On Thu, Jan 19, 2017 at 4:43 PM, William A Rowe Jr > wrote: >> I think one of our disconnects with 2.4 -> 2.6 is that in any other >> framework, there would be no ABI breakage in 2.6. That breakage >>

Re: Reset out x.minor.z definition of 'minor' at httpd?

On Thu, Jan 19, 2017 at 6:12 PM, David Zuelke wrote: > I don't know any framework/language/library out there that handles it that > strictly. Nginx, or Ruby, or PHP, or whatever... > > From x.y.z to x.y.z+1, retain full compatibility. > > From x.y.z to x.y+1.0, keep external API

Re: rfc7231 - content-md5

On Fri, Jan 20, 2017 at 1:21 PM, Dirk-Willem van Gulik wrote: > RFC 7231 has retired Content-MD5. > > Fair game to remove it from -trunk - or make it squeek 'debrecated' at WARN > or INFO and retire it at the next minor release ? Removing what, precisely? Content-MD5

Re: [Bug 60071] Child httpd processes crash with Segmentation fault when enabling more than 1 healthcheck

Cool! Yann, I see this as a show-stopper for 2.4.26... Do you agree? Would you like to propose this (and the 2 other commits) for backport to close this bug. Thx! > On Jan 20, 2017, at 2:21 AM, bugzi...@apache.org wrote: > > https://bz.apache.org/bugzilla/show_bug.cgi?id=60071 > > --- Comment

Re: Reset out x.minor.z definition of 'minor' at httpd?

> Am 20.01.2017 um 21:37 schrieb Graham Leggett : > > On 20 Jan 2017, at 7:47 PM, David Zuelke wrote: > >> I'd actually like to question the whole practice of porting features back to >> older branches. I think that's the core reason why trunk is in total

Re: Reset out x.minor.z definition of 'minor' at httpd?

> Am 20.01.2017 um 21:40 schrieb Jim Jagielski : > > >> On Jan 20, 2017, at 3:36 PM, Jim Jagielski wrote: >> >> >> If I really was the dictator Bill tries to insinuate that I am, >> I would simply branch 2.5 *right now* off of trunk. > > In fact, I'd

Re: rfc7231 - content-md5

> On 20 Jan 2017, at 20:49, William A Rowe Jr wrote: > > On Fri, Jan 20, 2017 at 1:21 PM, Dirk-Willem van Gulik > wrote: >> RFC 7231 has retired Content-MD5. >> >> Fair game to remove it from -trunk - or make it squeek 'debrecated' at WARN >> or

rfc7231 - content-md5

RFC 7231 has retired Content-MD5. Fair game to remove it from -trunk - or make it squeek 'debrecated' at WARN or INFO and retire it at the next minor release ? Dw.

Re: Reset out x.minor.z definition of 'minor' at httpd?

On 20 Jan 2017, at 4:29 PM, William A Rowe Jr wrote: >>> Right now, there are a number of gratuitous breaking changes on trunk >>> that change binary ABI. I'm considering a trunk fork to preserve these >>> changes (branches/3.x-future/?) and reverting every change to trunk/

Re: Reset out x.minor.z definition of 'minor' at httpd?

> On Jan 20, 2017, at 9:26 AM, William A Rowe Jr wrote: > > > Just so we are all in agreement, 2.4 has been neither conservative nor > maintenance in any conventional sense, for the past four years. Instead > we have users relying on the stable 2.2 release which we will

Re: Alternate versioning proposal: patch line releases

> On Jan 20, 2017, at 10:43 AM, Eric Covener wrote: > > On Fri, Jan 20, 2017 at 9:53 AM, William A Rowe Jr > wrote: >> Many if not most developers disagree with you, most developers agree that >> adding features and enhancements is disruptive. 2.4.x

Re: Reset out x.minor.z definition of 'minor' at httpd?

> On Jan 20, 2017, at 12:47 PM, David Zuelke wrote: > > > I'd actually like to question the whole practice of porting features back to > older branches. I think that's the core reason why trunk is in total > disarray, and why no substantial releases have been made. There is

Re: Reset out x.minor.z definition of 'minor' at httpd?

> On Jan 20, 2017, at 3:37 PM, Graham Leggett wrote: > > > We’ve had a significant amount of progress, a trunk that is so stable that > almost all fixes and features can be backported to v2.4 without any fear of > incompatibility, and the “fighting” is limited to very few

Re: Reset out x.minor.z definition of 'minor' at httpd?

> On Jan 20, 2017, at 3:36 PM, Jim Jagielski wrote: > > > If I really was the dictator Bill tries to insinuate that I am, > I would simply branch 2.5 *right now* off of trunk. In fact, I'd announce 2.5-alpha "immediately" as what's in trunk... with a set schedule that

Re: JSON for mod_status

On 01/18/2017 03:48 PM, Daniel Gruno wrote: > On 01/18/2017 03:19 PM, Luca Toscano wrote: >> >> >> 2017-01-18 10:56 GMT+01:00 Daniel Gruno > >: >> >> On 01/17/2017 07:33 PM, Jim Jagielski wrote: >> > It all depends on what Bill decides

Re: rfc7231 - content-md5

> On 20 Jan 2017, at 21:13, William A Rowe Jr wrote: > > On Fri, Jan 20, 2017 at 1:49 PM, William A Rowe Jr > wrote: >> On Fri, Jan 20, 2017 at 1:21 PM, Dirk-Willem van Gulik >> wrote: >>> RFC 7231 has retired Content-MD5. >>>

Re: svn commit: r1779525 - /httpd/httpd/trunk/modules/http2/h2_mplx.c

> On Jan 19, 2017, at 4:00 PM, Ruediger Pluem wrote: > > > > On 01/19/2017 09:38 PM, ic...@apache.org wrote: >> Author: icing >> Date: Thu Jan 19 20:38:50 2017 >> New Revision: 1779525 >> >> URL: http://svn.apache.org/viewvc?rev=1779525=rev >> Log: >> On the trunk: >> >>

Re: rfc7231 - content-md5

On Fri, Jan 20, 2017 at 1:49 PM, William A Rowe Jr wrote: > On Fri, Jan 20, 2017 at 1:21 PM, Dirk-Willem van Gulik > wrote: >> RFC 7231 has retired Content-MD5. >> >> Fair game to remove it from -trunk - or make it squeek 'debrecated' at WARN >> or

Re: Reset out x.minor.z definition of 'minor' at httpd?

On 20 Jan 2017, at 7:47 PM, David Zuelke wrote: > I'd actually like to question the whole practice of porting features back to > older branches. I think that's the core reason why trunk is in total > disarray, and why no substantial releases have been made. There is just no >

Re: rfc7231 - content-md5

On 20 Jan 2017, at 20:49, William A Rowe Jr wrote: > > Note that https://www.rfc-editor.org/rfc/rfc7616.txt still provides > for MD5 hashed > digest auth keys. So removing this altogether will break mod_auth_digest in a > manner that breaks existing user auth. > > > Note

Re: svn commit: r1779525 - /httpd/httpd/trunk/modules/http2/h2_mplx.c

> Am 20.01.2017 um 21:59 schrieb Jim Jagielski : > > >> On Jan 19, 2017, at 4:00 PM, Ruediger Pluem wrote: >> >> >> >> On 01/19/2017 09:38 PM, ic...@apache.org wrote: >>> Author: icing >>> Date: Thu Jan 19 20:38:50 2017 >>> New Revision: 1779525 >>> >>>

Re: Reset out x.minor.z definition of 'minor' at httpd?

On 20 Jan 2017, at 10:40 PM, Jim Jagielski wrote: > In fact, I'd announce 2.5-alpha "immediately" as what's > in trunk... with a set schedule that 2.6-Beta1 is tagged 2 > months later and a goal that 2.6-GA be announced at > ApacheCon Miami. > > But this all implies that

Re: Reset out x.minor.z definition of 'minor' at httpd?

On 01/20/2017 09:37 PM, Graham Leggett wrote: > On 20 Jan 2017, at 7:47 PM, David Zuelke wrote: > >> I'd actually like to question the whole practice of porting features back to >> older branches. I think that's the core reason why trunk is in total >> disarray, and why no

Re: mod_http2 and Frequent wake-ups for mpm_event

Hi, this patch solved the file_close segfault. Never saw that again. Right now i got this one: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f129f612274 in pthread_mutex_lock () from /lib/x86_64-linux-gnu/libpthread.so.0 (gdb) bt #0 0x7f129f612274 in

Re: svn commit: r1776575 - in /httpd/httpd/trunk: docs/log-message-tags/next-number docs/manual/mod/mod_remoteip.xml modules/metadata/mod_remoteip.c

First of all, http://blog.haproxy.com/haproxy/proxy-protocol/ list another module implementation for Apache: https://github.com/ggrandes/apache24-modules/blob/master/mod_myfixip.c If anyone wants to give it a look. Anyway, a few minor comments below. CJ Le 30/12/2016 à 15:20,

Re: Alternate versioning proposal: patch line releases

On Fri, Jan 20, 2017 at 8:07 AM, Graham Leggett wrote: > On 20 Jan 2017, at 2:15 AM, Jacob Champion wrote: > >> Ignore the versioning number then; that's not really the core of my >> proposal. The key points I'm making are >> >> - introduce the concept of

Re: Alternate versioning proposal: patch line releases

On Thu, Jan 19, 2017 at 5:49 PM, Jacob Champion wrote: > This is somewhat orthogonal to Bill's current suggestion. It solves a > different set of problems, more related to the short-term > features-versus-regressions argument and less related to the long-term ABI >

Re: Alternate versioning proposal: patch line releases

On Fri, Jan 20, 2017 at 9:53 AM, William A Rowe Jr wrote: > Many if not most developers disagree with you, most developers agree that > adding features and enhancements is disruptive. 2.4.x adds features and > enhancements to every release, and is therefore not low-risk, and

Re: mod_http2 and Frequent wake-ups for mpm_event

Hi, it crashed again with V6 and plain mod_http2 v1.8.8. This is the crash incl. line numbers: Program terminated with signal SIGSEGV, Segmentation fault. #0 apr_pool_cleanup_kill (p=0x2d392d322d32, data=data@entry=0x7f330006bc70, cleanup_fn=cleanup_fn@entry=0x7f33155b0f90 ) at

Re: svn commit: r1779578 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_http2.xml

2017-01-20 10:45 GMT+01:00 Stefan Eissing : > > > Am 20.01.2017 um 10:35 schrieb Luca Toscano : > > > > > > > > 2017-01-20 10:11 GMT+01:00 ste...@eissing.org : > > > > > Am 20.01.2017 um 09:45 schrieb elu...@apache.org: > >

Re: mod_http2 and Frequent wake-ups for mpm_event

Different apr versions? Might there have been a bugfix affecting us? > Am 20.01.2017 um 12:49 schrieb Stefan Priebe - Profihost AG > : > > might this be a debian bug? i can't reproduce with apr-included. > > Am 20.01.2017 um 08:20 schrieb Yann Ylavic: >> Hi, >> >> On

Re: mod_http2 and Frequent wake-ups for mpm_event

Please without. Then I least know if that version behaves. Planning on more extensive changes for a 1.9.0 now. Thanks! -Stefan > Am 20.01.2017 um 13:18 schrieb Stefan Priebe - Profihost AG > : > > Will start retesting V6 patch. Should I use mod_http2 1.8.8 with or

Re: mod_http2 and Frequent wake-ups for mpm_event

On Fri, Jan 20, 2017 at 12:49 PM, Stefan Priebe - Profihost AG wrote: > might this be a debian bug? i can't reproduce with apr-included. Did you build the included-apr (and httpd) with -fno-strict-aliasing ? Not sure Debian sets it for its builds either, just a speculation

Re: mod_http2 and Frequent wake-ups for mpm_event

Please use V7 too, I don't think I'll revert it in trunk (it makes sense). On Fri, Jan 20, 2017 at 1:20 PM, Stefan Eissing wrote: > Please without. Then I least know if that version behaves. Planning on more > extensive changes for a 1.9.0 now. Thanks! > > -Stefan

Re: Reset out x.minor.z definition of 'minor' at httpd?

On 19 Jan 2017, at 11:43 PM, William A Rowe Jr wrote: > I think one of our disconnects with 2.4 -> 2.6 is that in any other > framework, there would be no ABI breakage in 2.6. That breakage > would be deferred to and shipped as 3.0. > > The httpd project choose to call

Re: mod_http2 and Frequent wake-ups for mpm_event

On Fri, Jan 20, 2017 at 5:51 PM, Stefan Priebe - Profihost AG wrote: > Yes. Until now I got 4 traces. But all are the same pointing to apr kill > pool. Not like before where i got many different ones. Could you try this new patch on mod_http2 please? Thanks, Yann. Index:

Re: Alternate versioning proposal: patch line releases

On Fri, Jan 20, 2017 at 9:43 AM, Eric Covener wrote: > > Maybe a [POLL] thread is in order, specifically for the topic of > enhancements/stability in 2.4 and ignoring aspirations about a new > versioning system or 3.0. > > e.g. > > 2.4.x is: > [ ] evolving just fine > [ ] too

Re: Alternate versioning proposal: patch line releases

On Fri, Jan 20, 2017 at 5:27 PM, William A Rowe Jr wrote: > On Fri, Jan 20, 2017 at 9:43 AM, Eric Covener wrote: >> >> Maybe a [POLL] thread is in order, specifically for the topic of >> enhancements/stability in 2.4 and ignoring aspirations about a new >>

Re: mod_http2 and Frequent wake-ups for mpm_event

Yes. Until now I got 4 traces. But all are the same pointing to apr kill pool. Not like before where i got many different ones. Greets, Stefan Excuse my typo sent from my mobile phone. > Am 20.01.2017 um 17:44 schrieb Yann Ylavic : > > On Fri, Jan 20, 2017 at 5:41 PM,

Re: mod_http2 and Frequent wake-ups for mpm_event

On Fri, Jan 20, 2017 at 5:41 PM, Stefan Priebe - Profihost AG wrote: > Sorry misstyped it's V7 with mod_http 1.8.8 unpatched. Unpatched but still compiled with -fno-strict-aliasing (along with APR)? Thanks, Yann.

Re: mod_http2 and Frequent wake-ups for mpm_event

Sorry misstyped it's V7 with mod_http 1.8.8 unpatched. Stefan Excuse my typo sent from my mobile phone. > Am 20.01.2017 um 16:23 schrieb Stefan Priebe - Profihost AG > : > > Hi, > > it crashed again with V6 and plain mod_http2 v1.8.8. > > This is the crash incl. line

Re: Reset out x.minor.z definition of 'minor' at httpd?

> On 20.01.2017, at 15:34, William A Rowe Jr wrote: > > On Thu, Jan 19, 2017 at 6:12 PM, David Zuelke wrote: >> I don't know any framework/language/library out there that handles it that >> strictly. Nginx, or Ruby, or PHP, or whatever... >> >> From

Re: mod_http2 and Frequent wake-ups for mpm_event

Good catch, Yann. I have local modifications that throw most of the manual cleanup out and rely on auto pool cleanup as much as possible. Curious if that will solve Stefan's crashes. > Am 20.01.2017 um 18:17 schrieb Yann Ylavic : > > On Fri, Jan 20, 2017 at 5:51 PM,

Re: Reset out x.minor.z definition of 'minor' at httpd?

On Fri, Jan 20, 2017 at 12:47 PM, David Zuelke wrote: > I'd actually like to question the whole practice of porting features back to > older branches. I think that's the core reason why trunk is in total > disarray, and why no substantial releases have been made. There is just

Re: mod_http2 and Frequent wake-ups for mpm_event

Am 20.01.2017 um 18:17 schrieb Yann Ylavic: > On Fri, Jan 20, 2017 at 5:51 PM, Stefan Priebe - Profihost AG > wrote: >> Yes. Until now I got 4 traces. But all are the same pointing to apr kill >> pool. Not like before where i got many different ones. > > Could you try

Re: Reset out x.minor.z definition of 'minor' at httpd?

> Am 20.01.2017 um 01:46 schrieb Eric Covener : > > On Thu, Jan 19, 2017 at 4:43 PM, William A Rowe Jr > wrote: >> I think one of our disconnects with 2.4 -> 2.6 is that in any other >> framework, there would be no ABI breakage in 2.6. That breakage >>

Re: svn commit: r1779578 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_http2.xml

2017-01-20 10:11 GMT+01:00 ste...@eissing.org : > > > Am 20.01.2017 um 09:45 schrieb elu...@apache.org: > > > > Author: elukey > > Date: Fri Jan 20 08:45:40 2017 > > New Revision: 1779578 > > > > URL: http://svn.apache.org/viewvc?rev=1779578=rev > > Log: > > Added more details

Re: svn commit: r1779578 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_http2.xml

> Am 20.01.2017 um 09:45 schrieb elu...@apache.org: > > Author: elukey > Date: Fri Jan 20 08:45:40 2017 > New Revision: 1779578 > > URL: http://svn.apache.org/viewvc?rev=1779578=rev > Log: > Added more details to mod-proxy-http2's doc > > Modified: >

Re: svn commit: r1779578 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_http2.xml

> Am 20.01.2017 um 10:35 schrieb Luca Toscano : > > > > 2017-01-20 10:11 GMT+01:00 ste...@eissing.org : > > > Am 20.01.2017 um 09:45 schrieb elu...@apache.org: > > > > Author: elukey > > Date: Fri Jan 20 08:45:40 2017 > > New Revision: 1779578 > > >