Re: [VOTE] Release Apache httpd 2.4.26 as GA

+1 AIX/xlc/ppc64 I have two quirks to record, both are openssl / openssl 1.1 related but given the state of my AIX system I am still +1 on the release. - proxy/ssl.t almost totally fails with handhsake errors between client and origin [Tue Jun 13 21:37:04.265062 2017] [ssl:info] [pid

Re: svn commit: r20021 - /dev/httpd/

I don't know that it really matters, but this guy is in there twice (in each CHANGES doc), once with the PR # and once without: > + *) mod_proxy: Allow the per-request environment variable "no-proxy" to > + be used as an alternative to ProxyPass /path !. This is primarily > + to set

[VOTE] Release Apache httpd 2.4.26 as GA

The pre-release test tarballs for Apache httpd version 2.4.26 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.26 GA. [ ] +1: Good to go [ ] +0: meh [ ] -1: Danger Will Robinson. And why. Vote will last the

Re: The drive for 2.4.26

There was a delay in doing the T due to an issue that was being investigated. This looks resolved now. With that, I plan on doing a T& today at ~1:30pm (Eastern) unless someone else wishes to RM.

Re: TTLimit directive

Hey Nick, it must be 0, not 255. I updated it in patch attached  Sent from my iPhone > On 13 Jun 2017, at 13:52, Nick Kew wrote: > >> On Tue, 2017-06-13 at 11:41 +0300, Donatas Abraitis wrote: >> >> I would like to propose this patchset allowing to set maximum TTL value for

Re: TTLimit directive

On Tue, 2017-06-13 at 11:41 +0300, Donatas Abraitis wrote: > I would like to propose this patchset allowing to set maximum TTL value for > incoming requests. This is not a usual use case, but I'm interested (maybe > others too) to have this in place. The real use case would be like this one >

Re: ocsp stapling improvements

> Am 12.06.2017 um 21:35 schrieb Ruediger Pluem : > > > > On 06/12/2017 05:25 PM, Stefan Eissing wrote: >> I talked to the people orignally writing our ssl OCSP code regarding >> feedback we got from the Let's Encrypt server outage [1]. We agreed >> that some valid points

Re: ocsp stapling improvements

> Am 13.06.2017 um 00:48 schrieb Hanno Böck : > > Hi, > > On Mon, 12 Jun 2017 17:25:39 +0200 > Stefan Eissing wrote: > >> 1. Hand out existing responses until expired >> 2. Persist responses (is this just a config/default issue?) >> 3. Start

TTLimit directive

Hi, I would like to propose this patchset allowing to set maximum TTL value for incoming requests. This is not a usual use case, but I'm interested (maybe others too) to have this in place. The real use case would be like this one http://blog.donatas.net/blog/2017/04/20/http-request-validation/.