add UseCanonicalName On to retain the old behavior. The module mod_userdir will no longer act on requests unless a UserDir directive specifying a directory name is present in the config file. To restore to specify an optional timeout, after which httpd will terminate regardless of the status of any requests being served. Proxying The new mod_proxy_balancer module provides load balancing services for added. Event MPM The event MPM uses a separate thread to handle Keep Alive requests and accepting connections. Keep Alive requests have traditionally required httpd to dedicate a worker to handle it. This

add UseCanonicalName On to retain the old behavior. The module mod_userdir will no longer act on requests unless a UserDir directive specifying a directory name is present in the config file. To restore to specify an optional timeout, after which httpd will terminate regardless of the status of any requests being served. Proxying The new mod_proxy_balancer module provides load balancing services for added. Event MPM The event MPM uses a separate thread to handle Keep Alive requests and accepting connections. Keep Alive requests have traditionally required httpd to dedicate a worker to handle it. This

add UseCanonicalName On to retain the old behavior. The module mod_userdir will no longer act on requests unless a UserDir directive specifying a directory name is present in the config file. To restore to specify an optional timeout, after which httpd will terminate regardless of the status of any requests being served. Proxying The new mod_proxy_balancer module provides load balancing services for added. Event MPM The event MPM uses a separate thread to handle Keep Alive requests and accepting connections. Keep Alive requests have traditionally required httpd to dedicate a worker to handle it. This

add UseCanonicalName On to retain the old behavior. The module mod_userdir will no longer act on requests unless a UserDir directive specifying a directory name is present in the config file. To restore to specify an optional timeout, after which httpd will terminate regardless of the status of any requests being served. Proxying The new mod_proxy_balancer module provides load balancing services for added. Event MPM The event MPM uses a separate thread to handle Keep Alive requests and accepting connections. Keep Alive requests have traditionally required httpd to dedicate a worker to handle it. This

add UseCanonicalName On to retain the old behavior. The module mod_userdir will no longer act on requests unless a UserDir directive specifying a directory name is present in the config file. To restore to specify an optional timeout, after which httpd will terminate regardless of the status of any requests being served. Proxying The new mod_proxy_balancer module provides load balancing services for added. Event MPM The event MPM uses a separate thread to handle Keep Alive requests and accepting connections. Keep Alive requests have traditionally required httpd to dedicate a worker to handle it. This

In 2.2, access control based on client hostname, IP address, and other characteristics of client requests was done using the directives Order, Allow, Deny, and Satisfy. In 2.4, such access control is done authentication and all requests are denied. 2.2 configuration: Order deny,allow Deny from all 2.4 configuration: Require all denied In this example, there is no authentication and all requests are allowed. were meaningfully combined, the access control directives should be migrated. This example allows requests meeting both criteria: 2.2 configuration: Order allow,deny Deny from all # Satisfy ALL is the

In 2.2, access control based on client hostname, IP address, and other characteristics of client requests was done using the directives Order, Allow, Deny, and Satisfy. In 2.4, such access control is done control. In this example, all requests are denied. 2.2 configuration: Order deny,allow Deny from all 2.4 configuration: Require all denied In this example, all requests are allowed. 2.2 configuration: longer supported. SSLProxyCheckPeerCN and SSLProxyCheckPeerExpire now default to On, causing proxy requests to HTTPS hosts with bad or outdated certificates to fail with a 502 status code (Bad gateway) htpasswd

In 2.2, access control based on client hostname, IP address, and other characteristics of client requests was done using the directives Order, Allow, Deny, and Satisfy. In 2.4, such access control is done control. In this example, all requests are denied. 2.2 configuration: Order deny,allow Deny from all 2.4 configuration: Require all denied In this example, all requests are allowed. 2.2 configuration: longer supported. SSLProxyCheckPeerCN and SSLProxyCheckPeerExpire now default to On, causing proxy requests to HTTPS hosts with bad or outdated certificates to fail with a 502 status code (Bad gateway) htpasswd

In 2.2, access control based on client hostname, IP address, and other characteristics of client requests was done using the directives Order, Allow, Deny, and Satisfy. In 2.4, such access control is done authentication and all requests are denied. 2.2 configuration: Order deny,allow Deny from all 2.4 configuration: Require all denied In this example, there is no authentication and all requests are allowed. were meaningfully combined, the access control directives should be migrated. This example allows requests meeting both criteria: 2.2 configuration: Order allow,deny Deny from all # Satisfy ALL is the

In 2.2, access control based on client hostname, IP address, and other characteristics of client requests was done using the directives Order, Allow, Deny, and Satisfy. In 2.4, such access control is done control. In this example, all requests are denied. 2.2 configuration: Order deny,allow Deny from all 2.4 configuration: Require all denied In this example, all requests are allowed. 2.2 configuration: longer supported. SSLProxyCheckPeerCN and SSLProxyCheckPeerExpire now default to On, causing proxy requests to HTTPS hosts with bad or outdated certificates to fail with a 502 status code (Bad gateway) htpasswd