Re: Redis and mod_cache/mod_socache

Interesting. Thx! > On Nov 2, 2016, at 5:36 AM, Mario Brandt <jbl...@gmail.com> wrote: > > Hi, > > there is already a working module. Works on Linux and Windows. > https://github.com/photom/mod_socache_redis > You may wana check it out. > > On 31 Octobe

Re: Redis and mod_cache/mod_socache

The current work-in-progress, not yet APR-ized is at: https://github.com/jimjag/credis > On Oct 31, 2016, at 11:49 AM, Graham Leggett <minf...@sharp.fm> wrote: > > On 31 Oct 2016, at 5:05 PM, Jim Jagielski <j...@jagunet.com> wrote: > >> Moving to APR: >>

Re: Redis and mod_cache/mod_socache

it. > On Oct 31, 2016, at 10:15 AM, Graham Leggett <minf...@sharp.fm> wrote: > > On 31 Oct 2016, at 3:43 PM, Jim Jagielski <j...@jagunet.com> wrote: > >> It would, but that would mean even more of a APR dependency >> and a wait until the next release of APR an

Re: Redis and mod_cache/mod_socache

It would, but that would mean even more of a APR dependency and a wait until the next release of APR and etc, etc, etc... Basically, APR moves too slow for httpd. > On Oct 31, 2016, at 9:34 AM, Graham Leggett <minf...@sharp.fm> wrote: > > On 31 Oct 2016, at 3:30 PM, J

Redis and mod_cache/mod_socache

Query: Think it would be worth my time to work on a Redis implementation for mod_cache/mod_socache? I am working on a minimal Redis lib, related to work, which is basically a soft reboot of Credis from GoogleCode, which could serve as the core functionality, which is what got me thinking about it.

Re: Cache sync

Proposed in STATUS... > On Oct 21, 2016, at 11:33 AM, Jim Jagielski <j...@jagunet.com> wrote: > > I'd like to sync-up the various improvement of mod_cache (et.al.) > found in trunk to 2.4... Any issues before I start on a comprehensive > patchset?

Cache sync

I'd like to sync-up the various improvement of mod_cache (et.al.) found in trunk to 2.4... Any issues before I start on a comprehensive patchset?

Re: [PATCH] Introducing mod_brotli

Ahh... that's... interesting. > On Oct 19, 2016, at 8:37 PM, Jacob Champion wrote: > > On 09/16/2016 05:32 AM, Evgeny Kotkov wrote: >> This patch adds a module for dynamic Brotli (RFC 7932) compression in httpd. > > Just in case someone else runs into this: I gave

Using memcached w/ socache

Before I start digging into the code to try to figure this out, has anyone use the memcache socache module to use memcached as the backend storage for mod_cache? I'm trying to figure out exactly *how* to configure this... I'm guessing it's something like CacheEnable socache CacheSocache

Re: headers.t error on 2.4 HEAD

Anyone...? Any ideas?? > On Oct 11, 2016, at 12:34 PM, Jim Jagielski <j...@jagunet.com> wrote: > > On HEAD of httpd-2.4, the test framework fails on headers.t: > > header: [FooBar] vs [Foo Bar] > # testing : compare header Hello value > # expected: 'Fo

headers.t error on 2.4 HEAD

On HEAD of httpd-2.4, the test framework fails on headers.t: header: [Foo Bar] vs [Foo Bar] # testing : compare header Hello value # expected: 'Foo Bar' # received: 'Foo Bar' not ok 3 I am guessing that this is due to the header work being in some sort of intermediate state of

Re: Loads of dup symbols in h2_util.c and h2_proxy_util.c

Bringo! https://www.youtube.com/watch?v=4MpyHBoiTwk > On Oct 11, 2016, at 10:35 AM, Stefan Eissing <stefan.eiss...@greenbytes.de> > wrote: > > Fixed (hopefully ;-) > > -Stefan > >> Am 11.10.2016 um 15:59 schrieb Jim Jagielski <j...@jagunet.c

Re: Loads of dup symbols in h2_util.c and h2_proxy_util.c

t; Changed. If you could verify that current trunk + 2.4.x do not have this > issue any more, that'd be nice. > > -Stefan > >> Am 11.10.2016 um 15:13 schrieb Jim Jagielski <j...@jagunet.com>: >> >> ... and on trunk too it seems... >>> On Oct 11, 2016, at 9

