apache server configuration
I made a PHP applet yesterday and wanted to run it locally to test it, but my work computer didn’t have an installation environment, so I downloaded a wamp and everything went smoothly, including Apache, Mysql, and PHP. Start the wamp service, enter "http://localhost" in the browser, the access is normal, and the wamp homepage pops up. Therefore, I want to configure my own CrashServer website into Apache and test it by accessing it locally through a virtual domain name. As a result, I encountered a lot of problems. After researching on Google today, I finally found that both Ren and Du are connected.
1. First of all, Apache’s configuration files are httpd.conf and httpd-vhosts.conf. Let’s first look at the default configuration of httpd.conf after wamp is installed.
file:///C:/Users/ADMINI~1/AppData/Local/Temp/msohtmlclip1/01/clip_image001.gif
DocumentRoot"d:/wamp/www/"
AllowOverride none
Require all denied
Options Indexes FollowSymLinks
AllowOverride all
Require local
#Virtual hosts
#Include conf/extra/httpd-vhosts.conf file:///C:/Users/ADMINI~1/AppData/Local/Temp/msohtmlclip1/01/clip_image001.gif
To access through a virtual domain name website, you need to configure httpd-vhosts.conf. Then you need to start httpd-vhosts.conf, because it is closed by default, so remove the # in front of #Include conf/extra/httpd-vhosts.conf in the configuration file. So httpd-vhosts.conf is enabled, then we edit the httpd-vhosts.conf file.
2. The location of the httpd-vhosts.conf file is in conf/extra in the apache directory. The Include conf/extra/httpd-vhosts.conf above actually tells you its location.
In this file, add the configuration of my CrashServer website above:
NameVirtualHost*:80
DocumentRoot "D:/wamp/www/CrashServer"
ServerName crash.com
First of all, my CrashServer is placed under wamp/www, which is the default website directory of wamp. Secondly, I want to use crash.com to access the CrashServer when testing locally, so the configuration is as above.
Here, in order for us to access the local site through crash.com, we need to modify the hosts file and add 127.0.0.1 crash.com.
At this point, the configuration is complete, so I restarted Apache, entered crash.com to access, and the result was normal access. However, when accessing with localhost, the homepage of wamp originally appeared, but now CrashServer is displayed, so we need to add 127.0.0.1 localhost to hosts, and add the localhost site configuration to httpd-vhosts.conf. Now This is what it looks like:
NameVirtualHost*:80
DocumentRoot "D:/wamp/www"
ServerName localhost DocumentRoot" D:/wamp/www/CrashServer"
ServerName crash.com
OK, this is basically the end. The website is configured and it looks very, very simple. But this is not the case for me. I encountered the following problem yesterday.
First of all, my CrashServer was not placed under wamp/www at the beginning, but under E:360Downloads, so I had the following configuration:
DocumentRoot"E: /360Downloads/CrashServer"
ServerName crash.com
This is correct, the path is correct, and the virtual domain name is also correct, but when accessing it, it prompts 403 Forbidden, no permission. So Google, oh, realized that it wanted to add permissions to the CrashServer directory, so it modified the configuration as follows:
DocumentRoot "E:/360Downloads/CrashServer"
ServerName crash.com
Order Allow,Deny
Allow from All
Require all granted
Restart Apache and access is normal. First of all, the new Directory can be added in httpd.conf or httpd-vhosts.conf. I think it is better to add it in the latter. The configuration content is clearer and the project directory permissions follow the project. Site configuration. In the newly added Directory above, we have added permissions to the CrashServer directory under 360Downloads and allowed access, so we no longer prompt 403 Forbidden.
This problem is so simple and easy to write now, but when the problem occurs, it is very disturbing and depressing. For projects outside wamp/www, you need to give the project directory permissions. Note:
OrderAllow, Deny
Allow from All
Requireall granted
These three items are indispensable. This is configured to allow external computers to access the server. site.
3. After solving the problem today, I thought of accessing my site through other devices under the same LAN, so I used my mobile phone to enter my computer’s IP in the browser, but it couldn’t be accessed. I Googled it again, and it turned out that I needed to modify httpd.conf. Configuration in:
Options Indexes FollowSymLinks
AllowOverride all
Require local
Among them, Require local, not Google, but look As I know the name, it only allows local access, so I changed it to Require all granted, allowing all requested access, and the mobile phone can access it.
Reference, http://roteg.iteye.com/blog/1465380, here is an explanation of access verification configuration.
Here, there is a configuration blog post written by a foreigner, which is very good, https://www.kristengrote.com/blog/articles/how-to-set-up-virtual-hosts-using-wamp#wamp-step-7 , but the only thing is that in his Step 7, add permissions to the project directory:
Order Deny,Allow
Allow from all
< ;/Directory>
But Require all granted is missing, resulting in 403 Forbidden in the end. Require all granted is only required in 2.4 and not required in 2.2.
This makes it understandable why some of the technical articles published by Google mention require all granted, while others do not.
This configuration is performed in the following wamp environment:
![]() At this point, configuring the PHP site under Apache is complete. If you encounter any technical problems that are not solved in time during the learning process, we recommend a good WeChat public account: [Tuosheng Technology], and professional technicians will solve it for you. [Tuosheng Technology] focuses on sharing the most comprehensive video learning materials and learning experiences on programming development. At present, teaching videos for Java, Android, UID, PHP, iOS, etc. have been compiled,
|

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











