Difference between revisions of "Apache"
|Line 16:||Line 16:|
In yum, Apache is distributed under the package name '''
In yum, Apache is distributed under the package name '''''' (for ''hypertext transfer protocol daemon''). Use the package manager associated with your distribution to install Apache. (For more information on how to use yum, see [[Linux#Repository-Based Package Managers|the Linux guide]].)
Revision as of 15:01, 25 January 2019
Apache is the industry standard web server for Linux distributions. It is highly configurable and has a wide range of modules ready for different needs.
What is a web server?
A web server is software that listens for connections to your machine, and when a connection is receive, processes the request and responds with the appropriate information. Most web servers listen on port 80, which is reserved for the purpose, and use the HTTP protocol.
For example, when you visit this wiki, you are sending a request over the internet to some machine that is probably located somewhere in EIT (the user seldom knows exactly where the machine is located). The web server receives your request, and it processes the data you sent. Finally, the server prepares a response (the web page), and sends it back to you.
You define your settings for Apache using directives. Some of the directives you will likely encounter include:
- DocumentRoot: The path to the directory where the top level web files are going to be stored.
- IfModule: The following block would be included if specified module exists.
- User: Which user apache2 will run as.
- Group: Which group will have group access to default web files.
- AccessFileName: The name of the access file (that specifies user names/passwords and other limitations to files/directories).
- ErrorLog: Where any errors will be written.
- Include: Include some other files.
- LogFormat: How to write a log message.
- ErrorDocument: Files to display for some HTTP errors (500, 404, 402 etc.).
- Alias: Map a directory URL to some other location on your filesystem. Requires that the Alias module be loaded.
You can also specify some Apache configurations without delving into the master configuration file. To do this, put a file named .htaccess in any directory that Apache is serving. All directives in it will be interpreted as if they were in a Directory directive in the master configuration file.
VERY IMPORTANT: The directory containing .htaccess must not have the AllowOverride None directive in the master configuration file in order for .htaccess to be read.
Use the Directory directive to assign other directives to a specific directory. For example:
<Directory /var/www/> Options Indexes FollowSymLinks AllowOverride None Order allow,deny allow from all RedirectMatch ^/$ /apache2-default/ </Directory>
This sets options for the /var/www directory.
- The Options directive says that:
- If no index page is present in a directory, display a directory index page instead
- Apache will follow symbolic links in the directory
- AllowOverride None says that .htaccess files cannot alter the Apache options in this directory and all sub-directories
- Order allow,deny and Allow from all specifies that anybody is allowed to access this server via HTTP.
Note that this directory is actually the root directory of the web server.
The UserDir Module
If you want to change the name of the UserDir web server root from public_html to something else like .html, follow these instructions. (You do not need to do this for the purposes of CSE 330; this serves as a reference.)
- Rename your public_html to .html
- The "." in front of the directory name means that the directory is a hidden one. You will not see it with the normal "ls" command. Use "ls -a" to see hidden files as well.
- Edit the UserDir configuration file.
- In RHEL, edit the userDir configuration file at /etc/httpd/conf.d/userdir.conf
- Find the line that reads
UserDir public_htmland change it to
- Restart Apache.
Apache creates two log files: one for all access attempts to your server, and one for errors. The locations of these log files are:
- Access Log: /var/log/httpd/access_log
- Error Log: /var/log/httpd/error_log
You might find it helpful to see access and errors appear "live" in your terminal window as they are created. To do this, you can use the tail -f command. Since the log files have strict permissions, you will need to also use sudo. Example:
$ sudo tail -f /var/log/httpd/access_log
Virtual Hosts are used to run multiple Apache web servers from the same machine. Virtual hosts can listen for connections on different ports and/or different hostnames, serving completely different web sites to each. For example:
<VirtualHost cse330.dyndns.org> ServerAdmin webmaster@localhost ServerName cse330.dyndns.org DocumentRoot /home/www/cse330/ ErrorLog /var/log/httpd/error_log LogLevel warn CustomLog /var/log/apache2/access_log combined ServerSignature On </VirtualHost>
This configuration enables any requests that use a host name of cse330.dyndns.org will use /home/www/cse330 as the root document directory. Make sure that the DocumentRoot directory exists and is readable by the httpd process. In RHEL, Apache runs as the apache user.
It is good practice to put raw server configuration files in /etc/httpd/sites-available. To activate a site, create a symlink from the configuration in sites-available to a sibling directory called sites-enabled.
Restarting Apache and Testing
Whenever you make changes to the Apache configuration files, you will need to restart Apache for the changes to take effect. There are several different ways to restart Apache; they all functionally do (almost) the same thing, so choose your favorite:
$ sudo /usr/sbin/apachectl restart $ sudo apachectl restart # if /usr/sbin is in your PATH (which it is *not* by default in RHEL) $ sudo /etc/init.d/httpd restart $ sudo /sbin/service httpd restart $ sudo service httpd restart
If you're torn for which version is the "best" to use, the commands involving apachectl (think "Apache Control") are written by the Apache folks themselves. This has a couple advantages:
- They show you errors in the startup process (if there are any)
- They give you the option to perform a "soft" restart; that is, a restart that allows any pending connections to complete. To perform a soft restart, use graceful:
sudo apachectl graceful
In my anecdotal experience, the apachectl commands are also faster than the service or init.d commands.
To make sure everything is working, create a test file in your home directory under public_html, and then point your browser to it: http://ec2-xxx-xx-xx-xxx.compute-1.amazonaws.com/~yourUserName/hello.txt