Re: Loads of dup symbols in h2_util.c and h2_proxy_util.c

... and on trunk too it seems... > On Oct 11, 2016, at 9:05 AM, Jim Jagielski <j...@jagunet.com> wrote: > > Forgot to mention: This is on HEAD httpd-2.4 > >> On Oct 11, 2016, at 8:50 AM, Jim Jagielski <j...@jagunet.com> wrote: >> >> There are a b

Re: Loads of dup symbols in h2_util.c and h2_proxy_util.c

Forgot to mention: This is on HEAD httpd-2.4 > On Oct 11, 2016, at 8:50 AM, Jim Jagielski <j...@jagunet.com> wrote: > > There are a bunch of dup symbols popping up during link; these > symbols exist in both h2_util.c and h2_proxy_util.c. > > Note: this is AFTER ensuring a 'make extraclean'...

Loads of dup symbols in h2_util.c and h2_proxy_util.c

There are a bunch of dup symbols popping up during link; these symbols exist in both h2_util.c and h2_proxy_util.c. Note: this is AFTER ensuring a 'make extraclean'...

Re: 2.4.24 soon?

I'm thinking of a T around the last week of Oct...

Re: mod_macro: Control on bad nesting

'bool' ?? > On Oct 5, 2016, at 8:50 AM, Nick Gearls wrote: > > The proposed patch > (https://bz.apache.org/bugzilla/attachment.cgi?id=34012=diff) is fully > back-ward compatible and can save a lot of useless warnings in the log. > Anyway to get somebody review it? > >

Re: 2.4.24 soon?

I'd like to see us work on having a 2.4.24 out sometime this month... Can we spend some time on existing backports and seeing what of usefulness in trunk *can and should* be backported to 2.4? Thx!! > On Sep 19, 2016, at 11:36 AM, Jim Jagielski <j...@jagunet.com> wrote: > > &g

Re: 2.4.24 soon?

> On Aug 2, 2016, at 2:59 PM, Jacob Champion wrote: > > On 08/02/2016 11:12 AM, William A Rowe Jr wrote: >> One additional thought... On 2.2 and 2.4 I see this change as entirely >> opt-in, no disruption to a user performing a subversion upgrade. On >> 2.6/3.0 I'd want us

Re: [PATCH] Introducing mod_brotli

Wow! This is great stuff. Brotli support has been in my TODO queue for awhile. Thanks! > On Sep 16, 2016, at 8:32 AM, Evgeny Kotkov > wrote: > > Hi all, > > This patch adds a module for dynamic Brotli (RFC 7932) compression in httpd. > > The new compression

Re: httpd and letsencrypt

Also, and this is personal, I don't tend to "trust" entities with non-public membership: https://github.com/orgs/letsencrypt/people > On Aug 29, 2016, at 3:49 PM, Jim Jagielski <j...@jagunet.com> wrote: > > Key, of course (no pun intended) is a client impl with a

Re: httpd and letsencrypt

Key, of course (no pun intended) is a client impl with a suitable and acceptable license. There is https://kristaps.bsd.lv/letskencrypt/, but last I looked it required, iirc, LibreSSL as well as it still being somewhat instable. I am hoping we can get pointers to alternatives :) > On Aug 29,

Re: Backporting HttpProtocolOptions survey

+1 > On Aug 26, 2016, at 7:10 AM, Ruediger Pluem wrote: > > > Debug > > We should ban it unequivocally. > > Only a single toggle. > > Default should be strict. >

Re: httpd and letsencrypt

+1 I am guessing someone from: https://letsencrypt.org/about/ or https://letsencrypt.org/isrg/ most likely Josh Aas? > On Aug 26, 2016, at 12:44 PM, Jacob Champion wrote: > > On 08/26/2016 07:47 AM, Rich Bowen wrote: >> At LinuxCon I spoke with the director of

Re: svn commit: r1756186 - in /httpd/httpd/trunk: include/ modules/http/ modules/proxy/

> On Aug 12, 2016, at 9:58 AM, yla...@apache.org wrote: > > Modified: httpd/httpd/trunk/include/ap_mmn.h > URL: > http://svn.apache.org/viewvc/httpd/httpd/trunk/include/ap_mmn.h?rev=1756186=1756185=1756186=diff > == >

Re: HTTP/1.1 strict ruleset

ay of trusted backend > servers and apps, you might want to be more tolerant (although Roy and > Jim may disagree with me on this.) > FWIW, I agree w/ you on this.

Re: HTTP/1.1 strict ruleset

> On Aug 4, 2016, at 6:21 PM, Roy T. Fielding wrote: > > > Leaving existing users in a broken state of non-compliance with the primary > Internet standard we are claiming to implement just because of unsubstantiated > FUD is far more frustrating. Bugs get fixed. Users

Re: Frequent wake-ups for mpm_event

> On Aug 9, 2016, at 9:02 AM, Luca Toscano wrote: > > > I like these suggestions, they look good! (This assuming that what I have > written above is correct, otherwise I didn't get them :) > +1

Re: Core on trunk for t/apache/limits.t

Looks like r1755343 fixed it... > On Aug 5, 2016, at 11:28 AM, Jim Jagielski <j...@jagunet.com> wrote: > > This is HEAD >> On Aug 5, 2016, at 11:09 AM, Yann Ylavic <ylavic@gmail.com> wrote: >> >> On Fri, Aug 5, 2016 at 4:06 PM, Jim Jagielski <

Re: Core on trunk for t/apache/limits.t

This is HEAD > On Aug 5, 2016, at 11:09 AM, Yann Ylavic <ylavic@gmail.com> wrote: > > On Fri, Aug 5, 2016 at 4:06 PM, Jim Jagielski <j...@jagunet.com> wrote: >> >> Will try to recreate on Linux > > Can you still reproduce with r1755343?

Re: Core on trunk for t/apache/limits.t

That's the one... :/ > On Aug 5, 2016, at 10:27 AM, Rainer Jung <rainer.j...@kippdata.de> wrote: > > Am 05.08.2016 um 16:06 schrieb Jim Jagielski: >> Testing HEAD on trunk I see t/apache/limits.t failing w/ >> a core dump on OSX 10.11.6: >> >> t/apach

Core on trunk for t/apache/limits.t

Testing HEAD on trunk I see t/apache/limits.t failing w/ a core dump on OSX 10.11.6: t/apache/limits.t .. 4/12 # Failed test 4 in t/apache/limits.t at line 168 fail #2 t/apache/limits.t .. Failed 1/12 subtests (lldb) bt * thread #1: tid = 0x, 0x7fff9307f362 libsystem_kernel.dylib`read +

Re: Frequent wake-ups for mpm_event

If APR_POLLSET_WAKEABLE was more universal and, therefore, more widely tested, I'd be +1... as it is, let's see what the feedback is. > On Aug 5, 2016, at 8:58 AM, Luca Toscano wrote: > > > > 2016-08-04 17:56 GMT+02:00 Luca Toscano : > Hi Apache

Anyone using CLion ?

CLion is a C IDE built around cmake. I thought I'd try using it w/ trunk but have had numerous issues, likely because our cmake implementation is a work-in-progress. Anyone have success in using CLion on httpd or, in fact, any non-cmake C project?

Re: svn commit: r1754579 - /httpd/httpd/trunk/server/gen_test_char.c

If we use this table more than once and we depend on consistency between them then we should make it a shared extern. > On Jul 29, 2016, at 6:00 PM, wr...@apache.org wrote: > > Author: wrowe > Date: Fri Jul 29 22:00:52 2016 > New Revision: 1754579 > > URL:

Re: 2.4.24 soon?

I think we should look into other stuff we could fold in in the short term. > On Jul 21, 2016, at 10:27 AM, Eric Covener <cove...@gmail.com> wrote: > > We have httpoxy as well as a rewrite+fastcgi regression in the queue. > Jim, do you have a near-term release in you

Re: svn commit: r1753263 - in /httpd/httpd/trunk: include/httpd.h modules/http/http_protocol.c

e first value. > > I suggest on trunk we use a value outside the bitmask range of 0-63 as > INVALID and consider turning this into an array of 128 bits. mod_ftp, for > examples, implents many more non-http methods and relies on the method auth > logic. > > >

Re: svn commit: r1753263 - in /httpd/httpd/trunk: include/httpd.h modules/http/http_protocol.c

Doesn't this make this unsuitable for backport for 2.4? > On Jul 18, 2016, at 12:20 PM, wr...@apache.org wrote: > > Author: wrowe > Date: Mon Jul 18 16:20:27 2016 > New Revision: 1753263 > > URL: http://svn.apache.org/viewvc?rev=1753263=rev > Log: > A whole lotta nope, if you implement HTCPCP

Re: svn commit: r1753223 - /httpd/httpd/trunk/modules/http/http_protocol.c

Beat me to the patch... :) > On Jul 18, 2016, at 12:02 PM, William A Rowe Jr <wr...@rowe-clan.net> wrote: > > On Mon, Jul 18, 2016 at 11:00 AM, Jim Jagielski <j...@jagunet.com> wrote: > Hrm. ap_method_registry_init lacks HEAD > > And has no M_HEAD, it's M_GET

Re: svn commit: r1753223 - /httpd/httpd/trunk/modules/http/http_protocol.c

I am getting NUMEROUS errors on trunk... HEAD is returning 501. The only test where this does NOT occur is: "HEAD /modules/cgi/perl.pl HTTP/1.1" 200 8 Looks suspicious to me... > On Jul 18, 2016, at 11:44 AM, Rüdiger Plüm wrote: > > > > On 07/18/2016 05:28 PM, William A

Re: svn commit: r1753223 - /httpd/httpd/trunk/modules/http/http_protocol.c

Hrm. ap_method_registry_init lacks HEAD. > On Jul 18, 2016, at 11:57 AM, William A Rowe Jr <wr...@rowe-clan.net> wrote: > > Investigating, should have it clearer w/in 1/2 an hr > > > On Jul 18, 2016 10:54 AM, "Jim Jagielski" <j...@jagunet.com> wrote:

Re: Multiple test framework errors on trunk

[Mon Jul 18 15:57:00.513202 2016] [core:error] [pid 6239:tid 123145317863424] [client 127.0.0.1:60655] AH00135: Invalid method in request HEAD /apache/etags/none/plus-mis/minus-ms/test.txt HTTP/1.1 > On Jul 18, 2016, at 11:55 AM, Jim Jagielski <j...@jagunet.com> wrote: > > In

Re: svn commit: r1753223 - /httpd/httpd/trunk/modules/http/http_protocol.c

; Investigating, should have it clearer w/in 1/2 an hr > > > On Jul 18, 2016 10:54 AM, "Jim Jagielski" <j...@jagunet.com> wrote: > I am getting NUMEROUS errors on trunk... HEAD is returning 501. The > only test where this does NOT occur is: > > &

Re: Multiple test framework errors on trunk

In fact, ALL HEADs are returning 501, except for this single one: "HEAD /modules/cgi/perl.pl HTTP/1.1" 200 8

Re: Multiple test framework errors on trunk

etags.t at line 160 fail #50 Looks like the same w/ headers too... lots of 501s :( > On Jul 18, 2016, at 11:31 AM, Jim Jagielski <j...@jagunet.com> wrote: > > On CentOS6 as well. Obviously, either something is hosed on > trunk or something has changed and the test framework

Re: Multiple test framework errors on trunk

On CentOS6 as well. Obviously, either something is hosed on trunk or something has changed and the test framework has not been updated... > On Jul 18, 2016, at 11:17 AM, Jim Jagielski <j...@jagunet.com> wrote: > > On OSX 10.11.5 (Xcode 7.3.x), I am getting multiple errors on trun

Multiple test framework errors on trunk

On OSX 10.11.5 (Xcode 7.3.x), I am getting multiple errors on trunk, with clear sailing on httpd-2.4 Test errors are for t/apache/etags.t, t/modules/expires.t and t/modules/headers.t Sample verbose output below: # --- # ExpiresActive On ExpiresDefault "modification plus 16 days 43 minutes 15

[ANNOUNCE] Apache HTTP Server 2.4.23 Released

Apache HTTP Server 2.4.23 Released The Apache Software Foundation and the Apache HTTP Server Project are pleased to announce the release of version 2.4.23 of the Apache HTTP Server ("Apache"). This version of Apache is our latest GA release of the new generation 2.4.x branch of

[RESULT] Re: [VOTE] Release Apache httpd 2.4.23 as GA

With the 72hrs up, and with: More than the 3 +1 (binding) votes and no +/-0 or -1s, I call this vote CLOSED with the result of the vote PASSING! Thx to all testers, etc... > On Jun 30, 2016, at 1:21 PM, Jim Jagielski <j...@jagunet.com> wrote: > > The pre-release test tarballs f

Re: [VOTE] Release Apache httpd 2.4.23 as GA

+1: o OSX 10.11.5, Xcode 7.3.1 o CentOS 6, 64bit o CentOS 7, 64 bit o Ubuntu 15.10, 64 bit > On Jun 30, 2016, at 1:21 PM, Jim Jagielski <j...@jagunet.com> wrote: > > The pre-release test tarballs for Apache httpd 2.4.23 can be found > at the usual place: > >

[VOTE] Release Apache httpd 2.4.23 as GA

The pre-release test tarballs for Apache httpd 2.4.23 can be found at the usual place: http://httpd.apache.org/dev/dist/ I'm calling a VOTE on releasing these as Apache httpd 2.4.23 GA. [ ] +1: Good to go [ ] +0: meh [ ] -1: Danger Will Robinson. And why. Vote will last the normal 72

Re: svn commit: r1750779 - in /httpd/httpd/trunk: CHANGES modules/ssl/ssl_engine_kernel.c

+1 > On Jun 30, 2016, at 11:38 AM, Stefan Eissing > wrote: > > We now set exactly the same callback right before in line 709. If we had more > than one callback, we would not have to specify NULL, but restore any > previous callback there was, right? > > But

Re: 2.4.23 T Status

I will doing a T of 2.4.23 this (Thurs) afternoon (eastern)...

2.4.23 T Status

With this coming weekend a US holiday weekend, I am hesitant to do a release this actual week. Instead, I will T either tomorrow or Fri in hopes of announcing on the 5th (Tues).

Re: svn commit: r1750392 - in /httpd/httpd/trunk: CHANGES docs/log-message-tags/next-number include/ap_mmn.h modules/proxy/mod_proxy.h modules/proxy/mod_proxy_ajp.c modules/proxy/mod_proxy_fcgi.c modu

> On Jun 27, 2016, at 4:25 PM, Yann Ylavic <ylavic@gmail.com> wrote: > > On Mon, Jun 27, 2016 at 9:05 PM, Jim Jagielski <j...@jagunet.com> wrote: >> >>> On Jun 27, 2016, at 1:26 PM, yla...@apache.org wrote: >>> >>> +apr_bucket_b

Re: T 2.4.23 tomorrow (Thurs) ??

I am thinking of a T today... Anyone see or know of any reasons for not doing so? Or anyone wish to make uninformed or incorrect assumptions (with veiled threats) against a T for no valid reason other than it's an opportunity to do so? > On Jun 22, 2016, at 4:05 PM, Jim Jagielski

Re: svn commit: r1750392 - in /httpd/httpd/trunk: CHANGES docs/log-message-tags/next-number include/ap_mmn.h modules/proxy/mod_proxy.h modules/proxy/mod_proxy_ajp.c modules/proxy/mod_proxy_fcgi.c modu

> On Jun 27, 2016, at 1:26 PM, yla...@apache.org wrote: > > +apr_bucket_brigade *tmp_bb; > } proxy_conn_rec; > I am missing the reason why this brigade needs to be a field in this struct. Is it simply to prevent us having to create it during each call of ap_proxy_check_backend()?

