Additional LB providers

2015-06-18 Thread Jim Jagielski
I'm playing around w/ a newish LB provider that balances based on latency. I'd like to fold it in after I clean it up a bit but it seems to me that we could also fold in the round-robin provider in example (after a suitable cleanup) as well as add in a simply by_random as well. Comments?

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

2015-06-18 Thread William A Rowe Jr
In some cases, perhaps, but this was objection asked-and-answered so my -1 was void. On Thu, Jun 18, 2015 at 12:07 PM, Yann Ylavic ylavic@gmail.com wrote: On Thu, Jun 18, 2015 at 5:39 PM, wr...@apache.org wrote: Author: wrowe Date: Thu Jun 18 15:39:53 2015 New Revision: 1686248

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

2015-06-18 Thread Yann Ylavic
On Thu, Jun 18, 2015 at 5:39 PM, wr...@apache.org wrote: Author: wrowe Date: Thu Jun 18 15:39:53 2015 New Revision: 1686248 URL: http://svn.apache.org/r1686248 Log: After addressing a defect, don't discuss, this isn't a forum :) Note the patch is updated, and delete now-irrelevant

NOTE: Intent to TR 2.4.15 Tomorrow (Friday, June 19)

2015-06-18 Thread Jim Jagielski
Subj sez it all.

Re: NOTE: Intent to TR 2.4.15 Tomorrow (Friday, June 19)

2015-06-18 Thread Jeff Trawick
On Thu, Jun 18, 2015 at 1:08 PM, Jim Jagielski j...@jagunet.com wrote: Subj sez it all. +!

Re: Roll 2.2.30 in conjunction with 2.4.14

2015-06-18 Thread William A Rowe Jr
On Jun 11, 2015 8:22 AM, Eric Covener cove...@gmail.com wrote: On Thu, Jun 11, 2015 at 9:08 AM William A Rowe Jr wr...@rowe-clan.net wrote: But withholding a security fix for legacy server users? Sounds like a way to earn distrust of the user community, not reassure them that 2.4.14 is the

Re: NOTE: Intent to TR 2.4.15 Tomorrow (Friday, June 19)

2015-06-18 Thread Yann Ylavic
On Thu, Jun 18, 2015 at 7:08 PM, Jim Jagielski j...@jagunet.com wrote: Subj sez it all. +1 Maybe including the gcc warning silenced in r1684057 (proposed in r1686298)?

Re: NOTE: Intent to TR 2.4.15 Tomorrow (Friday, June 19)

2015-06-18 Thread olli hauer
On 2015-06-18 19:08, Jim Jagielski wrote: Subj sez it all. I don't know if it is worth to report this, but the on 2.4.12. I don't see the following warnings Test build 2.4.15 (Last Changed Rev: 1686275) --- core.lo --- core.c:5003:1: warning: unused variable 'aplog_module_index'

Re: NOTE: Intent to TR 2.4.15 Tomorrow (Friday, June 19)

2015-06-18 Thread olli hauer
On 2015-06-18 22:17, Rainer Jung wrote: Am 18.06.2015 um 21:54 schrieb Jeff Trawick: On Thu, Jun 18, 2015 at 3:03 PM, olli hauer oha...@gmx.de mailto:oha...@gmx.de wrote: On 2015-06-18 19:08, Jim Jagielski wrote: Subj sez it all. I don't know if it is worth to report

Re: NOTE: Intent to TR 2.4.15 Tomorrow (Friday, June 19)

2015-06-18 Thread Yann Ylavic
Since wherever AP_DECLARE_MODULE is used we don't need the APLOG_USE_MODULE part (ie. the static declaration of aplog_module_index), that would possibly be better to use a new AP_DEFINE_MODULE, simply as: #define AP_DECLARE_MODULE(foo) \ module AP_MODULE_DECLARE_DATA foo##_module The

Re: NOTE: Intent to TR 2.4.15 Tomorrow (Friday, June 19)

2015-06-18 Thread Yann Ylavic
On Thu, Jun 18, 2015 at 9:03 PM, olli hauer oha...@gmx.de wrote: On 2015-06-18 19:08, Jim Jagielski wrote: Subj sez it all. I don't know if it is worth to report this, but the on 2.4.12. I don't see the following warnings These were not in 2.4.12 with the same compiler (and version)?

Re: NOTE: Intent to TR 2.4.15 Tomorrow (Friday, June 19)

2015-06-18 Thread Jeff Trawick
On Thu, Jun 18, 2015 at 3:03 PM, olli hauer oha...@gmx.de wrote: On 2015-06-18 19:08, Jim Jagielski wrote: Subj sez it all. I don't know if it is worth to report this, but the on 2.4.12. I don't see the following warnings Are you using clang for both compiles? (I think I saw those for

Re: NOTE: Intent to TR 2.4.15 Tomorrow (Friday, June 19)

2015-06-18 Thread olli hauer
On 2015-06-18 21:54, Jeff Trawick wrote: On Thu, Jun 18, 2015 at 3:03 PM, olli hauer oha...@gmx.de wrote: On 2015-06-18 19:08, Jim Jagielski wrote: Subj sez it all. I don't know if it is worth to report this, but the on 2.4.12. I don't see the following warnings Are you using clang

Re: NOTE: Intent to TR 2.4.15 Tomorrow (Friday, June 19)

2015-06-18 Thread Rainer Jung
Am 18.06.2015 um 21:54 schrieb Jeff Trawick: On Thu, Jun 18, 2015 at 3:03 PM, olli hauer oha...@gmx.de mailto:oha...@gmx.de wrote: On 2015-06-18 19:08, Jim Jagielski wrote: Subj sez it all. I don't know if it is worth to report this, but the on 2.4.12. I don't see the

Re: Using UPN from subjectAltName with SSLUserName

2015-06-18 Thread Yann Ylavic
On Thu, Jun 18, 2015 at 11:49 AM, Jan Pazdziora jpazdzi...@redhat.com wrote: I'd appreciate any comments about suitability of such change, as well as the implementation. Specifically, I'm not sure if people will prefer the generic and currently proposed SSL_CLIENT_SAN_otherName_n

Re: sni+alpn, vhost+certs

2015-06-18 Thread Stefan Eissing
I have a patch for this now, but discovered that mod_h2 needs some more: In the ALPN propose callback, the module needs to know which vhost the connection is about. And not only that, it needs the server_rec of that to check its config. If the module is disabled in that vhost, it should not

Using UPN from subjectAltName with SSLUserName

2015-06-18 Thread Jan Pazdziora
Hello, I've noticed that support for getting subjectAltName entries Email and Type landed in 2.4.13, via r1676087. We've come across another type in subjectAltName, Microsoft Universal Principal Name (OID 1.3.6.1.4.1.311.20.2.3) which would be useful to retrieve from the certificate and use for

Re: sni+alpn, vhost+certs

2015-06-18 Thread Yann Ylavic
On Thu, Jun 18, 2015 at 11:07 AM, Stefan Eissing stefan.eiss...@greenbytes.de wrote: It retrieves SNI servername via ssl_var_lookup, creates a fake request_rec incokes ap_update_vhost_from_headers(). Not very elegant. a) is there another way? Maybe define a new ap_get_vhost_from_name() and