Hi,
> Here's an update of current 1.5 status. All reported bugs were fixed. > > I'm currently working on something that was just reported to me today > which is not exactly a bug but a design mistake around the way track- > counters are tracked between HTTP requests when they're done in "content" > rules. And we'll probably be ready for a dev22 that should fix all the > reported issues. Thanks for the update. So I suspect there is still a small timeframe (a few weeks) where you still accept low-risk feature patches? I'm specifically asking because I would've liked to take a look at extending the verify keyword with a snifilter, like mentioned here [1]. This would be useful for SNI-based vhosting when some domains authenticate the client certificate and others don't (also see the downsides of "verify optional" in that thread). Regards, Lukas [1] http://permalink.gmane.org/gmane.comp.web.haproxy/14733
