This complex directive uses a colon-separated “cipher-spec” string consisting of OpenSSL cipher specifications to configure the cipher suite that the client negotiates in the SSL handshake phase.

Note: This is the global SSLCipherSuite setting. You can also set SSLCipherSuite in other contexts (for example, a VirtualHost). In that context, it would override the global setting. This can cause PCI scans to fail port 443 even if SSLCipherSuite is set appropriately in this interface. For information on how to check for that situation and address it, click here.

This complex directive uses a space-separated string consisting of protocol specifications to configure the SSL and TLS protocols that the client and server negotiate in the SSL/TLS handshake phase.

Note: This is the global SSLProtocol setting. You can also set SSLProtocol in other contexts (for example, a VirtualHost). In that context, it would override the global setting. This can cause PCI scans to fail port 443 even if SSLProtocol is set appropriately in this interface.

To ensure compatibility with all clients, we recommend that you enable TLSv1.2.

This option enables OCSP stapling. If enabled (and requested by the client), an OCSP response for its own certificate will be included in the TLS handshake.

This directive enables the display of additional information about incoming requests on the Apache status page.

This directive adjusts the verbosity of the messages recorded in the error logs. Values below 'info' are not recommended for production systems.

Warning: do not change this unless you know the impact of doing so. Stats may be wrong if you set this improperly.

Warning: do not change this unless you know the impact of doing so. Stats may be wrong if you set this improperly.

This directive sets the behavior of TRACE requests for both the core server and mod_proxy.

This “signature” is the trailing footer line under server-generated documents (error messages, information pages, etc).

• Product Only (e.g. “Apache”)
• Minimal (e.g Apache/2.4.52)
• OS (e.g Apache/2.4.52 (Unix))
• Full (e.g Apache/2.4.52 (Unix) MyModX/1.3 MyModY/1.4)

This directive configures the file attributes that are used to create the ETag response header field when the request is file based.

Note: “None” means that if a document is file based, no ETag field will be included in the response.

This directive’s values enable or disable various features of Apache. It is recommended that you thoroughly read the documentation before changing any of its values to avoid inadvertently disabling features on which your customers may rely.

Note: These settings can be overridden in other contexts that have their own Options directive.

This directive sets the number of child server processes created on startup. Since the number of processes is dynamically controlled depending on the load, there is usually little reason to adjust this parameter.

This directive sets the desired minimum number of idle child server processes. Tuning of this parameter should only be necessary on very busy sites.

This directive sets the desired maximum number of idle child server processes. Tuning of this parameter should only be necessary on very busy sites.

This directive sets the maximum configured value for MaxClients for the lifetime of the Apache process.

Special care must be taken when using this directive. If ServerLimit is set to a value much higher than necessary, extra, unused shared memory will be allocated. If both ServerLimit and MaxClients are set to values higher than the system can handle, Apache may not start or the system may become unstable.

We highly recommend using the default setting unless you fully understand how it will interact with your Apache build and MaxClients setting.

This directive sets the limit on the number of simultaneous requests that will be served. This interface allows up to the value of the ServerLimit setting. This used to be called 'MaxClients' prior to Apache 2.4.

This directive sets the limit on the number of requests that an individual child server process will handle.

After MaxConnectionsPerChild requests, the child process will die. If MaxConnectionsPerChild is 0, then the process will never expire. This used to be called 'MaxRequestsPerChild' prior to Apache 2.4.

This directive enables persistent HTTP connections.

This directive sets the amount of time the server will wait for subsequent requests on a persistent connection.

This directive sets the number of requests allowed on a persistent connection.

This directive sets the amount of time the server will wait for certain events before failing a request.

This directive enables symlink protection in order to reduce the impact of race conditions if you enable the FollowSymlinks and SymLinksIfOwnerMatch Apache directives.

If one or both of those directives are not in effect this directive will have unexpected behavior so it is highly recommended to leave it off in that case.

The checks this directive performs can have significant performance impacts on the server. We strongly recommend that you do not enable this feature unless you absolutely require it.