Re: svn commit: r1804671 - /httpd/httpd/trunk/modules/md/mod_md_config.c

Thanks for the feedback and the crosspost. I think it would be great to offer peeps that already link serf into their server to avoid an additional dependency. Regarding Apache infrastructure use: Would you prefer that the server gracefully restarts itself (when needed, at a time interval

Re: svn commit: r1804671 - /httpd/httpd/trunk/modules/md/mod_md_config.c

Already requested in Git issue #17 : On Windows: A script to sent an email, kill zombie processes (needed now on Win), copy e.g. cert's to mail servers etc. Btw. There there is at moment no restart in mod-md code for Windows, maybe a dev has a solution (Maybe Bill) ? In mod_md_os.c now:

Re: svn commit: r1804671 - /httpd/httpd/trunk/modules/md/mod_md_config.c

Oh, I don't know that Infra has any specific request on the restart/update mechanism. I'd just say: build it how you think best. What would work for Everybody should work just fine for us. On Mon, Aug 14, 2017 at 2:09 AM, Stefan Eissing < stefan.eiss...@greenbytes.de> wrote: > Thanks for the

Re: SSLPolicy

> I hope this looks attractive to you. All bugs are mine. Let me know what you > think. It looks neat. I think accessible doc will be key. But for the sake of discussion, what will we do / what will distributors do when say TLS1.3 or some esoteric part of it is only available in some SSL

SSLPolicy

Here is my proposal for more semantic sugar. It defines 3 new SSL* config directives: - to define a set of SSL* directives under a name - SSLPolicy merge the non-proxy parts of the policy into the current server config. local directives will override - SSLProxyPolicy

Re: SSLPolicy

Am 14.08.2017 um 17:14 schrieb Eric Covener : >> I hope this looks attractive to you. All bugs are mine. Let me know what you >> think. > > It looks neat. I think accessible doc will be key. yes. I was thinking of generating, but had no bright idea so far. > But for the