Home
HSLAB HTTP Monitor Online Help Prev Page Prev Page
HSLAB HTTP Monitor Help System
What's new
What is it
System Requirements
Handy Software Lab Products FAQ
Before You Begin
How it works
Why This Software?
Work With the Program
Main Window
Server Status
Connection and Network Statistics
Content Statistics
Detailed Statistics for Virtual Server (Table)
Virtual Server Connections Distribution
Server Operation
Server Operation Distribution
Countries
Connections by Country
Connections by Host
Monitor Options
Apache Configuration Wizard
Connections Data
Server Profiles
Threshold and Alarms
Advanced Filtering Options
Simple Regexp Syntax
Regular Expressions
Related Apache Documents
Apache Core Features
Module mod_status
Access Control by URL
Apache's Handler Use
Apache Performance Notes
Contacts
Company
Support
Report a bug
License Agreement and Registration
END-USER LICENSE AGREEMENT FOR THIS SOFTWARE
Distribution of Evaluation Version
Why Register?
Unregistered version limitations
Register Online
Enter Registration Code
Related Information
Comma-separated values
Enabling Status Support
Apache HTTP Server

Apache HTTP Server Version 1.3

What is a Handler

A "handler" is an internal Apache representation of the action to be performed when a file is called. Generally, files have implicit handlers, based on the file type. Normally, all files are simply served by the server, but certain file typed are "handled" separately. For example, you may use a type of "application/x-httpd-cgi" to invoke CGI scripts.

Apache 1.1 adds the additional ability to use handlers explicitly. Either based on filename extensions or on location, these handlers are unrelated to file type. This is advantageous both because it is a more elegant solution, but it also allows for both a type and a handler to be associated with a file (See also Files with Multiple Extensions)

Handlers can either be built into the server or to a module, or they can be added with the Action directive. The built-in handlers in the standard distribution are as follows:

·server-status: Get the server's status report (mod_status

Directives


AddHandler

Syntax: AddHandler handler-name extension extension...

Context: server config, virtual host, directory, .htaccess

FileInfo

Status: Base

Module: mod_mime

Compatibility: AddHandler is only available in Apache 1.1 and later

AddHandler maps the filename extensions extension to the handler . This mapping is added to any already in force, overriding any mappings that already exist for the same extension. For example, to activate CGI scripts with the file extension "", you might use:

    AddHandler cgi-script cgi

Once that has been put into your srm.conf or httpd.conf file, any file containing the ".cgi" extension will be treated as a CGI program.

See also: Files with multiple extensions


SetHandler

Syntax: SetHandler handler-name

Context: directory, .htaccess

Status: Base

Module: mod_mime

Compatibility: SetHandler is only available in Apache 1.1 and later.

When placed into an .htaccess file or a <Directory> or <Location> section, this directive forces all matching files to be parsed through the handler given by . For example, if you had a directory you wanted to be parsed entirely as imagemap rule files, regardless of extension, you might put the following into an .htaccess file in that directory:

    SetHandler imap-file

Another example: if you wanted to have the server display a status report whenever a URL of http://servername/status was called, you might put the following into access.conf:

    <Location /status>

    SetHandler server-status

    </Location>


The CHM file was converted to HTML by chm2web software.