Re: svn commit: r1750301 - in /httpd/httpd/trunk/modules/proxy: mod_proxy.h proxy_util.c

Doesn't this depend on: trunk patch: http://svn.apache.org/r1656259 http://svn.apache.org/r1656359 (CHANGES entry) which, in STATUS, is tagged as still being worked? > On Jun 27, 2016, at 4:23 AM, Stefan Eissing wrote: > > This looks nice for

Re: T 2.4.23 tomorrow (Thurs) ??

Things are still too loosey-goosey... I am going to wait until the start of next week to (likely) T and give some time for the churn to stabilize.

Re: T 2.4.23 tomorrow (Thurs) ??

Ugg... Thanks for the test and the feedback. Will hold off and look into it. > On Jun 23, 2016, at 7:13 AM, Jens Schleusener <jens.schleuse...@t-online.de> > wrote: > > On Wed, 22 Jun 2016, Jim Jagielski wrote: > >> Subj sez it all... afaict, there are no showsto

T 2.4.23 tomorrow (Thurs) ??

Subj sez it all... afaict, there are no showstoppers and no outstanding issues (none seen in STATUS, or noted as such on any Email threads). So... anyone opposed to a T tomorrow in the hopes of getting this out to people by the start of next week??

2.4.23

My plan is to tag T once we get the configure stuff sorted out.

