This module processes .map files, thereby
replacing the functionality of the imagemap CGI
program. Any directory or document type configured to use the
handler imap-file (using either
will be processed by this module.
The following directive will activate files ending with
.map as imagemap files:
AddHandler imap-file map
Note that the following is still supported:
AddType application/x-httpd-imap map
However, we are trying to phase out "magic MIME types" so we
are deprecating this method.
The lines in the imagemap files can have one of several
directive value [x,y ...]
directive value "Menu text" [x,y
directive value x,y ... "Menu text"
The directive is one of base,
default, poly, circle,
rect, or point. The value is an
absolute or relative URL, or one of the special values listed
below. The coordinates are x,y
pairs separated by whitespace. The quoted text is used as the text of
the link if a imagemap menu is generated. Lines beginning with '#' are
There are six directives allowed in the imagemap file. The
directives can come in any order, but are processed in the
order they are found in the imagemap file.
Has the effect of <base href="value">
. The non-absolute URLs of the map-file are taken relative
to this value. The base directive overrides
ImapBase as set in a
.htaccess file or in the server configuration files.
In the absence of an ImapBase configuration
directive, base defaults to
base_uri is synonymous with base.
Note that a trailing slash on the URL is significant.
The action taken if the coordinates given do not fit any
of the poly, circle or
rect directives, and there are no
point directives. Defaults to nocontent
in the absence of an ImapDefault configuration setting, causing a status
code of 204 No Content to be returned. The client
should keep the same page displayed.
Takes three to one-hundred points, and is obeyed if the
user selected coordinates fall within the polygon defined by
Takes the center coordinates of a circle and a point on
the circle. Is obeyed if the user selected point is with the
Takes the coordinates of two opposing corners of a
rectangle. Obeyed if the point selected is within this
Takes a single point. The point directive closest to the
user selected point is obeyed if no other directives are
satisfied. Note that default will not be
followed if a point directive is present and
valid coordinates are given.
A coordinate consists of an x and a y
value separated by a comma. The coordinates are separated
from each other by whitespace. To accommodate the way Lynx
handles imagemaps, should a user select the coordinate
0,0, it is as if no coordinate had been
#Comments are printed in a 'formatted' or 'semiformatted' menu.
#And can contain html tags. <hr>
poly map "Could I have a menu, please?" 0,0 0,10 10,10 10,0
rect .. 0,0 77,27 "the directory of the referer"
circle http://www.inetnebr.com/lincoln/feedback/ 195,0 305,27
rect another_file "in same directory as referer" 306,0 419,27
point http://www.zyzzyva.com/ 100,100
point http://www.tripod.com/ 200,200
rect mailto:firstname.lastname@example.org 100,150 200,0 "Bugs?"
The ImapDefault directive sets the default
default used in the imagemap files. Its value is
overridden by a default directive within the
imagemap file. If not present, the default action
is nocontent, which means that a 204 No
Content is sent to the client. In this case, the client
should continue to display the original page.
The ImapMenu directive determines the
action taken if an imagemap file is called without valid
If ImapMenu is none, no menu is generated,
and the default action is performed.
A formatted menu is the simplest menu.
Comments in the imagemap file are ignored. A level one header
is printed, then an hrule, then the links each on a separate
line. The menu has a consistent, plain look close to that of
a directory listing.
In the semiformatted menu, comments are
printed where they occur in the imagemap file. Blank lines
are turned into HTML breaks. No header or hrule is printed,
but otherwise the menu is the same as a
Comments are printed, blank lines are ignored. Nothing is
printed that does not appear in the imagemap file. All breaks
and headers must be included as comments in the imagemap
file. This gives you the most flexibility over the appearance
of your menus, but requires you to treat your map files as
HTML instead of plaintext.