Re: svn commit: r1725301 [1/6] - in /httpd/httpd/branches/2.4.x: ./ docs/manual/mod/ modules/http2/

> Am 18.01.2016 um 22:05 schrieb Christophe JAILLET > : > > Le 18/01/2016 17:22, ic...@apache.org a écrit : >> Author: icing >> Date: Mon Jan 18 16:22:57 2016 >> New Revision: 1725301 >> >> URL: http://svn.apache.org/viewvc?rev=1725301=rev >> Log: >> mod_http2

Re: mod_mime_magic, gzipped tarballs and Docker

On 01/18/2016 09:22 PM, William A Rowe Jr wrote: On Mon, Jan 18, 2016 at 5:13 AM, Jan Kaluža > wrote: On 01/08/2016 07:44 PM, William A Rowe Jr wrote: Do we have to repeat the softmagic call if checkzmagic resolves to

Re: mod_fcgid and broken doc links

There is a need and an audience for both. We provide both. I see no reason for us to stop doing that unless we feel that we can no longer support both in the manner in which our community expects. FWIW, I don't see that as the current situation. > On Jan 18, 2016, at 9:29 PM, William A Rowe Jr

Re: Work in progress: mod_proxy Health Check module

On 19 January 2016 19:01:12 GMT, Jim Jagielski wrote: >Okey dokey... this is quite functional at this stage. >Right now we have: > > o TCP health checking (socket up/down) > o HTTP OPTIONS checking > o HTTP HEAD checking > o Support for ap_expr against the response of >

Re: help from cache gurus?

fwiw, this tested out fine Thx! > On Jan 14, 2016, at 10:25 AM, Eric Covener wrote: > > Review please? Didn't want unnecessary churn in svn. > > http://people.apache.org/~covener/patches/httpd-trunk-cachecontrol.diff > > (whitespace not included) > > I think the changing

Re: svn commit: r1725523 - in /httpd/httpd/trunk/modules/proxy: mod_proxy.h mod_proxy_hcheck.c

On 01/19/2016 06:45 PM, Jim Jagielski wrote: > >> On Jan 19, 2016, at 11:09 AM, Ruediger Pluem wrote: >> >>> +} else { >>> +if (rv != APR_SUCCESS) { >>> +worker->s->error_time = now; >>> +worker->s->fcount += 1; >>> +if

Re: svn commit: r1725523 - in /httpd/httpd/trunk/modules/proxy: mod_proxy.h mod_proxy_hcheck.c

Am 19.01.2016 um 20:02 schrieb Jim Jagielski: Ahhh... yeah, I guess updating all the usages to do that makes sense. Done in r1725602. On Jan 19, 2016, at 1:59 PM, Ruediger Pluem wrote: On 01/19/2016 06:45 PM, Jim Jagielski wrote: On Jan 19, 2016, at 11:09 AM,

Re: Work in progress: mod_proxy Health Check module

Okey dokey... this is quite functional at this stage. Right now we have: o TCP health checking (socket up/down) o HTTP OPTIONS checking o HTTP HEAD checking o Support for ap_expr against the response of the backend for OPTIONS/HEAD o Ability to add a URI to the worker's path

Re: svn commit: r1725523 - in /httpd/httpd/trunk/modules/proxy: mod_proxy.h mod_proxy_hcheck.c

> On Jan 19, 2016, at 11:09 AM, Ruediger Pluem wrote: > >> +} else { >> +if (rv != APR_SUCCESS) { >> +worker->s->error_time = now; >> +worker->s->fcount += 1; >> +if (worker->s->fcount >= worker->s->fails) { >> +

Re: svn commit: r1725523 - in /httpd/httpd/trunk/modules/proxy: mod_proxy.h mod_proxy_hcheck.c

Ahhh... yeah, I guess updating all the usages to do that makes sense. thx! > On Jan 19, 2016, at 1:59 PM, Ruediger Pluem wrote: > > > > On 01/19/2016 06:45 PM, Jim Jagielski wrote: >> >>> On Jan 19, 2016, at 11:09 AM, Ruediger Pluem wrote: >>> +

Re: Work in progress: mod_proxy Health Check module

Right now GET and CPING (as well as provider) is on my TODO, in fact, they are currently set as "unimplemented" although the hooks are there. The main issue is that we need to worry about a (possibly) large response body and some method of checking against that. I have some ideas, but it's not as

Re: mod_mime_magic, gzipped tarballs and Docker

Accept On Jan 19, 2016 4:22 AM, "William A Rowe Jr" wrote: > On Mon, Jan 18, 2016 at 5:13 AM, Jan Kaluža wrote: > >> On 01/08/2016 07:44 PM, William A Rowe Jr wrote: >> >>> Do we have to repeat the softmagic call if checkzmagic resolves to >>>

Re: svn commit: r1725523 - in /httpd/httpd/trunk/modules/proxy: mod_proxy.h mod_proxy_hcheck.c

On 01/19/2016 03:14 PM, j...@apache.org wrote: > Author: jim > Date: Tue Jan 19 14:14:27 2016 > New Revision: 1725523 > > URL: http://svn.apache.org/viewvc?rev=1725523=rev > Log: > For OPTIONS and HEAD, only 2xx and 3xx are considered "passing" > (until I implement the conditions expr

socket timeouts

A questions for the knowledgable SSL people here: I experimented with setting socket timeouts to 1 second during HTTP/2's keepalive reading and closing the connection after n such TIMEUP returns. That works nicely on cleartext connections, but https:// return APR_EOF on reads after the first