Re: OK to backport mod_md 2.6.11 features?

On 6/15/26 11:19 AM, Rainer Jung wrote:
> Since mod_md is now archived upstreams, I would like to backport the last few features that were added in 2.6.11 before it got
> archived. Backport means first backport to trunk, but likely also propose for 2.4.x
> 
> They are mostly:
> 
> * Support CA-specific HTTP proxy settings
>   Allow the MDHttpProxy setting to be set per MDomain.
> 
> * Support CA-specific connection root certificates
>   Allow the MDCACertificateFile setting to be set per MDomain.
> 
> * New directive: MDHttpProxyCACertificateFile
> 
> At the end, our trunk mod_md would be in sync with the archived one, except for the few trunk local changes, like new default for
> MDServerStatus etc.
> 
> I would also like to remove MOD_MD_VERSION and MOD_MD_VERSION_NUM, because having separate versions for mod_md probably makes no
> more sense.
> 
> Finally I would take a look at the differences between pytest in the archived mod_md version and our trunk one and see, what seems
> plausible for backport.
> 
> Are the any objections?

Fine with me. Thanks for taking care.

Regards

Rüdiger