Re: [VOTE] Release Apache httpd 2.4.22 as GA

I am recalling this VOTE as well.

Re: [VOTE] Release Apache httpd 2.4.22 as GA

> On Jun 21, 2016, at 10:58 AM, William A Rowe Jr <wr...@rowe-clan.net> wrote: > > > > > On Jun 21, 2016, at 7:39 AM, Jim Jagielski <j...@jagunet.com> wrote: > > > > Just a reminder for those still testing and/or waiting to cast > > a vote: One

Re: [VOTE] Release Apache httpd 2.4.22 as GA

a larger group of people to test it out. > On Jun 21, 2016, at 7:39 AM, Jim Jagielski <j...@jagunet.com> wrote: > > Just a reminder for those still testing and/or waiting to cast > a vote: One cannot veto a release and even tho OtherBill has > voted a someway bi-polar -1, my i

Re: svn commit: r1748888 - /httpd/httpd/trunk/modules/proxy/config.m4

> On Jun 21, 2016, at 7:56 AM, Plüm, Rüdiger, Vodafone Group > <ruediger.pl...@vodafone.com> wrote: > > > >> -Original Message- >> From: Jim Jagielski [mailto:j...@jagunet.com] >> Sent: Dienstag, 21. Juni 2016 13:46 >> To: dev@httpd.ap

