equivalent than the number of worker threads. The old name is still supported. The DefaultType directive no longer has any effect, other than to emit a warning if it's used with any value other than none RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single Mutex directive. You will need to evaluate any use of these removed directives in your 2.2 configuration to determine mod_ldap: LDAPTrustedClientCert is now consistently a per-directory setting only. If you use this directive, review your configuration to make sure it is present in all the necessary directory contexts. mod_filter:

equivalent than the number of worker threads. The old name is still supported. The DefaultType directive no longer has any effect, other than to emit a warning if it's used with any value other than none RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single Mutex directive. You will need to evaluate any use of these removed directives in your 2.2 configuration to determine mod_ldap: LDAPTrustedClientCert is now consistently a per-directory setting only. If you use this directive, review your configuration to make sure it is present in all the necessary directory contexts. mod_filter:

equivalent than the number of worker threads. The old name is still supported. The DefaultType directive no longer has any effect, other than to emit a warning if it's used with any value other than none RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single Mutex directive. You will need to evaluate any use of these removed directives in your 2.2 configuration to determine mod_ldap: LDAPTrustedClientCert is now consistently a per-directory setting only. If you use this directive, review your configuration to make sure it is present in all the necessary directory contexts. mod_filter:

equivalent than the number of worker threads. The old name is still supported. The DefaultType directive no longer has any effect, other than to emit a warning if it's used with any value other than none RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single Mutex directive. You will need to evaluate any use of these removed directives in your 2.2 configuration to determine mod_ldap: LDAPTrustedClientCert is now consistently a per-directory setting only. If you use this directive, review your configuration to make sure it is present in all the necessary directory contexts. mod_filter:

equivalent than the number of worker threads. The old name is still supported. The DefaultType directive no longer has any effect, other than to emit a warning if it's used with any value other than none RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single Mutex directive. You will need to evaluate any use of these removed directives in your 2.2 configuration to determine mod_ldap: LDAPTrustedClientCert is now consistently a per-directory setting only. If you use this directive, review your configuration to make sure it is present in all the necessary directory contexts. mod_filter:

equivalent than the number of worker threads. The old name is still supported. The DefaultType directive no longer has any effect, other than to emit a warning if it's used with any value other than none RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single Mutex directive. You will need to evaluate any use of these removed directives in your 2.2 configuration to determine mod_ldap: LDAPTrustedClientCert is now consistently a per-directory setting only. If you use this directive, review your configuration to make sure it is present in all the necessary directory contexts. mod_filter:

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997 12.3 Directive Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002 equivalent than the number of worker threads. The old name is still supported. • The DEFAULTTYPE directive no longer has any effect, other than to emit a warning if it’s used with any value other than none RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single MUTEX directive. You will need to evaluate any use of these removed di- rectives in your 2.2 configuration to determine

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997 12.3 Directive Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002 equivalent than the number of worker threads. The old name is still supported. • The DEFAULTTYPE directive no longer has any effect, other than to emit a warning if it’s used with any value other than none RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single MUTEX directive. You will need to evaluate any use of these removed di- rectives in your 2.2 configuration to determine

equivalent than the number of worker threads. The old name is still supported. The DefaultType directive no longer has any effect, other than to emit a warning if it's used with any value other than none RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single Mutex directive. You will need to evaluate any use of these removed directives in your 2.2 configuration to determine mod_ldap: LDAPTrustedClientCert is now consistently a per-directory setting only. If you use this directive, review your configuration to make sure it is present in all the necessary directory contexts. mod_filter:

equivalent than the number of worker threads. The old name is still supported. The DefaultType directive no longer has any effect, other than to emit a warning if it's used with any value other than none RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single Mutex directive. You will need to evaluate any use of these removed directives in your 2.2 configuration to determine mod_ldap: LDAPTrustedClientCert is now consistently a per-directory setting only. If you use this directive, review your configuration to make sure it is present in all the necessary directory contexts. mod_filter: