HTTPD Configuration For PHP Website Development
INTRODUCTION
Apache HTTP Server is configured by placing directives in plain text configuration files. The main configuration file is usually called httpd.conf. The location of this file is set at compile-time, but may be overridden with the -f command line flag. In addition, other configuration files may be added using the Include directive, and wildcards can be used to include many configuration files. Any directive may be placed in any of these configuration files. Changes to the main configuration files are only recognized by httpd when it is started or restarted.
Read http://httpd.apache.org/docs/current/configuring.html
Read http://www.thegeekstuff.com/2008/08/9-tips-to-use-apachectl-and-httpd-like-a-power-user/
PREPARATION
This tutorial uses UwAmp server package.
Set the Text Editor value as the path pointing to Notepad++ program.
STEPS
1) FINDING HTTPD CONFIG FILE.
Click the Source File button besides the Apache Config button in the Configuration Section of UwAmp.
2) EDITING HTTPD CONFIG FILE.
(If you have configured UwAmp to use Notepad++ to edit the text file, ) Notepad++ shows the content of Apache Config file ie, httpd.conf
Note: The location shown by the Notepad++ title bar is C:\UwAmp\bin\apache\conf\httpd_uwamp.conf. This path may differ subject to the location where UwAmp is stored.
3) SYNTAX.
httpd configuration files contain one directive per line. The backslash "\" may be used as the last character on a line to indicate that the directive continues onto the next line. There must be no other characters or white space between the backslash and the end of the line.
Arguments to directives are separated by whitespace. If an argument contains spaces, you must enclose that argument in quotes.
Directives in the configuration files are case-insensitive, but arguments to directives are often case sensitive. Lines that begin with the hash character "#" are considered comments, and are ignored. Comments may not be included on a line after a configuration directive. Blank lines and white space occurring before a directive are ignored, so you may indent directives for clarity.
4) MODULES.
httpd is a modular server. This implies that only the most basic functionality is included in the core server. Extended features are available through modules which can be loaded into httpd. By default, a base set of modules is included in the server at compile-time. If the server is compiled to use dynamically loaded modules, then modules can be compiled separately and added at any time using the LoadModule directive. Otherwise, httpd must be recompiled to add or remove modules. Configuration directives may be included conditional on a presence of a particular module by enclosing them in an <IfModule> block. However, <IfModule> blocks are not required, and in some cases may mask the fact that you're missing an important module.
5) SCOPE OF DIRECTIVES.
Directives placed in the main configuration files apply to the entire server. If you wish to change the configuration for only a part of the server, you can scope your directives by placing them in <Directory>, <DirectoryMatch>, <Files>, <FilesMatch>, <Location>, and <LocationMatch> sections. These sections limit the application of the directives which they enclose to particular filesystem locations or URLs. They can also be nested, allowing for very fine grained configuration.
httpd has the capability to serve many different websites simultaneously. This is called Virtual Hosting. Directives can also be scoped by placing them inside <VirtualHost> sections, so that they will only apply to requests for a particular website.
6) PHP Configuration.
6a) Registering PHP interpreter.
6b) Registering valid file extension for PHP Interpreter to execute.
7) UWAMP ADDITIONAL SETTINGS
Filename: C:\UwAmp\UwAmp README
_ _ ___ | | | | / _ \ | | | |_ _/ /_\ \_ __ ___ _ __ | | | \ \ /\ / / _ | '_ ` _ \| '_ \ | |_| |\ V V /| | | | | | | | | |_) | \___/ \_/\_/ \_| |_/_| |_| |_| .__/ | | |_| 01010101 01110111 01000001 01101101 01110000 V 2.2.1 www.uwamp.com -------------------------------------------- Apache config file : UwAmp\bin\apache\conf\httpd_uwamp.conf PHP config file : UwAmp\bin\php\CURRENT PHP VERSION\php_uwamp.ini
MYSQL config file : UwAmp\bin\database\mysql\my_uwamp.ini MYSQL PASSWORD : user : root password : root Available Macro in setting: {TEMPPATH} = UwAmp\temp {APACHEPATH} = UwAmp\bin\apache {DOCUMENTPATH} = UwAmp\www {PHPAPPS} = UwAMp\phpapps {PHPPATH} = UwAmp\bin\php\CURRENT PHP IN UWAMP CONTROL\ {PHPAPACHE2FILE} = UwAmp\bin\php\CURRENT PHP IN UWAMP CONTROL\CURRENT apache2.dll {PHPEXTPATH} = UwAmp\bin\php\CURRENT PHP IN UWAMP CONTROL\ext {PHPZENDPATH} = UwAmp\bin\php\CURRENT PHP IN UWAMP CONTROL\zend_ext {PHPMODULENAME} = Module name of current php version {LISTEN_VIRTUAL_HOST_PORT} = Apache Listens ports {MYSQLPATH} = UwAmp\bin\database\mysql\ {MYSQLBINPATH} = UwAmp\bin\database\mysql\bin {MYSQLDATAPATH} = UwAmp\bin\database\mysql\data {ONLINE_MODE} = Order allow,deny Allow from all OR = Order deny,allow Allow from 127.0.0.1 localhost if ONLINE_MODE is set to Online the serveur is available for all IP if ONLINE_MODE is set to Offline the serveur is available just for 127.0.0.1 |
8) FURTHER EXERCISE
Check the httpd file for XAMPP for the above items.
8.1) httpd.conf
https://docs.google.com/document/d/1Zsa_2bZ2mTFW_Z3QbCZiKewcphccDo_PM5nQqwPaaus/edit?usp=sharing
8.2) httpd-xampp.conf
https://docs.google.com/document/d/1URVLb9L9myOe8liKUkSZBqdgV2yEICBrq7p2bq32s5Y/edit?usp=sharing