Re: svn commit: r1748888 - /httpd/httpd/trunk/modules/proxy/config.m4

2.4.21 was pulled for a very specific reason and was fixed to address that specific reason... The below will be in 2.4.23 for sure. The question is whether or not to pull/stop 2.4.22... since this isn't a regression per-se, I am leaning towards not unless this issue is larger than it appears...

Re: [VOTE] Release Apache httpd 2.4.22 as GA

iam A Rowe Jr <wr...@rowe-clan.net> wrote: > > On Mon, Jun 20, 2016 at 8:20 AM, Jim Jagielski <j...@jagunet.com> wrote: > The pre-release test tarballs for Apache httpd 2.4.22 can be found > at the usual place: > > http://httpd.apache.org/dev/dist/ >

Re: [VOTE] Release Apache httpd 2.4.22 as GA

> On Jun 20, 2016, at 9:20 AM, Jim Jagielski <j...@jagunet.com> wrote: > > The pre-release test tarballs for Apache httpd 2.4.22 can be found > at the usual place: > > http://httpd.apache.org/dev/dist/ > > I'm calling a VOTE on releasing these as Apache http

[VOTE] Release Apache httpd 2.4.22 as GA

The pre-release test tarballs for Apache httpd 2.4.22 can be found at the usual place: http://httpd.apache.org/dev/dist/ I'm calling a VOTE on releasing these as Apache httpd 2.4.22 GA. [ ] +1: Good to go [ ] +0: meh [ ] -1: Danger Will Robinson. And why. Vote will last the normal 72

