On 22.02.2014 19:17, Falco Schwarz wrote:
Kaspar, I switched back to your version and realized, that the directive
SSLCertificateChainFile was always used in a VirtualHost.
If the directive is in server scope, the warning is written correctly.
On 22.02.2014 18:56, William A. Rowe Jr. wrote:
Understood and this would explain assigning them to MOD_SSL_LIBS etc. But
added to MOD_LIBS? That struck me as very odd.
Putting a module prefix into the variable name would make assembling the
commands in build/rules.mk more complex, and it
William A. Rowe Jr. wrote:
I believe that Kaspar and Ruediger are still entirely at odds with my
position, but this 'enhancement' should never have been unilaterally
applied as it was to 2.2.26 and must be reverted (even as the feature
is 'fixed' with corrections they have blessed), e.g. the
On 21.02.2014 04:08, Yann Ylavic wrote:
Similarly, a new SSLProxyCheckPeerCN canon option could be handled
so that admins needing ProxyPreserveHost on could still forward the
client's Host but check the backend's CN against ServerName.
It remains my humble opinion, that this behavior should be
