Uso del Manipulador de Apache

Que es un Manipulador

Modulos relacionados

Directivas relacionadas


Un "manipulador" es una representación interna de la acción desarrollada por Apache cuando un fichero es llamado. Generalmente, los ficheros tienen manipuladores implícitos, basados en el tipo de fichero. Normalmente, todos son servidos simplemente por el servidor, pero ciertos tipos de fichero son "manipulados" por separado.


Apache 1.1 adds the ability to use handlers explicitly. Based on either filename extensions or on location, handlers can be specified without relation to file type. This is advantageous both because it is a more elegant solution, and because 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 included in a module, or they can be added with the Action directive. The built-in handlers in the standard distribution are as follows:


Modifying static content using a CGI script

The following directives will cause requests for files with the html extension to trigger the launch of the CGI script.

     Action add-footer /cgi-bin/
     AddHandler add-footer .html

Then the CGI script is responsible for sending the originally requested document (pointed to by the PATH_TRANSLATED environment variable) and making whatever modifications or additions are desired.

Files with HTTP headers

The following directives will enable the send-as-is handler, which is used for files which contain their own HTTP headers. All files in the /web/htdocs/asis/ directory will be processed by the send-as-is handler, regardless of their filename extensions.

    <Directory /web/htdocs/asis>
    SetHandler send-as-is

Programmer's Note

In order to implement the handler features, an addition has been made to the Apache API that you may wish to make use of. Specifically, a new record has been added to the request_rec structure:

    char *handler

If you wish to have your module engage a handler, you need only to set r->handler to the name of the handler at any time prior to the invoke_handler stage of the request. Handlers are implemented as they were before, albeit using the handler name instead of a content type. While it is not necessary, the naming convention for handlers is to use a dash-separated word, with no slashes, so as to not invade the media type name-space.