Re: [VOTE] Release Apache httpd 2.4.21 as GA

Due to a last-minute regression, I am cancelling this VOTE. Instead, the plan is to get the regression fix approved for backport (http://svn.apache.org/viewvc?view=revision=1749151) and release 2.4.22. Thx to all testers... and keep your eyes open for the next VOTE to come hopefully later on

Re: [VOTE] Release Apache httpd 2.4.21 as GA

chreven: >> >> Yes. Everything else is +1. Just this. Just wanted to express that I do not >> see it as blocking, but am not happy about it either. >> >>> Am 20.06.2016 um 13:49 schrieb Jim Jagielski <j...@jagunet.com>: >>> >>> Although no

Re: [VOTE] Release Apache httpd 2.4.21 as GA

gt; Tested: > (15.5.0 Darwin): event, prefork, worker > (14.04.1-Ubuntu, x86_64): event, worker > > Vote: +0 > > The bug discovered by Michael Kaufmann is not release breaking for me. If > we'd find another issue, I would bring in the fix. > > -Stefan >

Re: [VOTE] Release Apache httpd 2.4.21 as GA

> On Jun 16, 2016, at 1:07 PM, Jim Jagielski <j...@jagunet.com> wrote: > > The pre-release test tarballs for Apache httpd 2.4.21 can be found > at the usual place: > > http://httpd.apache.org/dev/dist/ > > I'm calling a VOTE on releasing these as Apache http

[VOTE] Release Apache httpd 2.4.21 as GA

The pre-release test tarballs for Apache httpd 2.4.21 can be found at the usual place: http://httpd.apache.org/dev/dist/ I'm calling a VOTE on releasing these as Apache httpd 2.4.21 GA. [ ] +1: Good to go [ ] +0: meh [ ] -1: Danger Will Robinson. And why. Vote will last the normal 72

T Of 2.4.21 today (Thurs) around noon

I'll be doing a T of 2.4.21 around noonish today...

Re: h2_proxy_util.c, is this going make 2.4.21?

b Steffen <i...@apachelounge.com>: >>>>> >>>>> I rather like to test before tagging. >>>>> >>>>> Can you apply these changes for my testing also to Git ? >>>>> >>>>> Steffen >>>>> >

Re: h2_proxy_util.c, is this going make 2.4.21?

it ? >>> >>> Steffen >>> >>> On Tuesday 14/06/2016 at 10:54, Stefan Eissing wrote: >>>> I just backported the h2_proxy_util.c change in r1748359. It also uses the >>>> back ported ap_cstr_casecmp* instead of its own copies. I tried to

Re: h2_proxy_util.c, is this going make 2.4.21?

What needs to be done? > On Jun 13, 2016, at 2:20 PM, Gregg Smith <g...@gknw.net> wrote: > > Hi Stefan, > > Any plans to backport this before Jim tags 2.4.21 tomorrow? > > Thanks, > > Gregg >

T Of 2.4.21 on Tues (June 14)

I am looking to T 2.4.21 tomorrow (Tues) with a hoped-for release on Friday. > On Jun 8, 2016, at 9:34 AM, Jim Jagielski <j...@jagunet.com> wrote: > > I am thinking about a T next week... > > Get those backports and votes IN! > >> On May 23, 2016, at 9:32 AM, J

Re: [PATCH] mod_proxy_http2: fix proxying of 32K+ sized responses

Thanks! > On Jun 10, 2016, at 10:58 AM, Evgeny Kotkov <evgeny.kot...@visualsvn.com> > wrote: > > Jim Jagielski <j...@jagunet.com> writes: > >> Thanks for the patch... It came thru, at least for me, mangled. >> >> Could you resend? > &g

Re: [PATCH] mod_proxy_http2: fix proxying of 32K+ sized responses

Thanks for the patch... It came thru, at least for me, mangled. Could you resend? > On Jun 10, 2016, at 10:21 AM, Evgeny Kotkov > wrote: > >

Re: Multiple patches; any takers before T?

Thx! Are any of these in trunk, or are they 2.4-branch specific? > On Jun 9, 2016, at 1:03 PM, Jacob Champion wrote: > > Hi all, > > It may be too late now that the T machinery is in motion, but I'll bump > some of my patchsets: > > - APXS:

Re: Will push for a T of 2.4.21 in June

I am thinking about a T next week... Get those backports and votes IN! > On May 23, 2016, at 9:32 AM, Jim Jagielski <j...@jagunet.com> wrote: > > Just a FYI: With http/2 and dynamic health checks now in > 2.4.x's reverse proxy, I will push for a release of 2.4.21 > for ear

Re: svn commit: r1747056 - in /httpd/httpd/branches/2.4.x: ./ STATUS modules/mappers/mod_rewrite.c

> It is just a remark that we should move forward and either backport > ap_cstr_casecmp[n] or decide to delay it to another release. I'd really prefer that it be added to this release... But I also know that there's some overlap w/ APR and that always causes delays.

Will push for a T of 2.4.21 in June

Just a FYI: With http/2 and dynamic health checks now in 2.4.x's reverse proxy, I will push for a release of 2.4.21 for early June. We need to continue to show that Apache httpd is leading tech in web server IT, and these enhancements are proof positive of that. I will RM.

Re: mod_proxy_hcheck backport

Seems like adding that directly to the module itself makes the most sense. Later versions will allow for using Provider API to make it easier to add various checks, On 2016-05-17 05:17, Stefan Eissing <stefan.eiss...@greenbytes.de> wrote: > Jim, > > how do you see the possi

Re: mod_proxy_hcheck backport

> On May 16, 2016, at 3:37 PM, Daniel Ruggeri <drugg...@primary.net> wrote: > > On 5/16/2016 8:19 AM, Jim Jagielski wrote: >> THANKS! This feature seemed to cause a lot of buzz @ ApacheCon so >> would be > > I believe I heard and/or used the term

Re: mod_proxy_hcheck backport

> On May 14, 2016, at 9:28 PM, drugg...@primary.net wrote: > > On 2016-05-12 16:33, Jim Jagielski wrote: >> Looking, begging, pleading for tests and votes :) > > Yup! You got mine. THANKS! This feature seemed to cause a lot of buzz @ ApacheCon so would be very very n

