Updating extensions conf

Custom DH parameters and an EC curve name for ephemeral keys, can also be added to end of the first file configured using .

The files may also include intermediate CA certificates, sorted from leaf to root.Look in the Compatibility chapter for details on the compatibility variables. If the DN in question contains multiple attributes of the same name, this suffix is used as a zero-based index to select a particular attribute.For example, where the server certificate subject DN included two OU attributes, HTTP_USER_AGENT PATH_INFO AUTH_TYPE HTTP_REFERER QUERY_STRING SERVER_SOFTWARE HTTP_COOKIE REMOTE_HOST API_VERSION HTTP_FORWARDED REMOTE_IDENT TIME_YEAR HTTP_HOST IS_SUBREQ TIME_MON HTTP_PROXY_CONNECTION DOCUMENT_ROOT TIME_DAY HTTP_ACCEPT SERVER_ADMIN TIME_HOUR THE_REQUEST SERVER_NAME TIME_MIN REQUEST_FILENAME SERVER_PORT TIME_SEC REQUEST_METHOD SERVER_PROTOCOL TIME_WDAY REQUEST_SCHEME REMOTE_ADDR TIME REQUEST_URI REMOTE_USER'' e Xtension format function which can be used to expand any variables provided by any module, especially those provided by mod_ssl which can you find in the above table.Only the first file can be used for custom parameters, as they are applied independently of the authentication algorithm type.Finally the end-entity certificate's private key can also be added to the certificate file instead of using a separate directive. If it is used, the certificate files using such an embedded key must be configured after the certificates using a separate key file.

Search for updating extensions conf:

updating extensions conf-60updating extensions conf-74

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “updating extensions conf”