On 20 Mar 2025, at 16:12, Rainer Jung <rainer.j...@kippdata.de> wrote:
> Am 20.03.25 um 16:34 schrieb Graham Leggett via dev: >> On 20 Mar 2025, at 15:08, Graham Leggett <minf...@sharp.fm> wrote: > ... >> To sum up: >> - httpd-trunk + apr-trunk - old API and new API will not build by definition. >> - httpd-trunk + apr-trunk + https://github.com/apache/httpd/pull/438: >> <https://github.com/apache/httpd/pull/438:> new API and new API will build >> - httpd-trunk + apr-util-1.7: old API and old+new API will build >> - httpd-trunk + apr-util-1.7 + https://github.com/apache/httpd/pull/438 >> <https://github.com/apache/httpd/pull/438:>: new API and old+new API will >> build > > What about httpd 2.4.x and apt-util 1.7.x? httpd v2.4.x is identical to httpd-trunk. Everything in httpd-trunk has been backported to v2.4, so it's all the same code. Replace httpd-trunk with httpd-2.4.x and you get the same matrix above. I use this in production using apr-util v1.7 + httpd 2.4.63 at the moment. The end goal is I get full SASL support, specifically EXTERNAL over unix domain sockets, and it works great. Regards, Graham --