mod_proxy_hcheck backport

Looking, begging, pleading for tests and votes :)

Re: svn commit: r1739876 - /httpd/httpd/branches/2.4.x/STATUS

+1... I had just applied the patch in STATUS w/o seeing this thread. Best to just revert this all and get back to 2.4.18 behavior (and code) > On Apr 27, 2016, at 12:40 AM, Stefan Eissing > wrote: > > > >> Am 27.04.2016 um 03:53 schrieb William A Rowe Jr

Request for eyes and tests

In the 2.4 STATUS file there are 2 backports which, I think, would be exceptional if we could get in 2.4 asap. They are the dynamic health check and the http/2 proxy stuff. These are some killer features and would be great to have httpd 2.4 be the web server/reverse proxy that brings 'em to the

Re: TIL

Grrr... w/o looking too deeply into this, this seems very wrong. Is that a long-standing bug or something recently "optimized" away? > On Apr 26, 2016, at 10:49 AM, Stefan Eissing > wrote: > > Today I Learned the difference between writing > DATA + META > and

Re: allow newlines in T_ESCAPE_LOGITEM?

No opinion :) > On Apr 13, 2016, at 3:43 PM, Eric Covener wrote: > > Currently newlines get backslash-escaped if written to the errorlog. > This is via server/gen_test_char.c and stems from an ancient vuln > about escape sequences in log files potentially affecting peoples >

