Apache 2.2 2.4 difference
The settings in httpd.conf are similar and different after the Windows environment is changed from Apache2.2 to Apache2.4.
1. Change of permission setting method
2.2 Use Order Deny / Allow method, 2.4 switch to Require
apache2.2:
Order deny,allow
Deny from all
apache2.4:
Require all denied
The more commonly used ones here are as follows:
Require all denied Require all granted Require host xxx.com Require ip 192.168.1 192.168.2 Require local
Note: If there are any settings in the htaccess file, they must also be modified
2. Change the logging mode setting
RewriteLogLevel command is changed to logLevel
The first value set by LOGLEVEL is the default level for the entire Apache, followed by The logging level of this module can be modified for the specified module
For example:
LogLevel warn rewrite: warn
3, Namevirtualhost is removed
4, More modules need to be loaded
To enable Gzip, mod_deflate needs to be loaded in apache2.2, and mod_filter and mod_deflate need to be loaded in apache2.4
To enable SSL, in apache2.2 Mod_ssl needs to be loaded in, mod_socache_shmcb and mod_ssl need to be loaded in apache2.4
5. Recommended settings in the windows environment
EnableSendfile Off EnableMMAP Off
When the Log log appears It is recommended to set
AcceptFilter http none AcceptFilter https none
when there are errors such as AcceptEx failed. Note: Win32DisableAcceptEx is replaced by AcceptFilter None in apache2.4.
6, Listen setting Adjustment
Taking 443 as an example, you cannot only set Listen 443
The following error will occur:
(OS 10048) Only one communication address (protocol/network address) can be used at a time /connection): AH00072: make_sock: could not bind to address [::]:443
(OS 10048) Only one communication end address (protocol/network address/connection) can be used at a time: AH00072: make_sock: could not bind to address 0.0.0.0:443
AH00451: no listening sockets available, shutting down
AH00015: Unable to open logs
Therefore, you need to specify the listening IP, and you can set multiple
For more Apache related technical articles, please visit the Apache usage tutorial column to learn!
The above is the detailed content of Apache 2.2 2.4 difference. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

To set up a CGI directory in Apache, you need to perform the following steps: Create a CGI directory such as "cgi-bin", and grant Apache write permissions. Add the "ScriptAlias" directive block in the Apache configuration file to map the CGI directory to the "/cgi-bin" URL. Restart Apache.

When the Apache 80 port is occupied, the solution is as follows: find out the process that occupies the port and close it. Check the firewall settings to make sure Apache is not blocked. If the above method does not work, please reconfigure Apache to use a different port. Restart the Apache service.

Apache connects to a database requires the following steps: Install the database driver. Configure the web.xml file to create a connection pool. Create a JDBC data source and specify the connection settings. Use the JDBC API to access the database from Java code, including getting connections, creating statements, binding parameters, executing queries or updates, and processing results.

There are 3 ways to view the version on the Apache server: via the command line (apachectl -v or apache2ctl -v), check the server status page (http://<server IP or domain name>/server-status), or view the Apache configuration file (ServerVersion: Apache/<version number>).

The steps to start Apache are as follows: Install Apache (command: sudo apt-get install apache2 or download it from the official website) Start Apache (Linux: sudo systemctl start apache2; Windows: Right-click the "Apache2.4" service and select "Start") Check whether it has been started (Linux: sudo systemctl status apache2; Windows: Check the status of the "Apache2.4" service in the service manager) Enable boot automatically (optional, Linux: sudo systemctl

To delete an extra ServerName directive from Apache, you can take the following steps: Identify and delete the extra ServerName directive. Restart Apache to make the changes take effect. Check the configuration file to verify changes. Test the server to make sure the problem is resolved.

Apache cannot start because the following reasons may be: Configuration file syntax error. Conflict with other application ports. Permissions issue. Out of memory. Process deadlock. Daemon failure. SELinux permissions issues. Firewall problem. Software conflict.

How to view the Apache version? Start the Apache server: Use sudo service apache2 start to start the server. View version number: Use one of the following methods to view version: Command line: Run the apache2 -v command. Server Status Page: Access the default port of the Apache server (usually 80) in a web browser, and the version information is displayed at the bottom of the page.
