From: Graham Leggett
+This directive points to a certificate store containing certificates, +intermediate certificates, and private keys, represented by a URI. +
++If no scheme is specified, the path will default to a file: +URI, pointing at PEM encoded data, or a PKCS12 file. Other schemes +include, but are not limited to, pkcs11: for smartcards and +HSMs, cng: for the Windows certificate store, and +handle: for TPMs. On Windows, where a file path is also a +valid URI, the file: scheme must be used. +
++The directive can be specified multiple times with tightly scoped +URIs to target specific certificates and keys, or could be specified +with a general URI like pkcs11: that considers all possible +certificates and keys. Certificates, intermediate certificates, and keys +can be defined in any order. +
+Certificates and keys are processed as follows. +
+If the private key is encrypted, the pass phrase dialog is forced +at startup time.
+ +These URIs are read at server startup, while the server is still running
+as root (before privilege dropping), so it may be owned by
+and readable only by root. The URI is not re-read during
+normal operation; a server restart is required for changes to take
+effect.
+You can use both SSLCertificateFile and SSLCertificateURI together, however +there is no overlap between the mechanisms. A certificate defined by +SSLCertificateFile will not be matched with a key from SSLCertificateURI. +
+
+This directive sets the all-in-one URI where you can assemble the
+Certificates of Certification Authorities (CA) whose clients you deal
+with. These are used for Client Authentication. This can be used alternatively
+and/or additionally to
This URI is read at server startup, while the server is still running
+as root (before privilege dropping), so it may be owned by
+and readable only by root. The URI is not re-read during
+normal operation; a server restart is required for changes to take
+effect.
+This directive sets the all-in-one file where you can
+assemble the Certificate Revocation Lists (CRL) of Certification
+Authorities (CA) whose clients you deal with. These are used
+for Client Authentication. This can be used alternatively and/or
+additionally to
This URI is read at server startup, while the server is still running
+as root (before privilege dropping), so it may be owned by
+and readable only by root. The URI is not re-read during
+normal operation; a server restart is required for changes to take
+effect.
+This directive points to a certificate store containing certificates, +intermediate certificates, and private keys, represented by a URI, +to be used when authenticating to another proxy server. +
++If no scheme is specified, the path will default to a file: +URI, pointing at PEM encoded data, or a PKCS12 file. Other schemes +include, but are not limited to, pkcs11: for smartcards and +HSMs, cng: for the Windows certificate store, and +handle: for TPMs. On Windows, where a file path is also a +valid URI, the file: scheme must be used. +
++The directive can be specified multiple times with tightly scoped +URIs to target specific certificates and keys, or could be specified +with a general URI like pkcs11: that considers all possible +certificates and keys. Certificates, intermediate certificates, and keys +can be defined in any order. +
+Proxy certificates and keys are processed as follows. +
+If the private key is encrypted, the pass phrase dialog is forced +at startup time.
+ +These URIs are read at server startup, while the server is still running
+as root (before privilege dropping), so it may be owned by
+and readable only by root. The URI is not re-read during
+normal operation; a server restart is required for changes to take
+effect.
When challenged to provide a client certificate by a remote server,
+the server should provide a list of acceptable certificate
+authority names in the challenge. If such a list is not
+provided,
If the list of CA names is provided by the remote server,
+and no matching client certificate can be found, no client
+certificate will be provided by
+You can use both SSLProxyMachineCertificateFile and +SSLProxyMachineCertificateURI together, however there is +no overlap between the mechanisms. A certificate defined by +SSLProxyMachineCertificateFile will not be matched with a +key from SSLProxyMachineCertificateURI. +
+
+This directive sets the all-in-one URI where you can assemble the
+Certificates of Certification Authorities (CA) whose remote servers you deal
+with. These are used for Remote Server Authentication. This can be used alternatively
+and/or additionally to
+
+This directive sets the all-in-one URI where you can
+assemble the Certificate Revocation Lists (CRL) of Certification
+Authorities (CA) whose remote servers you deal with. These are used
+for Remote Server Authentication. This can be
+used alternatively and/or additionally to