Unintended Side Effects (Was: Re: svn commit: r1732275 - in /httpd/httpd/branches/2.4.x: ./ include/ap_mmn.h include/http_connection.h include/scoreboard.h modules/generators/mod_status.c modules/ssl/

We should always ensure that when we fix something, or when we add something, we don't change the current behavior of httpd in an unintended way. This rev is a great example of that. The clearing of those scoreboard slots is completely unrelated to the actual change itself. Of course, the "blame"

Re: svn commit: r1732275 - in /httpd/httpd/branches/2.4.x: ./ include/ap_mmn.h include/http_connection.h include/scoreboard.h modules/generators/mod_status.c modules/ssl/ssl_engine_kernel.c server/con

The old behavior was expected, and very, very useful. It was made that way for a reason. +1 on reverting to old behavior... > On Apr 13, 2016, at 4:04 PM, Yann Ylavic wrote: > > On Thu, Feb 25, 2016 at 11:27 AM, wrote: >> Author: icing >> Date: Thu Feb

[ANNOUNCE] Apache HTTP Server 2.4.20 Released

Apache HTTP Server 2.4.20 Released The Apache Software Foundation and the Apache HTTP Server Project are pleased to announce the release of version 2.4.20 of the Apache HTTP Server ("Apache"). This version of Apache is our latest GA release of the new generation 2.4.x branch of

Re: proxy API compat break in 2.4.7

Ahh... yes, for 3rd party modules depending on mod_proxy, or using mod_proxy, they would need to be recompiled. Ideally, we should have put these at the end of the struct as we do with the more "major" structs. > On Apr 7, 2016, at 2:09 PM, Rainer Jung wrote: > >

Re: proxy API compat break in 2.4.7

> On Apr 7, 2016, at 6:55 PM, Yann Ylavic wrote: > > On Thu, Apr 7, 2016 at 8:09 PM, Rainer Jung wrote: >> Revision 1560081 (backport of r1533087) introduced "char >> uds_path[PROXY_WORKER_MAX_NAME_SIZE]" in the middle of the >>

<    3   4   5   6   7   8   9   10   11   12   >