Session hijacking can be achieved through the following steps: 1. Obtain the session ID, 2. Use the session ID, 3. Keep the session active. The methods to prevent session hijacking in PHP include: 1. Use the session_regenerate_id() function to regenerate the session ID, 2. Store session data through the database, 3. Ensure that all session data is transmitted through HTTPS.

There are four main error types in PHP: 1.Notice: the slightest, will not interrupt the program, such as accessing undefined variables; 2. Warning: serious than Notice, will not terminate the program, such as containing no files; 3. FatalError: the most serious, will terminate the program, such as calling no function; 4. ParseError: syntax error, will prevent the program from being executed, such as forgetting to add the end tag.

PHP and Python each have their own advantages, and choose according to project requirements. 1.PHP is suitable for web development, especially for rapid development and maintenance of websites. 2. Python is suitable for data science, machine learning and artificial intelligence, with concise syntax and suitable for beginners.

HTTP request methods include GET, POST, PUT and DELETE, which are used to obtain, submit, update and delete resources respectively. 1. The GET method is used to obtain resources and is suitable for read operations. 2. The POST method is used to submit data and is often used to create new resources. 3. The PUT method is used to update resources and is suitable for complete updates. 4. The DELETE method is used to delete resources and is suitable for deletion operations.

In PHP, password_hash and password_verify functions should be used to implement secure password hashing, and MD5 or SHA1 should not be used. 1) password_hash generates a hash containing salt values to enhance security. 2) Password_verify verify password and ensure security by comparing hash values. 3) MD5 and SHA1 are vulnerable and lack salt values, and are not suitable for modern password security.

PHP is a scripting language widely used on the server side, especially suitable for web development. 1.PHP can embed HTML, process HTTP requests and responses, and supports a variety of databases. 2.PHP is used to generate dynamic web content, process form data, access databases, etc., with strong community support and open source resources. 3. PHP is an interpreted language, and the execution process includes lexical analysis, grammatical analysis, compilation and execution. 4.PHP can be combined with MySQL for advanced applications such as user registration systems. 5. When debugging PHP, you can use functions such as error_reporting() and var_dump(). 6. Optimize PHP code to use caching mechanisms, optimize database queries and use built-in functions. 7

The arrow function was introduced in PHP7.4 and is a simplified form of short closures. 1) They are defined using the => operator, omitting function and use keywords. 2) The arrow function automatically captures the current scope variable without the use keyword. 3) They are often used in callback functions and short calculations to improve code simplicity and readability.

PHP is widely used in e-commerce, content management systems and API development. 1) E-commerce: used for shopping cart function and payment processing. 2) Content management system: used for dynamic content generation and user management. 3) API development: used for RESTful API development and API security. Through performance optimization and best practices, the efficiency and maintainability of PHP applications are improved.
