[UNIT 1 <Continued>]: <Understanding Apache>

Size: px

Start display at page:

Download "[UNIT 1 <Continued>]: <Understanding Apache>"

Stewart Harper
5 years ago
Views:

[UNIT 1 <Continued>]: <Understanding Apache> Directives DocumentRoot This directive specifies the root directory of the server s content hierarchy, Syntax DocumentRoot dir Where dir is the directory

1 [UNIT 1 <Continued>]: <Understanding Apache> Directives DocumentRoot This directive specifies the root directory of the server s content hierarchy, Syntax DocumentRoot dir Where dir is the directory s absolute pathname, it can be whatever you like, but remember that the user that Apache runs as must have read access to all files and executable access to all it s directories in the hierarchy The Documentroot directive is valid in the server config and virtual host contexts DirectoryIndex UserDir This directive specifies which file is served when the user requests a directory. DirectoryIndex file [file ] Where the file specifies the file to be served. Each file is tried in order until a match is found For example, if you wrote most of your site in PHP but some parts were pure HTML, you might use this: DirectoryIndex index.php index.html If none of the file can be found (Or the directive is missing), the contents of the directory are displayed as specified in the IndexOptions directive The name index is standard but arbitrary The DirectoryIndex directive is valid in the server config and virtual host contexts This directive controls whether users may publish content from their own home directories UserDir dir disabled enabled users Where dir is the name of the directory that will be published, provided of course that it it is in the user s home directory. If dir isn t specified then it defaults to ~/public_html 1

The disabled keyword prevents content from being published from user s home directories, and enabled allows you to chose from which user s home directories content may be served.

2 The disabled keyword prevents content from being published from user s home directories, and enabled allows you to chose from which user s home directories content may be served. Multiple users names are separated by spaces Using multiple UserDir directives combines their effect To display the user published content, users must visit the site s URL followed by /~ and the user s username The UserDir is valid in the server config and virtual host contexts Changing Document Root= /var/www/html/jesse /var/www/html/jesse/index.html = <html> <h1>it Works!</h1> </html> It works!! 2

Website Location= /var/www/html/jesse Two Types of Errors Configuration Error A error in the configuration will immediately be displayed when you

3 Website Location= /var/www/html/jesse Two Types of Errors Configuration Error A error in the configuration will immediately be displayed when you restart the Apache service Client Human Error When the Configuration Path to a resource is set correctly for example and the Client types in the wrong path, 3

4 Logging Directives Three directives are used to configure Apache s logging ErrorLog This directive specifies where Apache s error messages are to be sent ErrorLog file syslog[:facility] Where file specifies the name of the file to which errors are logged. The syslog keyword specifies that errors are to be logged via the syslog service using the optional facility (which defaults to local7 ). Sysconfig Mai Kernel Daemon The ErrorLog directive is valid in the server config and virtual host contexts LogLevel This directive specifies the level of error messages to be logged LogLevel level Where level is one of eight values, ranging from debug (Least severe) to emerg (Most severe). Errors at level or higher are logged The LogLevel directive is valid in the server config and virtual host contexts CustomLog This directive is used to specify a customized log file for non error messages. CustomLog file format Where file specifies the file to which the logs are written, and format specifies the format. It can either specify the nickname of a format defined using a LogFormat directive, or an explicit format string. In addition to literal characters, the format string may contain one or more formatting directives. These are introduced using the % character, and examples include: %v The canonical name of the server serving the request %h The remote host s hostname %s The status of the request 4

5 See the Apache documentation for more details of these and many more formatting directives The CustomLog directive is valid in the server config and virtual host contexts 5

6 Content Control Directives There are a number of directives that enable the users to control how various content is handled. The following is a partial list ErrorDocument This directive specifies the action taken by Apache when the specified error occurs ErrorDocument code action Where code is the error code for which this directive defines a response, and action is the action to be taken The action may be one of the following: A literal text string The absolute pathname of a file containing a script or other content to which the client is redirected A URI that points to an external script or other content to which the client is redirected The ErrorDocument directive is valid in all four contexts IndexOptions This directive specifies how Apache displays directory listings IndexOptions [+ ]option [...] Where option is one or more indexing option(s), some of which are: FancyIndexing Displays index with clickable headings IgnoreCase Ignores case with sorting names NameWidth=n Sets the width of the filename column to n characters The IndexOptions directive is valid in all four contexts ServerTokens This directive specifies what server information is returned to clients ServerTokens token Where token is one of the following Prod Returns the product name, eg., Apache 6

7 Major Returns the major release number eg., Apache/2 Minor Returns the major and minor release numbers, eg., Apache/2.4 Min Returns the complete version, eg., Apache/2.4.6 OS Returns the name of the host operating system, in addition to the complete version, e.g., Apache/2.4.6 (CentOS) Full This is the same as the OS except it also sends the name and version numbers of non ASF modules, e.g., Apache/2.4.6 (CentOS) PHP/ The ServerTokens directive is valid only in the server config context ServerSignature This directive adds a line to server generated pages ServerSignature On Off The value On turns on the signature line, which has the format specified by the ServerTokens directive, and the name specified by the VirtualHost container The value Off turns off the server signature The value is the same as On, except that the server s name is a clickable mailto: link to the server s administrator, as specified by the ServerAdmin directive The ServerSignature directive is valid in all four contexts 7

8 Configuration Directives The next set of directives control Apache s configuration. They include: User Group Options This directive specifies the UID of the Apache processes User username #userid Where username is the name of the local [user, and #userid is a UID value The User directive is valid only in the server config context Much like the User directive, this directive specifies the HUI of the Apache process Group groupname #groupid Where groupname is the name of a local group, and #groupid is a GID value The group directive is valid only in the server config context This directive controls server features by directory Options [+ ]option [...] Where option specifies one or more options, which include None None of the features controlled by the directive are enabled All All of the features controlled by the directive are enables Includes Permit the use of SSL (server side includes), which are containers embedded within HTML that are evaluated on the server before the contents is passed to the client IncludesNOEXEC The same as includes, but disables the #exec and #exec cgi commands Indexes 8

9 Generates a directory listing if the DirectoryIndex directive is not set The Options directive is valid only in the directory context Security Directives 9

A PAtCHy server: developed by the Apache group formed 2/95 around by a number of people who provided patch files for NCSA httpd 1.3 by Rob McCool.

A PAtCHy server: developed by the Apache group formed 2/95 around by a number of people who provided patch files for NCSA httpd 1.3 by Rob McCool. Outline q Introduction to Apache httpd web server q Basic Compilation, Installation and Configuration q Apache File system q Apache Logging & Status q Security & Performance Features q Virtual Hosting