Re: Better ap_casecmpstr[n]?

2015-12-29 Thread Jim Jagielski
> On Dec 29, 2015, at 5:14 PM, William A Rowe Jr wrote: > > > Directive names, yes. Directive arguments - not as much. Yeah... that's what I said. We know our names :)

Re: Better ap_casecmpstr[n]?

2015-12-29 Thread William A Rowe Jr
On Tue, Dec 29, 2015 at 10:35 AM, Jim Jagielski wrote: > > > On Dec 29, 2015, at 11:28 AM, Yann Ylavic wrote: > > > > On Tue, Dec 29, 2015 at 5:16 PM, Jim Jagielski wrote: > >> In a sep thread on dev@apr, OtherBill appears to be trying to > >> determine the "right" name for the APR impl... maub

Re: Work in progress: mod_proxy Health Check module

2015-12-29 Thread Jim Jagielski
There is a somewhat easy way to do this via leveraging the functionality of SetEnvIfExpr. For example, what I am testing is the idea of: SetEnvIfCond "-R '10.0.0.0/8' || -R '172.16.0.0/12' || -R '192.168.0.0/16'" rfc1918 Which creates and stores *but does not evaluate* the above expressi

Work in progress: mod_proxy Health Check module

2015-12-29 Thread Jim Jagielski
Just a note that I've started committing my mod_proxy health check module work... it is still a work-in-progress but the goal is to always ensure that trunk is buildable and usable. Right now, the module needs to be explicitly enabled during configuration and all specific health-checks are basicall

Re: Better ap_casecmpstr[n]?

2015-12-29 Thread Yann Ylavic
On Tue, Dec 29, 2015 at 5:35 PM, Jim Jagielski wrote: > >> On Dec 29, 2015, at 11:28 AM, Yann Ylavic wrote: >> >> On Tue, Dec 29, 2015 at 5:16 PM, Jim Jagielski wrote: >>> >>> PS: What determines "abusive" usage? >> >> When used to compare something which is not a HTTP token or a scheme >> (eg.

Re: Better ap_casecmpstr[n]?

2015-12-29 Thread Jim Jagielski
> On Dec 29, 2015, at 11:28 AM, Yann Ylavic wrote: > > On Tue, Dec 29, 2015 at 5:16 PM, Jim Jagielski wrote: >> In a sep thread on dev@apr, OtherBill appears to be trying to >> determine the "right" name for the APR impl... maube we should >> wait to see what it's decided on there and we can fo

Re: Better ap_casecmpstr[n]?

2015-12-29 Thread Yann Ylavic
On Tue, Dec 29, 2015 at 5:16 PM, Jim Jagielski wrote: > In a sep thread on dev@apr, OtherBill appears to be trying to > determine the "right" name for the APR impl... maube we should > wait to see what it's decided on there and we can follow > suit. OK, although we won't be able to use APR's func

Re: Better ap_casecmpstr[n]?

2015-12-29 Thread Jim Jagielski
In a sep thread on dev@apr, OtherBill appears to be trying to determine the "right" name for the APR impl... maube we should wait to see what it's decided on there and we can follow suit. PS: What determines "abusive" usage? > On Dec 29, 2015, at 10:56 AM, Yann Ylavic wrote: > > On Tue, Dec 29,

Re: Better ap_casecmpstr[n]?

2015-12-29 Thread Yann Ylavic
On Tue, Dec 29, 2015 at 3:24 PM, Jim Jagielski wrote: > ping. > > Just a reminder that right now, trunk uses ap_casecmpstr[n](), > which can make some backport requests "problematic" due to > possible merge conflicts. I've just committed (in r1722150) more reverts of abusive ap_casecmpstr[n]() us

Re: Better ap_casecmpstr[n]?

2015-12-29 Thread Jim Jagielski
ping. Just a reminder that right now, trunk uses ap_casecmpstr[n](), which can make some backport requests "problematic" due to possible merge conflicts. Can we *please* decide what we are doing? trunk is starting to accumulate a bunch of kruft, which will make it difficult when we decide to sta

Re: .gitignore found in modules/http2

2015-12-29 Thread Stefan Eissing
Gone in r1722074. Was added by the original import. > Am 28.12.2015 um 18:01 schrieb Eric Covener : > > On Mon, Dec 28, 2015 at 11:46 AM, Jacob Perkins > wrote: >> We found a .gitignore file ./modules/http2 that is removing the MakeFile >> from the sources. Was this supposed to be merged in? It’