Módulos Relacionados	Directivas Relacionadas
`mod_actions` `mod_asis` `mod_cgi` `mod_imagemap` `mod_info` `mod_mime` `mod_negotiation` `mod_status`	`Action` `AddHandler` `RemoveHandler` `SetHandler`

Comentarios

Notice:
This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our mailing lists.

+ --> +Uso de los Handlers en Apache - Servidor HTTP Apache Versión 2.5 + + + + + + + +

+Apache > Servidor HTTP > Documentación > Versión 2.5

Uso de los Handlers en Apache

Idiomas disponibles: en | + es | + fr | + ja | + ko | + tr | + zh-cn

+ +

Este documento describe el uso de los Handlers en Apache.

¿Qué es un Handler?
Ejemplos
Nota para programadores

Consulte también

Comentarios

¿Qué es un Handler?

Módulos Relacionados	Directivas Relacionadas
`mod_actions` `mod_asis` `mod_cgi` `mod_imagemap` `mod_info` `mod_mime` `mod_negotiation` `mod_status`	`Action` `AddHandler` `RemoveHandler` `SetHandler`

+ + + + +

Un "handler" es una representación interna de Apache de + una acción que se va a ejecutar cuando hay una llamada a un + fichero. Generalmente, los ficheros tienen handlers + implícitos, basados en el tipo de fichero de que se + trata. Normalmente, todos los ficheros son simplemente servidos + por el servidor, pero algunos tipos de ficheros se tratan de forma + diferente.

+ +

Handlers pueden ser usados de manera explicita, + basándose en la extensión del fichero o en + la ubicación en la que esté, se pueden especificar handlers + sin tener en cuenta el tipo de fichero que se trate. Esto es + una ventaja por dos razones. Primero, es una solución + más elegante. Segundo, porque a un fichero se le pueden + asignar tanto un tipo como un handler. (Consulte + también la sección Ficheros y extensiones + múltiples.)

+ +

Los Handlers pueden tanto ser compilados con el servidor + como incluidos en un módulo, o añadidos con la + directiva Action. Los + handlers que vienen incluidos en el core con el servidor de la distribución + estándar de Apache son:

+ +

default-handler: Envía el fichero + usando el default_handler(), que es el handler + usado por defecto para tratar contenido + estático. (core)
send-as-is: Envía el fichero con + cabeceras HTTP tal y como es. (mod_asis)
cgi-script: Trata el fichero como un sript + CGI. (mod_cgi)
imap-file: Trata el fichero como un mapa de + imágenes. (mod_imagemap)
server-info: Extrae la información de + configuración del + servidor. (mod_info)
server-status: Extrae el informe del estado + del servidor. (mod_status)
type-map: Trata el fichero como una + correspondencia de tipos para la negociación de contenidos. + (mod_negotiation)

Ejemplos

+ + +

Modificar contenido estático usando un script + CGI

+ + +

Las siguientes directivas hacen que cuando haya una + petición de ficheros con la extensión + html se lance el script CGI + footer.pl.

+ +

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

+ +

En este caso, el script CGI es el responsable de enviar el + documento originalmente solicitado (contenido en la variable de + entorno PATH_TRANSLATED) y de hacer cualquier + modificación o añadido deseado.

+ + +

Archivos con cabeceras HTTP

+ + +

Las siguientes directivas activan el handler + send-as-is, que se usa para ficheros que contienen + sus propias cabeceras HTTP. Todos los archivos en el directorio + /web/htdocs/asis/ serán procesados por el + handler send-as-is, sin tener en cuenta su + extension.

+ +

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

+ + + +

Nota para programadores

+ + +

Para implementar las funcionalidades de los handlers, se ha + hecho un añadido a la API de + Apache que puede que quiera usar. Para ser más + específicos, se ha añadido un nuevo registro a la + estructura request_rec:

+ +

char *handler

+ + +

Si quiere que su módulo llame a un handler , solo tiene + que añadir r->handler al nombre del handler + en cualquier momento antes de la fase invoke_handler + de la petición. Los handlers se implementan siempre como se + hacía antes, aunque usando el nombre del handler en vez de un + tipo de contenido. Aunque no es de obligado cumplimiento, la + convención de nombres para los handlers es que se usen + palabras separadas por guiones, sin barras, de manera que no se + invada el media type name-space.

Idiomas disponibles: en | + es | + fr | + ja | + ko | + tr | + zh-cn

Comentarios

- \ No newline at end of file +//--> + diff --git a/docs/manual/howto/access.xml.es b/docs/manual/howto/access.xml.es index a46900aedf..7eeca7add5 100644 --- a/docs/manual/howto/access.xml.es +++ b/docs/manual/howto/access.xml.es @@ -1,214 +1,214 @@ - - - - - - - - - -How-To / Tutoriales - -Control de Acceso - -

El control de acceso, hace referencia a todos los medios que proporcionan - una forma de controlar el acceso a cualquier recurso. Esta parte estÃ¡ - separada de autenticaciÃ³n y autorizaciÃ³n.

- - - -

Control de Acceso por host -

- Si lo que se quiere es restringir algunas zonas del sitio web, basÃ¡ndonos - en la direcciÃ³n del visitante, esto puede ser realizado de manera - fÃ¡cil con el mÃ³dulo mod_authz_host. -

- -

La directiva Require - proporciona una variedad de diferentes maneras de permitir o denegar el acceso a los recursos. AdemÃ¡s puede ser usada junto con las directivas:RequireAll, RequireAny, y RequireNone, estos requerimientos pueden - ser combinados de forma compleja y arbitraria, para cumplir cualquiera que - sean tus polÃticas de acceso.

- -

- Las directivas Allow, - Deny, y - Order, - proporcionadas por mod_access_compat, estÃ¡n obsoletas y - serÃ¡n quitadas en futuras versiones. DeberÃ¡ evitar su uso, y tambiÃ©n - los tutoriales desactualizaos que recomienden su uso. -

- -

El uso de estas directivas es:

- - - -Require host address
-Require ip ip.address - - -

En la primera lÃnea, address es el FQDN de un nombre de - dominio (o un nombre parcial del dominio); puede proporcionar mÃºltiples - direcciones o nombres de dominio, si se desea. -

- -

En la segunda lÃnea, ip.address es la direcciÃ³n IP, una - direcciÃ³n IP parcial, una red con su mÃ¡scara, o una especificaciÃ³n red/nnn - CIDR. Pueden usarse tanto IPV4 como IPV6.

- -

Consulte tambiÃ©n la - documentaciÃ³n de mod_authz_host para otros ejemplos de esta sintaxis. -

- -

Puede ser insertado not para negar un requisito en particular. - Note que, ya que not es una negaciÃ³n de un valor, no puede ser - usado por si solo para permitir o denegar una peticiÃ³n, como not true - que no contituye ser false. En consecuencia, para denegar una - visita usando una negaciÃ³n, el bloque debe tener un elemento que se evalÃºa como - verdadero o falso. Por ejemplo, si tienes a alguien espameandote tu tablÃ³n de - mensajes, y tu quieres evitar que entren o dejarlos fuera, puedes realizar - lo siguiente: -

- - -<RequireAll> - Require all granted - Require not ip 10.252.46.165 -</RequireAll> - - -

Los visitantes que vengan desde la IP que se configura (10.252.46.165) - no tendrÃ¡n acceso al contenido que cubre esta directiva. Si en cambio, lo que se - tiene es el nombre de la mÃ¡quina, en vez de la IP, podrÃ¡s usar:

- - -Require not host host.example.com - - -

Y, Si lo que se quiere es bloquear el acceso desde dominio especifico, - podrÃ¡s especificar parte de una direcciÃ³n o nombre de dominio:

- - -Require not ip 192.168.205 -Require not host phishers.example.com moreidiots.example -Require not host gov - - -

Uso de las directivas RequireAll, RequireAny, y RequireNone pueden ser usadas - para forzar requisitos mÃ¡s complejos.

- -

Control de acceso por variables arbitrarias. - -

Haciendo el uso de If, - puedes permitir o denegar el acceso basado en variables de entrono arbitrarias - o en los valores de las cabeceras de las peticiones. Por ejemplo para denegar - el acceso basÃ¡ndonos en el "user-agent" (tipo de navegador asÃ como Sistema Operativo) - puede que hagamos lo siguiente: -

- - -<If "%{HTTP_USER_AGENT} == 'BadBot'"> - Require all denied -</If> - - -

Usando la sintaxis de Require - expr , esto tambiÃ©n puede ser escrito de la siguiente forma: -

- - - -Require expr %{HTTP_USER_AGENT} != 'BadBot' - - - Advertencia: -

El control de acceso por User-Agent es una tÃ©cnica poco fiable, - ya que la cabecera de User-Agent puede ser modificada y establecerse - al antojo del usuario.

- - -

Vea tambiÃ©n la pÃ¡gina de expresiones - para una mayor aclaraciÃ³n de que sintaxis tienen las expresiones y que - variables estÃ¡n disponibles.

- -

Control de acceso con mod_rewrite - -

El flag [F] de RewriteRule causa una respuesta 403 Forbidden - para ser enviada. USando esto, podrÃ¡ denegar el acceso a recursos basÃ¡ndose - en criterio arbitrario.

- -

Por ejemplo, si lo que desea es bloquear un recurso entre las 8pm y las - 7am, podrÃ¡ hacerlo usando mod_rewrite:

- - -RewriteEngine On -RewriteCond "%{TIME_HOUR}" ">=20" [OR] -RewriteCond "%{TIME_HOUR}" "<07" -RewriteRule "^/fridge" "-" [F] - - -

Esto devolverÃ¡ una respuesta de error 403 Forbidden para cualquier peticiÃ³n - despuÃ©s de las 8pm y antes de las 7am. Esta tÃ©cnica puede ser usada para cualquier - criterio que desee usar. TambiÃ©n puede redireccionar, o incluso reescribir estas - peticiones, si se prefiere ese enfoque. -

- -

La directiva If, - aÃ±adida en la 2.4, sustituye muchas cosas que mod_rewrite - tradicionalmente solÃa hacer, y deberÃ¡ comprobar estas antes de recurrir a -

- -

MÃ¡s informaciÃ³n - -

El motor de expresiones le da una gran - capacidad de poder para hacer una gran variedad de cosas basadas en - las variables arbitrarias del servidor, y debe consultar este - documento para mÃ¡s detalles.

- -

TambiÃ©n, deberÃ¡ leer la documentaciÃ³n de mod_authz_core - para ejemplos de combinaciones de mÃºltiples requisitos de acceso y especificar - cÃ³mo interactÃºan. -

- -

Vea tambiÃ©n los howtos de AuthenticaciÃ³n y AutorizaciÃ³n -

- - + + + + + + + + + +How-To / Tutoriales + +Control de Acceso + +

El control de acceso, hace referencia a todos los medios que proporcionan + una forma de controlar el acceso a cualquier recurso. Esta parte estÃ¡ + separada de autenticaciÃ³n y autorizaciÃ³n.

+ + + +

Control de Acceso por host +

+ Si lo que se quiere es restringir algunas zonas del sitio web, basÃ¡ndonos + en la direcciÃ³n del visitante, esto puede ser realizado de manera + fÃ¡cil con el mÃ³dulo mod_authz_host. +

+ +

La directiva Require + proporciona una variedad de diferentes maneras de permitir o denegar el acceso a los recursos. AdemÃ¡s puede ser usada junto con las directivas:RequireAll, RequireAny, y RequireNone, estos requerimientos pueden + ser combinados de forma compleja y arbitraria, para cumplir cualquiera que + sean tus polÃticas de acceso.

+ +

+ Las directivas Allow, + Deny, y + Order, + proporcionadas por mod_access_compat, estÃ¡n obsoletas y + serÃ¡n quitadas en futuras versiones. DeberÃ¡ evitar su uso, y tambiÃ©n + los tutoriales desactualizaos que recomienden su uso. +

+ +

El uso de estas directivas es:

+ + + +Require host address
+Require ip ip.address + + +

En la primera lÃnea, address es el FQDN de un nombre de + dominio (o un nombre parcial del dominio); puede proporcionar mÃºltiples + direcciones o nombres de dominio, si se desea. +

+ +

En la segunda lÃnea, ip.address es la direcciÃ³n IP, una + direcciÃ³n IP parcial, una red con su mÃ¡scara, o una especificaciÃ³n red/nnn + CIDR. Pueden usarse tanto IPV4 como IPV6.

+ +

Consulte tambiÃ©n la + documentaciÃ³n de mod_authz_host para otros ejemplos de esta sintaxis. +

+ +

Puede ser insertado not para negar un requisito en particular. + Note que, ya que not es una negaciÃ³n de un valor, no puede ser + usado por si solo para permitir o denegar una peticiÃ³n, como not true + que no contituye ser false. En consecuencia, para denegar una + visita usando una negaciÃ³n, el bloque debe tener un elemento que se evalÃºa como + verdadero o falso. Por ejemplo, si tienes a alguien espameandote tu tablÃ³n de + mensajes, y tu quieres evitar que entren o dejarlos fuera, puedes realizar + lo siguiente: +

+ + +<RequireAll> + Require all granted + Require not ip 10.252.46.165 +</RequireAll> + + +

Los visitantes que vengan desde la IP que se configura (10.252.46.165) + no tendrÃ¡n acceso al contenido que cubre esta directiva. Si en cambio, lo que se + tiene es el nombre de la mÃ¡quina, en vez de la IP, podrÃ¡s usar:

+ + +Require not host host.example.com + + +

Y, Si lo que se quiere es bloquear el acceso desde dominio especifico, + podrÃ¡s especificar parte de una direcciÃ³n o nombre de dominio:

+ + +Require not ip 192.168.205 +Require not host phishers.example.com moreidiots.example +Require not host gov + + +

Uso de las directivas RequireAll, RequireAny, y RequireNone pueden ser usadas + para forzar requisitos mÃ¡s complejos.

+ +

Control de acceso por variables arbitrarias. + +

Haciendo el uso de If, + puedes permitir o denegar el acceso basado en variables de entrono arbitrarias + o en los valores de las cabeceras de las peticiones. Por ejemplo para denegar + el acceso basÃ¡ndonos en el "user-agent" (tipo de navegador asÃ como Sistema Operativo) + puede que hagamos lo siguiente: +

+ + +<If "%{HTTP_USER_AGENT} == 'BadBot'"> + Require all denied +</If> + + +

Usando la sintaxis de Require + expr , esto tambiÃ©n puede ser escrito de la siguiente forma: +

+ + + +Require expr %{HTTP_USER_AGENT} != 'BadBot' + + + Advertencia: +

El control de acceso por User-Agent es una tÃ©cnica poco fiable, + ya que la cabecera de User-Agent puede ser modificada y establecerse + al antojo del usuario.

+ + +

Vea tambiÃ©n la pÃ¡gina de expresiones + para una mayor aclaraciÃ³n de que sintaxis tienen las expresiones y que + variables estÃ¡n disponibles.

+ +

Control de acceso con mod_rewrite + +

El flag [F] de RewriteRule causa una respuesta 403 Forbidden + para ser enviada. USando esto, podrÃ¡ denegar el acceso a recursos basÃ¡ndose + en criterio arbitrario.

+ +

Por ejemplo, si lo que desea es bloquear un recurso entre las 8pm y las + 7am, podrÃ¡ hacerlo usando mod_rewrite:

+ + +RewriteEngine On +RewriteCond "%{TIME_HOUR}" ">=20" [OR] +RewriteCond "%{TIME_HOUR}" "<07" +RewriteRule "^/fridge" "-" [F] + + +

Esto devolverÃ¡ una respuesta de error 403 Forbidden para cualquier peticiÃ³n + despuÃ©s de las 8pm y antes de las 7am. Esta tÃ©cnica puede ser usada para cualquier + criterio que desee usar. TambiÃ©n puede redireccionar, o incluso reescribir estas + peticiones, si se prefiere ese enfoque. +

+ +

La directiva If, + aÃ±adida en la 2.4, sustituye muchas cosas que mod_rewrite + tradicionalmente solÃa hacer, y deberÃ¡ comprobar estas antes de recurrir a +

+ +

MÃ¡s informaciÃ³n + +

El motor de expresiones le da una gran + capacidad de poder para hacer una gran variedad de cosas basadas en + las variables arbitrarias del servidor, y debe consultar este + documento para mÃ¡s detalles.

+ +

TambiÃ©n, deberÃ¡ leer la documentaciÃ³n de mod_authz_core + para ejemplos de combinaciones de mÃºltiples requisitos de acceso y especificar + cÃ³mo interactÃºan. +

+ +

Vea tambiÃ©n los howtos de AuthenticaciÃ³n y AutorizaciÃ³n +

+ + diff --git a/docs/manual/invoking.html.es b/docs/manual/invoking.html.es index 68aa548382..fa2841379c 100644 --- a/docs/manual/invoking.html.es +++ b/docs/manual/invoking.html.es @@ -1,169 +1,169 @@ - - - - + + + + -Iniciar Apache - Servidor HTTP Apache Versión 2.5 - - - - - - - -

-Apache > Servidor HTTP > Documentación > Versión 2.5

Iniciar Apache

Idiomas disponibles: de | - en | - es | - fr | - ja | - ko | - tr

- -

En Windows, Apache se ejecuta normalmente como un servicio. - Para obtener más información, consulte - Ejecutar Apache como un - servicio.

- -

En Unix, el programa httpd se - ejecuta como un demonio (daemon) de forma contíniua y en segundo plano - y atiende las peticiones que le lleguen. Este documento describe cómo - invocar el programa httpd.

Cómo iniciar Apache
Errores Durante el Arranque
Iniciar Apache al Iniciar el Sistema
Información Adicional

Consulte también

Cómo iniciar Apache

- -

Si el puerto especificado en la directiva Listen del fichero de - configuración es el que viene por defecto, es decir, el - puerto 80 (o cualquier otro puerto por debajo del 1024), entonces - es necesario tener privilegios de usuario root (superusuario) para - iniciar Apache, de modo que pueda establecerse una conexión a - través de esos puertos privilegiados. Una vez que el servidor - Apache se ha iniciado y ha completado algunas tareas preliminares, - tales como abrir sus ficheros log, lanzará varios procesos, - procesos hijo, que hacen el trabajo de escuchar y atender - las peticiones de los clientes. El proceso principal, - httpd continúa ejecutándose con el usuario root, pero los - procesos hijo se ejecutan con menores privilegios de usuario. - Esto lo controla el Módulo de - MultiProcesamiento (MPM) seleccionado.

- -

La forma recomendada para invocar el ejecutable - httpd es usando el script de control - apachectl. Este script fija - determinadas variables de entorno que son necesarias para que - httpd funcione correctamente en el sistema operativo, - y después invoca el binario httpd. - apachectl pasa a httpd - cualquier argumento que se le pase a través de la línea de comandos, - de forma que cualquier opción de httpd puede ser usada - también con apachectl. Puede editar - directamente el script apachectl y cambiar la - variable HTTPD variable que está al principio y - que especifica la ubicación exacta en la que está el - binario httpd y cualquier argumento de línea de - comandos que quiera que esté siempre presente.

- -

La primera cosa que hace httpd cuando es invocado - es localizar y leer el fichero de - configuración httpd.conf. El lugar en el que - está ese fichero se determina al compilar, pero también - es posible especificar la ubicación en la que se encuentra al - iniciar el servidor Apache usando la opción de línea de - comandos -f

- -

/usr/local/apache2/bin/apachectl -f - /usr/local/apache2/conf/httpd.conf

- -

Si todo va bien durante el arranque, la sesión de terminal - se suspenderá un momento y volverá a estar activa casi - inmediatamente. Esto quiere decir que el servidor está activo - y funcionando. Puede usar su navegador para conectarse al - servidor y ver la página de prueba que hay en el directorio de - la directiva - DocumentRoot.

Errores Durante el Arranque

- -

Si Apache encuentra una error irrecuperable durante el - arranque, escribirá un mensaje describiendo el problema en la - consola o en el archivo ErrorLog antes de abortar la - ejecución. Uno de los mensajes de error más comunes es - "Unable to bind to Port ...". Cuando se recibe este - mensaje es normalmente por alguna de las siguientes razones:

- -

Está intentando iniciar el servidor Apache en un puerto - privilegiado (del 0 al 1024) sin haber hecho login como usuario - root; ó bien
Está intentando iniciar el servidor Apache mientras - está ya ejecutando Apache o algún otro servidor web en - el mismo puerto.

- -

Puede encontrar más información sobre cómo - solucionar problemas, en la sección de Preguntas Frecuentes de Apache.

Iniciar Apache al Iniciar el Sistema

- -

Si quiere que el servidor Apache continúe su ejecución - después de reiniciar el sistema, debe añadir una llamada - a apachectl en sus archivos de arranque (normalmente - rc.local o un fichero en ese directorio del tipo - rc.N). Esto iniciará Apache como usuario - root. Antes de hacer esto, asegúrese de que la - configuración de seguridad y las restricciones de acceso de - su servidor Apache están correctamente configuradas.

- -

El script apachectl está diseñado para - actuar como un script estándar de tipo SysV init; puede tomar los - argumentos start, restart, y - stop y traducirlos en las señales apropiadas - para httpd. De esta manera, casi siempre puede - simplemente enlazar apachectlcon el directorio init - adecuado. Pero asegúrese de comprobar los requisitos exactos - de su sistema.

Información Adicional

- -

En la sección El Servidor y Programas - de Soporte puede encontrar más información sobre - las opciones de línea de comandos que puede pasar a httpd y apachectl así como sobre otros - programas de soporte incluidos con el servidor Apache. - También hay documentación sobre todos los módulos incluidos con la distribución de - Apache y sus correspondientes directivas asociadas.

Idiomas disponibles: de | - en | - es | - fr | - ja | - ko | - tr

Comentarios

+ --> +Iniciar Apache - Servidor HTTP Apache Versión 2.5 + + + + + + + +

+Apache > Servidor HTTP > Documentación > Versión 2.5

Iniciar Apache

Idiomas disponibles: de | + en | + es | + fr | + ja | + ko | + tr

+ +

En Windows, Apache se ejecuta normalmente como un servicio. + Para obtener más información, consulte + Ejecutar Apache como un + servicio.

+ +

En Unix, el programa httpd se + ejecuta como un demonio (daemon) de forma contíniua y en segundo plano + y atiende las peticiones que le lleguen. Este documento describe cómo + invocar el programa httpd.

Cómo iniciar Apache
Errores Durante el Arranque
Iniciar Apache al Iniciar el Sistema
Información Adicional

Consulte también

Cómo iniciar Apache

+ +

Si el puerto especificado en la directiva Listen del fichero de + configuración es el que viene por defecto, es decir, el + puerto 80 (o cualquier otro puerto por debajo del 1024), entonces + es necesario tener privilegios de usuario root (superusuario) para + iniciar Apache, de modo que pueda establecerse una conexión a + través de esos puertos privilegiados. Una vez que el servidor + Apache se ha iniciado y ha completado algunas tareas preliminares, + tales como abrir sus ficheros log, lanzará varios procesos, + procesos hijo, que hacen el trabajo de escuchar y atender + las peticiones de los clientes. El proceso principal, + httpd continúa ejecutándose con el usuario root, pero los + procesos hijo se ejecutan con menores privilegios de usuario. + Esto lo controla el Módulo de + MultiProcesamiento (MPM) seleccionado.

+ +

La forma recomendada para invocar el ejecutable + httpd es usando el script de control + apachectl. Este script fija + determinadas variables de entorno que son necesarias para que + httpd funcione correctamente en el sistema operativo, + y después invoca el binario httpd. + apachectl pasa a httpd + cualquier argumento que se le pase a través de la línea de comandos, + de forma que cualquier opción de httpd puede ser usada + también con apachectl. Puede editar + directamente el script apachectl y cambiar la + variable HTTPD variable que está al principio y + que especifica la ubicación exacta en la que está el + binario httpd y cualquier argumento de línea de + comandos que quiera que esté siempre presente.

+ +

La primera cosa que hace httpd cuando es invocado + es localizar y leer el fichero de + configuración httpd.conf. El lugar en el que + está ese fichero se determina al compilar, pero también + es posible especificar la ubicación en la que se encuentra al + iniciar el servidor Apache usando la opción de línea de + comandos -f

+ +

/usr/local/apache2/bin/apachectl -f + /usr/local/apache2/conf/httpd.conf

+ +

Si todo va bien durante el arranque, la sesión de terminal + se suspenderá un momento y volverá a estar activa casi + inmediatamente. Esto quiere decir que el servidor está activo + y funcionando. Puede usar su navegador para conectarse al + servidor y ver la página de prueba que hay en el directorio de + la directiva + DocumentRoot.

Errores Durante el Arranque

+ +

Si Apache encuentra una error irrecuperable durante el + arranque, escribirá un mensaje describiendo el problema en la + consola o en el archivo ErrorLog antes de abortar la + ejecución. Uno de los mensajes de error más comunes es + "Unable to bind to Port ...". Cuando se recibe este + mensaje es normalmente por alguna de las siguientes razones:

+ +

Está intentando iniciar el servidor Apache en un puerto + privilegiado (del 0 al 1024) sin haber hecho login como usuario + root; ó bien
Está intentando iniciar el servidor Apache mientras + está ya ejecutando Apache o algún otro servidor web en + el mismo puerto.

+ +

Puede encontrar más información sobre cómo + solucionar problemas, en la sección de Preguntas Frecuentes de Apache.

Iniciar Apache al Iniciar el Sistema

+ +

Si quiere que el servidor Apache continúe su ejecución + después de reiniciar el sistema, debe añadir una llamada + a apachectl en sus archivos de arranque (normalmente + rc.local o un fichero en ese directorio del tipo + rc.N). Esto iniciará Apache como usuario + root. Antes de hacer esto, asegúrese de que la + configuración de seguridad y las restricciones de acceso de + su servidor Apache están correctamente configuradas.

+ +

El script apachectl está diseñado para + actuar como un script estándar de tipo SysV init; puede tomar los + argumentos start, restart, y + stop y traducirlos en las señales apropiadas + para httpd. De esta manera, casi siempre puede + simplemente enlazar apachectlcon el directorio init + adecuado. Pero asegúrese de comprobar los requisitos exactos + de su sistema.

Información Adicional

+ +

En la sección El Servidor y Programas + de Soporte puede encontrar más información sobre + las opciones de línea de comandos que puede pasar a httpd y apachectl así como sobre otros + programas de soporte incluidos con el servidor Apache. + También hay documentación sobre todos los módulos incluidos con la distribución de + Apache y sus correspondientes directivas asociadas.

Idiomas disponibles: de | + en | + es | + fr | + ja | + ko | + tr

Comentarios

- \ No newline at end of file +//--> + diff --git a/docs/manual/mod/core.html.es b/docs/manual/mod/core.html.es index bb0344b4b5..f82f72d1bc 100644 --- a/docs/manual/mod/core.html.es +++ b/docs/manual/mod/core.html.es @@ -1,4452 +1,4452 @@ - - - - + + + + -core - Servidor HTTP Apache Versión 2.5 - - - - - - - - -

-Apache > Servidor HTTP > Documentación > Versión 2.5 > Módulos

Funcionalidad Básica de Apache

Idiomas disponibles: de | - en | - es | - fr | - ja | - tr

Esta traducción podría estar - obsoleta. Consulte la versión en inglés de la - documentación para comprobar si se han producido cambios - recientemente.

- -

Descripción:	Funcionalides básicas del Servidor HTTP Apache que siempre están presentes.
Estado:	Core

Directivas

AcceptFilter
AcceptPathInfo
AccessFileName
AddDefaultCharset
AllowEncodedSlashes
AllowOverride
AllowOverrideList
AsyncFilter
CGIMapExtension
CGIPassAuth
CGIVar
ContentDigest
DefaultRuntimeDir
DefaultType
Define
<Directory>
<DirectoryMatch>
DocumentRoot
<Else>
<ElseIf>
EnableMMAP
EnableSendfile
Error
ErrorDocument
ErrorLog
ErrorLogFormat
ExtendedStatus
FileETag
<Files>
<FilesMatch>
ForceType
GprofDir
HostnameLookups
<If>
<IfDefine>
<IfModule>
Include
IncludeOptional
KeepAlive
KeepAliveTimeout
<Limit>
<LimitExcept>
LimitInternalRecursion
LimitRequestBody
LimitRequestFields
LimitRequestFieldSize
LimitRequestLine
LimitXMLRequestBody
<Location>
<LocationMatch>
LogLevel
LogLevelOverride
MaxKeepAliveRequests
MaxRangeOverlaps
MaxRangeReversals
MaxRanges
MergeTrailers
Mutex
NameVirtualHost
Options
Protocol
Protocols
ProtocolsHonorOrder
QualifyRedirectURL
RegisterHttpMethod
RLimitCPU
RLimitMEM
RLimitNPROC
ScriptInterpreterSource
SeeRequestTail
ServerAdmin
ServerAlias
ServerName
ServerPath
ServerRoot
ServerSignature
ServerTokens
SetHandler
SetInputFilter
SetOutputFilter
TimeOut
TraceEnable
UnDefine
UseCanonicalName
UseCanonicalPhysicalPort
<VirtualHost>
Warning

Bugfix checklist

Consulte también

Comentarios

- -

AcceptFilter Directiva

- - - - - - -

Descripción:	Configura mejoras para un Protocolo de Escucha de Sockets
Sintaxis:	`AcceptFilter protocol accept_filter`
Contexto:	server config
Estado:	Core
Módulo:	core

Esta directiva hace posible mejoras específicas a nivel de sistema operativo - y a través del tipo de Protocolo para un socket que escucha. - La premisa básica es que el kernel no envíe un socket al servidor - hasta que o bien los datos se hayan recibido o bien se haya almacenado - en el buffer una Respuesta HTTP completa. - Actualmente sólo están soportados - - Accept Filters sobre FreeBSD, TCP_DEFER_ACCEPT sobre Linux, - y AcceptEx() sobre Windows.

- -

El uso de none para un argumento desactiva cualquier filtro - aceptado para ese protocolo. Esto es útil para protocolos que requieren que un - servidor envíe datos primeros, tales como ftp: o nntp:

AcceptFilter nntp none

- - -

Los nombres de protocolo por defecto son https para el puerto 443 - y http para todos los demás puertos. Para especificar que se está - utilizando otro protocolo con un puerto a la escucha, añade el argumento protocol - a la directiva Listen.

- -

Los valores por defecto de FreeBDS son:

AcceptFilter http httpready
-AcceptFilter https dataready

- - -

El filtro httpready almacena en el buffer peticiones HTTP completas - a nivel de kernel. Una vez que la petición es recibida, el kernel la envía al servidor. - Consulta la página man de - - accf_http(9) para más detalles. Puesto que las peticiones HTTPS - están encriptadas, sólo se utiliza el filtro - accf_data(9).

- -

Los valores por defecto en Linux son:

AcceptFilter http data
-AcceptFilter https data

- - -

En Linux, TCP_DEFER_ACCEPT no soporta el buffering en peticiones http. - Cualquier valor además de none habilitará - TCP_DEFER_ACCEPT en ese socket. Para más detalles - ver la página man de Linux - - tcp(7).

- -

Los valores por defecto en Windows son:

AcceptFilter http data
-AcceptFilter https data

- - -

Sobre Windows mpm_winnt interpreta el argumento AcceptFilter para conmutar la API - AcceptEx(), y no soporta el buffering sobre el protocolo http. Hay dos valores - que utilizan la API Windows AcceptEx() y que recuperan sockets de red - entre conexiones. data espera hasta que los datos han sido - transmitidos como se comentaba anteriormente, y el buffer inicial de datos y las - direcciones de red son recuperadas a partir de una única llamada AcceptEx(). - connect utiliza la API AcceptEx() API, y recupera también - las direcciones de red, pero a diferencia de none - la opción connect no espera a la transmisión inicial de los datos.

- -

Sobre Windows, none usa accept() antes que AcceptEx() - y no recuperará sockets entre las conexiones. Lo que es útil para los adaptadores de - red con un soporte precario de drivers, así como para algunos proveedores de red - tales como drivers vpn, o filtros de spam, de virus o de spyware.

- - -

Consulte también

Protocol

AcceptPathInfo Directiva

- - - - - - - - -

Descripción:	Los recursos aceptan información sobre su ruta
Sintaxis:	`AcceptPathInfo On\|Off\|Default`
Valor por defecto:	`AcceptPathInfo Default`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core

- -

Esta directiva controla si las peticiones que contienen información sobre la ruta - que sigue un fichero que existe (o un fichero que no existe pero en un directorio que - sí existe) serán aceptadas o denegadas. La información de ruta puede estar disponible - para los scripts en la variable de entorno PATH_INFO.

- -

Por ejemplo, asumamos que la ubicación /test/ apunta a - un directorio que contiene únicamente el fichero - here.html. Entonces, las peticiones tanto para - /test/here.html/more como para - /test/nothere.html/more recogen - /more como PATH_INFO.

- -

Los tres posibles argumentos para la directiva - AcceptPathInfo son los siguientes:

Off: Una petición sólo será aceptada si - se corresponde con una ruta literal que existe. Por lo tanto, una petición - con una información de ruta después del nombre de fichero tal como - /test/here.html/more en el ejemplo anterior devolverá - un error 404 NOT FOUND.
On: Una petición será aceptada si una - ruta principal de acceso se corresponde con un fichero que existe. El ejemplo - anterior /test/here.html/more será aceptado si - /test/here.html corresponde a un fichero válido.
Default: La gestión de las peticiones - con información de ruta está determinada por el controlador responsable de la petición. - El controlador principal para para ficheros normales rechaza por defecto - peticiones PATH_INFO. Los controladores que sirven scripts, tales como cgi-script e isapi-handler, normalmente aceptan - PATH_INFO por defecto.

- -

El objetivo principal de la directiva AcceptPathInfo - es permitirnos sobrescribir la opción del controlador - de aceptar o rechazar PATH_INFO. Este tipo de reescritura se necesita, - por ejemplo, cuando utilizas un filtro, tal como - INCLUDES, para generar contenido - basado en PATH_INFO. El controlador principal normalmente rechazaría - la petición, de modo que puedes utilizar la siguiente configuración para habilitarla - como script:

- -

<Files "mypaths.shtml">
-  Options +Includes
-  SetOutputFilter INCLUDES
-  AcceptPathInfo On
-</Files>

- - - -

AccessFileName Directiva

- - - - - - - -

Descripción:	Nombre del fichero distribuido de configuración
Sintaxis:	`AccessFileName filename [filename] ...`
Valor por defecto:	`AccessFileName .htaccess`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

Mientras que procesa una petición el servidor busca - el primer fichero de configuración existente dentro de un listado de nombres en - cada directorio de la ruta del documento, si los ficheros distribuidos - de configuración están habilitados para ese - directorio. Por ejemplo:

- -

AccessFileName .acl

- - -

Antes de servir el documento - /usr/local/web/index.html, el servidor leerá - /.acl, /usr/.acl, - /usr/local/.acl y /usr/local/web/.acl - para las directivas, salvo que estén deshabilitadas con:

- -

<Directory "/">
-    AllowOverride None
-</Directory>

- - - - -

Consulte también

AddDefaultCharset Directiva

- - - - - - - - -

Descripción:	Juego de casrácteres que se le añade por defecto a una respuesta del tipo - contenido "content-type" es `text/plain` o `text/html`
Sintaxis:	`AddDefaultCharset On\|Off\|charset`
Valor por defecto:	`AddDefaultCharset Off`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core

Esta directiva especifica un valor por defecto para el tipo de soporte que - se usa como parámetro del juego de carácteres (el nombre de una - codificación de carácteres) para ser añadido a una respuesta si y solo si - el contenido de "content-type" es o text/plain o - text/html. Esto debería sobreescribir cualquier juego de - caracteres que se le especifique en el cuerpo de la respuesta mediante un - elemento META, aunque el comportamiento exacto depende a menudo - de la confuguracion del usuario cliente. Una configuración de - AddDefaultCharset Off deshabilita esta funcionalidad. - AddDefaultCharset On habilita un conjunto de caracteres por defecto - de iso-8859-1. Cualquier otro valor se asume que sea el charset - que va a ser usado, que debe ser uno de los juegos de carácteres - registradas por el IANA - para su uso en los tipos de medios de Internet (MIME types). - Por ejemplo:

- -

AddDefaultCharset utf-8

- - -

AddDefaultCharset debería ser utilizada sólo cuando - se sepa que todo el texto del recurso al que se le aplica se sabe que va a - estar en ese juego de caracteres y es inconveniente etiquetar los - documentos individualmente. Un ejemplo de ello es añadir el juego de caracteres - a recursos con contenido autogenerado, tales como scripts legados de CGI, - que pueden ser vulnerables a ataques de tipo XSS (Cross-Site Scripting), - debido a datos que incluye el usuario en la salida. Notese, sin embargo - una mejor solución es arreglar (o eliminar) dichos scripts, ya que - dejar por defecto un juego de carácteres no protege a los usuarios - que han habilitado la funcionalidad "auto-detect character encoding" en sus - navegadores. -

- -

Consulte también

AddCharset

AllowEncodedSlashes Directiva

- - - - - - - - -

Descripción:	Determina si Determines whether encoded path separators in URLs are allowed to -be passed through
Sintaxis:	`AllowEncodedSlashes On\|Off`
Valor por defecto:	`AllowEncodedSlashes Off`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache httpd 2.0.46 and later

The AllowEncodedSlashes directive allows URLs - which contain encoded path separators (%2F for / - and additionally %5C for \ on according systems) - to be used. Normally such URLs are refused with a 404 (Not found) error.

- -

Turning AllowEncodedSlashes On is - mostly useful when used in conjunction with PATH_INFO.

- -

Note

Allowing encoded slashes does not imply decoding. - Occurrences of %2F or %5C (only on - according systems) will be left as such in the otherwise decoded URL - string.

- -

Consulte también

AcceptPathInfo

AllowOverride Directiva

- - - - - - - -

Descripción:	Types of directives that are allowed in -`.htaccess` files
Sintaxis:	`AllowOverride All\|None\|directive-type -[directive-type] ...`
Valor por defecto:	`AllowOverride None (2.3.9 and later), AllowOverride All (2.3.8 and earlier)`
Contexto:	directory
Estado:	Core
Módulo:	core

When the server finds an .htaccess file (as - specified by AccessFileName) - it needs to know which directives declared in that file can override - earlier configuration directives.

- -

Only available in <Directory> sections

- AllowOverride is valid only in - <Directory> - sections specified without regular expressions, not in <Location>, <DirectoryMatch> or - <Files> sections. -

- -

When this directive is set to None, then - .htaccess files are completely ignored. - In this case, the server will not even attempt to read - .htaccess files in the filesystem.

- -

When this directive is set to All, then any - directive which has the .htaccess Context is allowed in - .htaccess files.

- -

The directive-type can be one of the following - groupings of directives.

- -

AuthConfig: - - Allow use of the authorization directives (AuthDBMGroupFile, - AuthDBMUserFile, - AuthGroupFile, - AuthName, - AuthType, AuthUserFile, Require, etc.).
FileInfo: - Allow use of the directives controlling document types - (ErrorDocument, - ForceType, - LanguagePriority, - SetHandler, - SetInputFilter, - SetOutputFilter, and - mod_mime Add* and Remove* directives), - document meta data (Header, RequestHeader, SetEnvIf, SetEnvIfNoCase, BrowserMatch, CookieExpires, CookieDomain, CookieStyle, CookieTracking, CookieName), - mod_rewrite directives RewriteEngine, RewriteOptions, RewriteBase, RewriteCond, RewriteRule) and - Action from - mod_actions. -
Indexes: - Allow use of the directives controlling directory indexing - (AddDescription, - AddIcon, AddIconByEncoding, - AddIconByType, - DefaultIcon, DirectoryIndex, FancyIndexing, HeaderName, IndexIgnore, IndexOptions, ReadmeName, - etc.).
Limit: - Allow use of the directives controlling host access (Allow, Deny and Order).
Options[=Option,...]: - Allow use of the directives controlling specific directory - features (Options and - XBitHack). - An equal sign may be given followed by a comma (but no spaces) - separated lists of options that may be set using the Options command.

- -

Example:

- -

- AllowOverride AuthConfig Indexes -

- -

In the example above all directives that are neither in the group - AuthConfig nor Indexes cause an internal - server error.

- -

For security and performance reasons, do not set - AllowOverride to anything other than None - in your <Directory /> block. Instead, find (or - create) the <Directory> block that refers to the - directory where you're actually planning to place a - .htaccess file.

- -

Consulte también

AllowOverrideList Directiva

- - - - - - - -

Descripción:	Individual directives that are allowed in -`.htaccess` files
Sintaxis:	`AllowOverrideList None\|directive -[directive-type] ...`
Valor por defecto:	`AllowOverrideList None`
Contexto:	directory
Estado:	Core
Módulo:	core

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

Consulte también

AsyncFilter Directiva

- - - - - - - - -

Descripción:	Set the minimum filter type eligible for asynchronous handling
Sintaxis:	`AsyncFilter request\|connection\|network`
Valor por defecto:	`AsyncFilter request`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Only available from Apache 2.5.0 and later.

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

CGIMapExtension Directiva

- - - - - - - - -

Descripción:	Technique for locating the interpreter for CGI -scripts
Sintaxis:	`CGIMapExtension cgi-path .extension`
Contexto:	directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core
Compatibilidad:	NetWare only

This directive is used to control how Apache httpd finds the - interpreter used to run CGI scripts. For example, setting - CGIMapExtension sys:\foo.nlm .foo will - cause all CGI script files with a .foo extension to - be passed to the FOO interpreter.

- -

CGIPassAuth Directiva

- - - - - - - - - -

Descripción:	Enables passing HTTP authorization headers to scripts as CGI -variables
Sintaxis:	`CGIPassAuth On\|Off`
Valor por defecto:	`CGIPassAuth Off`
Contexto:	directory, .htaccess
Anula:	AuthConfig
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache HTTP Server 2.4.13 and later

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

CGIVar Directiva

- - - - - - - - -

Descripción:	Controls how some CGI variables are set
Sintaxis:	`CGIVar variable rule`
Contexto:	directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache HTTP Server 2.4.21 and later

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

ContentDigest Directiva

- - - - - - - - -

Descripción:	Enables the generation of `Content-MD5` HTTP Response -headers
Sintaxis:	`ContentDigest On\|Off`
Valor por defecto:	`ContentDigest Off`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	Options
Estado:	Core
Módulo:	core

This directive enables the generation of - Content-MD5 headers as defined in RFC1864 - respectively RFC2616.

- -

MD5 is an algorithm for computing a "message digest" - (sometimes called "fingerprint") of arbitrary-length data, with - a high degree of confidence that any alterations in the data - will be reflected in alterations in the message digest.

- -

The Content-MD5 header provides an end-to-end - message integrity check (MIC) of the entity-body. A proxy or - client may check this header for detecting accidental - modification of the entity-body in transit. Example header:

- -

- Content-MD5: AuLb7Dp1rqtRtxz2m9kRpA== -

- -

Note that this can cause performance problems on your server - since the message digest is computed on every request (the - values are not cached).

- -

Content-MD5 is only sent for documents served - by the core, and not by any module. For example, - SSI documents, output from CGI scripts, and byte range responses - do not have this header.

- -

DefaultRuntimeDir Directiva

- - - - - - - - -

Descripción:	Base directory for the server run-time files
Sintaxis:	`DefaultRuntimeDir directory-path`
Valor por defecto:	`DefaultRuntimeDir DEFAULT_REL_RUNTIMEDIR (logs/)`
Contexto:	server config
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache 2.4.2 and later

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

Consulte también

the - security tips for information on how to properly set - permissions on the ServerRoot

DefaultType Directiva

- - - - - - - - - -

Descripción:	This directive has no effect other than to emit warnings -if the value is not `none`. In prior versions, DefaultType -would specify a default media type to assign to response content for -which no other media type configuration could be found. -
Sintaxis:	`DefaultType media-type\|none`
Valor por defecto:	`DefaultType none`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core
Compatibilidad:	The argument `none` is available in Apache httpd 2.2.7 and later. All other choices are DISABLED for 2.3.x and later.

This directive has been disabled. For backwards compatibility - of configuration files, it may be specified with the value - none, meaning no default media type. For example:

- -

- DefaultType None -

- -

DefaultType None is only available in - httpd-2.2.7 and later.

- -

Use the mime.types configuration file and the - AddType to configure media - type assignments via file extensions, or the - ForceType directive to configure - the media type for specific resources. Otherwise, the server will - send the response without a Content-Type header field and the - recipient may attempt to guess the media type.

- -

Define Directiva

- - - - - - -

Descripción:	Define the existence of a variable
Sintaxis:	`Define parameter-name`
Contexto:	server config
Estado:	Core
Módulo:	core

Equivalent to passing the -D argument to httpd.

This directive can be used to toggle the use of <IfDefine> sections without needing to alter - -D arguments in any startup scripts.

- -

<Directory> Directiva

- - - - - - -

Descripción:	Enclose a group of directives that apply only to the -named file-system directory, sub-directories, and their contents.
Sintaxis:	`<Directory directory-path> -... </Directory>`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

<Directory> and - </Directory> are used to enclose a group of - directives that will apply only to the named directory, - sub-directories of that directory, and the files within the respective - directories. Any directive that is allowed - in a directory context may be used. Directory-path is - either the full path to a directory, or a wild-card string using - Unix shell-style matching. In a wild-card string, ? matches - any single character, and * matches any sequences of - characters. You may also use [] character ranges. None - of the wildcards match a `/' character, so <Directory - /*/public_html> will not match - /home/user/public_html, but <Directory - /home/*/public_html> will match. Example:

- -

- <Directory /usr/local/httpd/htdocs> - - Options Indexes FollowSymLinks - - </Directory> -

- -

Be careful with the directory-path arguments: - They have to literally match the filesystem path which Apache httpd uses - to access the files. Directives applied to a particular - <Directory> will not apply to files accessed from - that same directory via a different path, such as via different symbolic - links.

- -

Regular - expressions can also be used, with the addition of the - ~ character. For example:

- -

- <Directory ~ "^/www/.*/[0-9]{3}"> -

- -

would match directories in /www/ that consisted of - three numbers.

- -

If multiple (non-regular expression) <Directory> sections - match the directory (or one of its parents) containing a document, - then the directives are applied in the order of shortest match - first, interspersed with the directives from the .htaccess files. For example, - with

- -

- <Directory /> - - AllowOverride None - - </Directory> - - <Directory /home/> - - AllowOverride FileInfo - - </Directory> -

- -

for access to the document /home/web/dir/doc.html - the steps are:

- -

Apply directive AllowOverride None - (disabling .htaccess files).
Apply directive AllowOverride FileInfo (for - directory /home).
Apply any FileInfo directives in - /home/.htaccess, /home/web/.htaccess and - /home/web/dir/.htaccess in that order.

- -

Regular expressions are not considered until after all of the - normal sections have been applied. Then all of the regular - expressions are tested in the order they appeared in the - configuration file. For example, with

- -

- <Directory ~ abc$> - - # ... directives here ... - - </Directory> -

- -

the regular expression section won't be considered until after - all normal <Directory>s and - .htaccess files have been applied. Then the regular - expression will match on /home/abc/public_html/abc and - the corresponding <Directory> will - be applied.

- -

Note that the default access for - <Directory /> is Allow from All. - This means that Apache httpd will serve any file mapped from an URL. It is - recommended that you change this with a block such - as

- -

- <Directory /> - - Order Deny,Allow - Deny from All - - </Directory> -

- -

and then override this for directories you - want accessible. See the Security Tips page for more - details.

- -

The directory sections occur in the httpd.conf file. - <Directory> directives - cannot nest, and cannot appear in a <Limit> or <LimitExcept> section.

- -

Consulte también

How <Directory>, - <Location> and <Files> sections work for an - explanation of how these different sections are combined when a - request is received

<DirectoryMatch> Directiva

- - - - - - -

Descripción:	Enclose directives that apply to -the contents of file-system directories matching a regular expression.
Sintaxis:	`<DirectoryMatch regex> -... </DirectoryMatch>`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

<DirectoryMatch> and - </DirectoryMatch> are used to enclose a group - of directives which will apply only to the named directory (and the files within), - the same as <Directory>. - However, it takes as an argument a - regular expression. For example:

- -

- <DirectoryMatch "^/www/(.+/)?[0-9]{3}"> -

- -

would match directories in /www/ that consisted of three - numbers.

- -

Compatability

- Prior to 2.3.9, this directive implicitly applied to sub-directories - (like <Directory>) and - could not match the end of line symbol ($). In 2.3.9 and later, - only directories that match the expression are affected by the enclosed - directives. -

- -

Trailing Slash

- This directive applies to requests for directories that may or may - not end in a trailing slash, so expressions that are anchored to the - end of line ($) must be written with care. -

- -

Consulte también

<Directory> for -a description of how regular expressions are mixed in with normal -<Directory>s
How <Directory>, <Location> and -<Files> sections work for an explanation of how these different -sections are combined when a request is received

DocumentRoot Directiva

- - - - - - - -

Descripción:	Directory that forms the main document tree visible -from the web
Sintaxis:	`DocumentRoot directory-path`
Valor por defecto:	`DocumentRoot /usr/local/apache/htdocs`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

This directive sets the directory from which httpd - will serve files. Unless matched by a directive like Alias, the server appends the - path from the requested URL to the document root to make the - path to the document. Example:

- -

- DocumentRoot /usr/web -

- -

then an access to - http://www.my.host.com/index.html refers to - /usr/web/index.html. If the directory-path is - not absolute then it is assumed to be relative to the ServerRoot.

- -

The DocumentRoot should be specified without - a trailing slash.

- -

Consulte también

Mapping URLs to Filesystem -Locations

<Else> Directiva

- - - - - - - -

Descripción:	Contains directives that apply only if the condition of a -previous `<If>` or -`<ElseIf>` section is not -satisfied by a request at runtime
Sintaxis:	`<Else> ... </Else>`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

Consulte también

<If>
<ElseIf>
How <Directory>, <Location>, - <Files> sections work for an explanation of how these - different sections are combined when a request is received. - <If>, - <ElseIf>, and - <Else> are applied last.

<ElseIf> Directiva

- - - - - - - -

Descripción:	Contains directives that apply only if a condition is satisfied -by a request at runtime while the condition of a previous -`<If>` or -`<ElseIf>` section is not -satisfied
Sintaxis:	`<ElseIf expression> ... </ElseIf>`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

Consulte también

Expressions in Apache HTTP Server, -for a complete reference and more examples.
<If>
<Else>
How <Directory>, <Location>, - <Files> sections work for an explanation of how these - different sections are combined when a request is received. - <If>, - <ElseIf>, and - <Else> are applied last.

EnableMMAP Directiva

- - - - - - - - -

Descripción:	Use memory-mapping to read files during delivery
Sintaxis:	`EnableMMAP On\|Off`
Valor por defecto:	`EnableMMAP On`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core

This directive controls whether the httpd may use - memory-mapping if it needs to read the contents of a file during - delivery. By default, when the handling of a request requires - access to the data within a file -- for example, when delivering a - server-parsed file using mod_include -- Apache httpd - memory-maps the file if the OS supports it.

- -

This memory-mapping sometimes yields a performance improvement. - But in some environments, it is better to disable the memory-mapping - to prevent operational problems:

- -

On some multiprocessor systems, memory-mapping can reduce the - performance of the httpd.
Deleting or truncating a file while httpd - has it memory-mapped can cause httpd to - crash with a segmentation fault. -

- -

For server configurations that are vulnerable to these problems, - you should disable memory-mapping of delivered files by specifying:

- -

- EnableMMAP Off -

- -

For NFS mounted files, this feature may be disabled explicitly for - the offending files by specifying:

- -

- <Directory "/path-to-nfs-files"> - - EnableMMAP Off - - </Directory> -

- -

EnableSendfile Directiva

- - - - - - - - - -

Descripción:	Use the kernel sendfile support to deliver files to the client
Sintaxis:	`EnableSendfile On\|Off`
Valor por defecto:	`EnableSendfile Off`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core
Compatibilidad:	Available in version 2.0.44 and later. Default changed to Off in -version 2.3.9.

This directive controls whether httpd may use the - sendfile support from the kernel to transmit file contents to the client. - By default, when the handling of a request requires no access - to the data within a file -- for example, when delivering a - static file -- Apache httpd uses sendfile to deliver the file contents - without ever reading the file if the OS supports it.

- -

This sendfile mechanism avoids separate read and send operations, - and buffer allocations. But on some platforms or within some - filesystems, it is better to disable this feature to avoid - operational problems:

- -

Some platforms may have broken sendfile support that the build - system did not detect, especially if the binaries were built on - another box and moved to such a machine with broken sendfile - support.
On Linux the use of sendfile triggers TCP-checksum - offloading bugs on certain networking cards when using IPv6.
On Linux on Itanium, sendfile may be unable to handle files - over 2GB in size.
With a network-mounted DocumentRoot (e.g., NFS, SMB, CIFS, FUSE), - the kernel may be unable to serve the network file through - its own cache.

- -

For server configurations that are not vulnerable to these problems, - you may enable this feature by specifying:

- -

- EnableSendfile On -

- -

For network mounted files, this feature may be disabled explicitly - for the offending files by specifying:

- -

- <Directory "/path-to-nfs-files"> - - EnableSendfile Off - - </Directory> -

Please note that the per-directory and .htaccess configuration - of EnableSendfile is not supported by - mod_cache_disk. - Only global definition of EnableSendfile - is taken into account by the module. -

- -

Error Directiva

- - - - - - - -

Descripción:	Abort configuration parsing with a custom error message
Sintaxis:	`Error message`
Contexto:	server config, virtual host, directory, .htaccess
Estado:	Core
Módulo:	core
Compatibilidad:	2.3.9 and later

If an error can be detected within the configuration, this - directive can be used to generate a custom error message, and halt - configuration parsing. The typical use is for reporting required - modules which are missing from the configuration.

- -

Example

- # ensure that mod_include is loaded - <IfModule !include_module> - Error mod_include is required by mod_foo. Load it with LoadModule. - </IfModule> - - # ensure that exactly one of SSL,NOSSL is defined - <IfDefine SSL> - <IfDefine NOSSL> - Error Both SSL and NOSSL are defined. Define only one of them. - </IfDefine> - </IfDefine> - <IfDefine !SSL> - <IfDefine !NOSSL> - Error Either SSL or NOSSL must be defined. - </IfDefine> - </IfDefine> -

- - -

ErrorDocument Directiva

- - - - - - - -

Descripción:	What the server will return to the client -in case of an error
Sintaxis:	`ErrorDocument error-code document`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core

In the event of a problem or error, Apache httpd can be configured - to do one of four things,

- -

output a simple hardcoded error message
output a customized message
redirect to a local URL-path to handle the - problem/error
redirect to an external URL to handle the - problem/error

- -

The first option is the default, while options 2-4 are - configured using the ErrorDocument - directive, which is followed by the HTTP response code and a URL - or a message. Apache httpd will sometimes offer additional information - regarding the problem/error.

- -

URLs can begin with a slash (/) for local web-paths (relative - to the DocumentRoot), or be a - full URL which the client can resolve. Alternatively, a message - can be provided to be displayed by the browser. Examples:

- -

- ErrorDocument 500 http://foo.example.com/cgi-bin/tester - ErrorDocument 404 /cgi-bin/bad_urls.pl - ErrorDocument 401 /subscription_info.html - ErrorDocument 403 "Sorry can't allow you access today" -

- -

Additionally, the special value default can be used - to specify Apache httpd's simple hardcoded message. While not required - under normal circumstances, default will restore - Apache httpd's simple hardcoded message for configurations that would - otherwise inherit an existing ErrorDocument.

- -

- ErrorDocument 404 /cgi-bin/bad_urls.pl - <Directory /web/docs> - - ErrorDocument 404 default - - </Directory> -

- -

Note that when you specify an ErrorDocument - that points to a remote URL (ie. anything with a method such as - http in front of it), Apache HTTP Server will send a redirect to the - client to tell it where to find the document, even if the - document ends up being on the same server. This has several - implications, the most important being that the client will not - receive the original error status code, but instead will - receive a redirect status code. This in turn can confuse web - robots and other clients which try to determine if a URL is - valid using the status code. In addition, if you use a remote - URL in an ErrorDocument 401, the client will not - know to prompt the user for a password since it will not - receive the 401 status code. Therefore, if you use an - ErrorDocument 401 directive then it must refer to a local - document.

- -

Microsoft Internet Explorer (MSIE) will by default ignore - server-generated error messages when they are "too small" and substitute - its own "friendly" error messages. The size threshold varies depending on - the type of error, but in general, if you make your error document - greater than 512 bytes, then MSIE will show the server-generated - error rather than masking it. More information is available in - Microsoft Knowledge Base article Q294807.

- -

Although most error messages can be overriden, there are certain - circumstances where the internal messages are used regardless of the - setting of ErrorDocument. In - particular, if a malformed request is detected, normal request processing - will be immediately halted and the internal error message returned. - This is necessary to guard against security problems caused by - bad requests.

- -

If you are using mod_proxy, you may wish to enable - ProxyErrorOverride so that you can provide - custom error messages on behalf of your Origin servers. If you don't enable ProxyErrorOverride, - Apache httpd will not generate custom error documents for proxied content.

- -

Consulte también

documentation of - customizable responses

ErrorLog Directiva

- - - - - - - -

Descripción:	Location where the server will log errors
Sintaxis:	`ErrorLog file-path\|syslog[:facility]`
Valor por defecto:	`ErrorLog logs/error_log (Unix) ErrorLog logs/error.log (Windows and OS/2)`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

The ErrorLog directive sets the name of - the file to which the server will log any errors it encounters. If - the file-path is not absolute then it is assumed to be - relative to the ServerRoot.

- -

Example

- ErrorLog /var/log/httpd/error_log -

- -

If the file-path - begins with a pipe character "|" then it is assumed to be a - command to spawn to handle the error log.

- -

Example

- ErrorLog "|/usr/local/bin/httpd_errors" -

- -

See the notes on piped logs for - more information.

- -

Using syslog instead of a filename enables logging - via syslogd(8) if the system supports it. The default is to use - syslog facility local7, but you can override this by - using the syslog:facility syntax where - facility can be one of the names usually documented in - syslog(1). The facility is effectively global, and if it is changed - in individual virtual hosts, the final facility specified affects the - entire server.

- -

Example

- ErrorLog syslog:user -

- -

SECURITY: See the security tips - document for details on why your security could be compromised - if the directory where log files are stored is writable by - anyone other than the user that starts the server.

Note

When entering a file path on non-Unix platforms, care should be taken - to make sure that only forward slashed are used even though the platform - may allow the use of back slashes. In general it is a good idea to always - use forward slashes throughout the configuration files.

- -

Consulte también

LogLevel
Apache HTTP Server Log Files

ErrorLogFormat Directiva

- - - - - - - -

Descripción:	Format specification for error log entries
Sintaxis:	`ErrorLog [connection\|request] format`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache httpd 2.3.9 and later

ErrorLogFormat allows to specify what - supplementary information is logged in the error log in addition to the - actual log message.

- -

Simple example

- ErrorLogFormat "[%t] [%l] [pid %P] %F: %E: [client %a] %M" -

- -

Specifying connection or request as first - paramter allows to specify additional formats, causing additional - information to be logged when the first message is logged for a specific - connection or request, respectivly. This additional information is only - logged once per connection/request. If a connection or request is processed - without causing any log message, the additional information is not logged - either.

- -

It can happen that some format string items do not produce output. For - example, the Referer header is only present if the log message is - associated to a request and the log message happens at a time when the - Referer header has already been read from the client. If no output is - produced, the default behaviour is to delete everything from the preceeding - space character to the next space character. This means the log line is - implicitly divided into fields on non-whitespace to whitespace transitions. - If a format string item does not produce output, the whole field is - ommitted. For example, if the remote address %a in the log - format [%t] [%l] [%a] %M is not available, the surrounding - brackets are not logged either. Space characters can be escaped with a - backslash to prevent them from delimiting a field. The combination '% ' - (percent space) is a zero-witdh field delimiter that does not produce any - output.

- -

The above behaviour can be changed by adding modifiers to the format - string item. A - (minus) modifier causes a minus to be logged if the - respective item does not produce any output. In once-per-connection/request - formats, it is also possible to use the + (plus) modifier. If an - item with the plus modifier does not produce any output, the whole line is - ommitted.

- -

A number as modifier can be used to assign a log severity level to a - format item. The item will only be logged if the severity of the log - message is not higher than the specified log severity level. The number can - range from 1 (alert) over 4 (warn) and 7 (debug) to 15 (trace8).

- -

Some format string items accept additional parameters in braces.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Format String	Description
`%%`	The percent sign
`%...a`	Remote IP-address and port
`%...A`	Local IP-address and port
`%...{name}e`	Request environment variable `name`
`%...E`	APR/OS error status code and string
`%...F`	Source file name and line number of the log call
`%...{name}i`	Request header `name`
`%...k`	Number of keep-alive requests on this connection
`%...l`	Loglevel of the message
`%...L`	Log ID of the request
`%...{c}L`	Log ID of the connection
`%...{C}L`	Log ID of the connection if used in connection scope, empty otherwise
`%...m`	Name of the module logging the message
`%M`	The actual log message
`%...{name}n`	Request note `name`
`%...P`	Process ID of current process
`%...T`	Thread ID of current thread
`%...t`	The current time
`%...{u}t`	The current time including micro-seconds
`%...{cu}t`	The current time in compact ISO 8601 format, including - micro-seconds
`%...v`	The canonical `ServerName` - of the current server.
`%...V`	The server name of the server serving the request according to the - `UseCanonicalName` - setting.
`\` (backslash space)	Non-field delimiting space
`%` (percent space)	Field delimiter (no output)

- -

The log ID format %L produces a unique id for a connection - or request. This can be used to correlate which log lines belong to the - same connection or request, which request happens on which connection. - A %L format string is also available in - mod_log_config, to allow to correlate access log entries - with error log lines. If mod_unique_id is loaded, its - unique id will be used as log ID for requests.

- -

Example (somewhat similar to default format)

- ErrorLogFormat "[%{u}t] [%-m:%l] [pid %P] %7F: %E: [client\ %a] - %M% ,\ referer\ %{Referer}i" -

- -

Example (similar to the 2.2.x format)

- ErrorLogFormat "[%t] [%l] %7F: %E: [client\ %a] - %M% ,\ referer\ %{Referer}i" -

- -

Advanced example with request/connection log IDs

- ErrorLogFormat "[%{uc}t] [%-m:%-l] [R:%L] [C:%{C}L] %7F: %E: %M" - ErrorLogFormat request "[%{uc}t] [R:%L] Request %k on C:%{c}L pid:%P tid:%T" - ErrorLogFormat request "[%{uc}t] [R:%L] UA:'%+{User-Agent}i'" - ErrorLogFormat request "[%{uc}t] [R:%L] Referer:'%+{Referer}i'" - ErrorLogFormat connection "[%{uc}t] [C:%{c}L] local\ %a remote\ %A" -

- - -

Consulte también

ExtendedStatus Directiva

- - - - - - - -

Descripción:	Keep track of extended status information for each -request
Sintaxis:	`ExtendedStatus On\|Off`
Valor por defecto:	`ExtendedStatus Off[*]`
Contexto:	server config
Estado:	Core
Módulo:	core

This option tracks additional data per worker about the - currently executing request, and a utilization summary; you - can see these variables during runtime by configuring - mod_status. Note that other modules may - rely on this scoreboard.

- -

This setting applies to the entire server, and cannot be - enabled or disabled on a virtualhost-by-virtualhost basis. - The collection of extended status information can slow down - the server. Also note that this setting cannot be changed - during a graceful restart.

- -

Note that loading mod_status will change - the default behavior to ExtendedStatus On, while other - third party modules may do the same. Such modules rely on - collecting detailed information about the state of all workers. - The default is changed by mod_status beginning - with version 2.3.6; the previous default was always Off.

- - -

FileETag Directiva

- - - - - - - - -

Descripción:	File attributes used to create the ETag -HTTP response header for static files
Sintaxis:	`FileETag component ...`
Valor por defecto:	`FileETag INode MTime Size`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core

- The FileETag directive configures the file - attributes that are used to create the ETag (entity - tag) response header field when the document is based on a static file. - (The ETag value is used in cache management to save - network bandwidth.) The - FileETag directive allows you to choose - which of these -- if any -- should be used. The recognized keywords are: -

- -

INode: The file's i-node number will be included in the calculation
MTime: The date and time the file was last modified will be included
Size: The number of bytes in the file will be included
All: All available fields will be used. This is equivalent to: -
FileETag INode MTime Size
None: If a document is file-based, no ETag field will be - included in the response

- -

The INode, MTime, and Size - keywords may be prefixed with either + or -, - which allow changes to be made to the default setting inherited - from a broader scope. Any keyword appearing without such a prefix - immediately and completely cancels the inherited setting.

- -

If a directory's configuration includes - FileETag INode MTime Size, and a - subdirectory's includes FileETag -INode, - the setting for that subdirectory (which will be inherited by - any sub-subdirectories that don't override it) will be equivalent to - FileETag MTime Size.

Warning

- Do not change the default for directories or locations that have WebDAV - enabled and use mod_dav_fs as a storage provider. - mod_dav_fs uses INode MTime Size - as a fixed format for ETag comparisons on conditional requests. - These conditional requests will break if the ETag format is - changed via FileETag. -

Server Side Includes

- An ETag is not generated for responses parsed by mod_include, - since the response entity can change without a change of the INode, MTime, or Size - of the static file with embedded SSI directives. -

- - -

<Files> Directiva

- - - - - - - -

Descripción:	Contains directives that apply to matched -filenames
Sintaxis:	`<Files filename> ... </Files>`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

The <Files> directive - limits the scope of the enclosed directives by filename. It is comparable - to the <Directory> - and <Location> - directives. It should be matched with a </Files> - directive. The directives given within this section will be applied to - any object with a basename (last component of filename) matching the - specified filename. <Files> - sections are processed in the order they appear in the - configuration file, after the <Directory> sections and - .htaccess files are read, but before <Location> sections. Note - that <Files> can be nested - inside <Directory> sections to restrict the - portion of the filesystem they apply to.

- -

The filename argument should include a filename, or - a wild-card string, where ? matches any single character, - and * matches any sequences of characters. - Regular expressions - can also be used, with the addition of the - ~ character. For example:

- -

- <Files ~ "\.(gif|jpe?g|png)$"> -

- -

would match most common Internet graphics formats. <FilesMatch> is preferred, - however.

- -

Note that unlike <Directory> and <Location> sections, <Files> sections can be used inside - .htaccess files. This allows users to control access to - their own files, at a file-by-file level.

- - -

Consulte también

How <Directory>, <Location> - and <Files> sections work for an explanation of how these - different sections are combined when a request is received

<FilesMatch> Directiva

- - - - - - - -

Descripción:	Contains directives that apply to regular-expression matched -filenames
Sintaxis:	`<FilesMatch regex> ... </FilesMatch>`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

The <FilesMatch> directive - limits the scope of the enclosed directives by filename, just as the - <Files> directive - does. However, it accepts a regular - expression. For example:

- -

- <FilesMatch "\.(gif|jpe?g|png)$"> -

- -

would match most common Internet graphics formats.

- -

Consulte también

How <Directory>, <Location> - and <Files> sections work for an explanation of how these - different sections are combined when a request is received

ForceType Directiva

- - - - - - - - -

Descripción:	Forces all matching files to be served with the specified -media type in the HTTP Content-Type header field
Sintaxis:	`ForceType media-type\|None`
Contexto:	directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core
Compatibilidad:	Moved to the core in Apache httpd 2.0

When placed into an .htaccess file or a - <Directory>, or - <Location> or - <Files> - section, this directive forces all matching files to be served - with the content type identification given by - media-type. For example, if you had a directory full of - GIF files, but did not want to label them all with .gif, - you might want to use:

- -

- ForceType image/gif -

- -

Note that this directive overrides other indirect media type - associations defined in mime.types or via the - AddType.

- -

You can also override more general - ForceType settings - by using the value of None:

- -

- # force all files to be image/gif: - <Location /images> - - ForceType image/gif - - </Location> - - # but normal mime-type associations here: - <Location /images/mixed> - - ForceType None - - </Location> -

- -

This directive primarily overrides the content types generated for - static files served out of the filesystem. For resources other than - static files, where the generator of the response typically specifies - a Content-Type, this directive has no effect.

- - -

GprofDir Directiva

- - - - - - -

Descripción:	Directory to write gmon.out profiling data to.
Sintaxis:	`GprofDir /tmp/gprof/\|/tmp/gprof/%`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

When the server has been compiled with gprof profiling support, - GprofDir causes gmon.out files to - be written to the specified directory when the process exits. If the - argument ends with a percent symbol ('%'), subdirectories are created - for each process id.

- -

This directive currently only works with the prefork - MPM.

- -

HostnameLookups Directiva

- - - - - - - -

Descripción:	Enables DNS lookups on client IP addresses
Sintaxis:	`HostnameLookups On\|Off\|Double`
Valor por defecto:	`HostnameLookups Off`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core

This directive enables DNS lookups so that host names can be - logged (and passed to CGIs/SSIs in REMOTE_HOST). - The value Double refers to doing double-reverse - DNS lookup. That is, after a reverse lookup is performed, a forward - lookup is then performed on that result. At least one of the IP - addresses in the forward lookup must match the original - address. (In "tcpwrappers" terminology this is called - PARANOID.)

- -

Regardless of the setting, when mod_authz_host is - used for controlling access by hostname, a double reverse lookup - will be performed. This is necessary for security. Note that the - result of this double-reverse isn't generally available unless you - set HostnameLookups Double. For example, if only - HostnameLookups On and a request is made to an object - that is protected by hostname restrictions, regardless of whether - the double-reverse fails or not, CGIs will still be passed the - single-reverse result in REMOTE_HOST.

- -

The default is Off in order to save the network - traffic for those sites that don't truly need the reverse - lookups done. It is also better for the end users because they - don't have to suffer the extra latency that a lookup entails. - Heavily loaded sites should leave this directive - Off, since DNS lookups can take considerable - amounts of time. The utility logresolve, compiled by - default to the bin subdirectory of your installation - directory, can be used to look up host names from logged IP addresses - offline.

- -

<If> Directiva

- - - - - - - -

Descripción:	Contains directives that apply only if a condition is -satisfied by a request at runtime
Sintaxis:	`<If expression> ... </If>`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

The <If> directive - evaluates an expression at runtime, and applies the enclosed - directives if and only if the expression evaluates to true. - For example:

- -

- <If "$req{Host} = ''"> -

- -

would match HTTP/1.0 requests without a Host: header.

- -

You may compare the value of any variable in the request headers - ($req), response headers ($resp) or environment ($env) in your - expression.

- -

Apart from =, If can use the IN - operator to compare if the expression is in a given range:

- -

- <If %{REQUEST_METHOD} IN GET,HEAD,OPTIONS> -

- - -

Consulte también

Expressions in Apache HTTP Server, -for a complete reference and more examples.
How <Directory>, <Location>, - <Files> sections work for an explanation of how these - different sections are combined when a request is received. - <If> has the same precedence - and usage as <Files>

<IfDefine> Directiva

- - - - - - - -

Descripción:	Encloses directives that will be processed only -if a test is true at startup
Sintaxis:	`<IfDefine [!]parameter-name> ... - </IfDefine>`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

The <IfDefine test>...</IfDefine> - section is used to mark directives that are conditional. The - directives within an <IfDefine> - section are only processed if the test is true. If - test is false, everything between the start and end markers is - ignored.

- -

The test in the <IfDefine> section directive can be one of two forms:

- -

parameter-name
!parameter-name

- -

In the former case, the directives between the start and end - markers are only processed if the parameter named - parameter-name is defined. The second format reverses - the test, and only processes the directives if - parameter-name is not defined.

- -

The parameter-name argument is a define as given on the - httpd command line via -Dparameter - at the time the server was started or by the Define directive.

- -

<IfDefine> sections are - nest-able, which can be used to implement simple - multiple-parameter tests. Example:

- -

- httpd -DReverseProxy -DUseCache -DMemCache ... - - # httpd.conf - <IfDefine ReverseProxy> - - LoadModule proxy_module modules/mod_proxy.so - LoadModule proxy_http_module modules/mod_proxy_http.so - <IfDefine UseCache> - - LoadModule cache_module modules/mod_cache.so - <IfDefine MemCache> - - LoadModule mem_cache_module modules/mod_mem_cache.so - - </IfDefine> - <IfDefine !MemCache> - - LoadModule cache_disk_module modules/mod_cache_disk.so - - </IfDefine> - - </IfDefine> - - </IfDefine> -

- -

<IfModule> Directiva

- - - - - - - - -

Descripción:	Encloses directives that are processed conditional on the -presence or absence of a specific module
Sintaxis:	`<IfModule [!]module-file\|module-identifier> ... - </IfModule>`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core
Compatibilidad:	Module identifiers are available in version 2.1 and -later.

The <IfModule test>...</IfModule> - section is used to mark directives that are conditional on the presence of - a specific module. The directives within an <IfModule> section are only processed if the test - is true. If test is false, everything between the start and - end markers is ignored.

- -

The test in the <IfModule> section directive can be one of two forms:

- -

module
!module

- -

In the former case, the directives between the start and end - markers are only processed if the module named module - is included in Apache httpd -- either compiled in or - dynamically loaded using LoadModule. The second format reverses the test, - and only processes the directives if module is - not included.

- -

The module argument can be either the module identifier or - the file name of the module, at the time it was compiled. For example, - rewrite_module is the identifier and - mod_rewrite.c is the file name. If a module consists of - several source files, use the name of the file containing the string - STANDARD20_MODULE_STUFF.

- -

<IfModule> sections are - nest-able, which can be used to implement simple multiple-module - tests.

- -

This section should only be used if you need to have one - configuration file that works whether or not a specific module - is available. In normal operation, directives need not be - placed in <IfModule> - sections.

- -

Include Directiva

- - - - - - - -

Descripción:	Includes other configuration files from within -the server configuration files
Sintaxis:	`Include [optional\|strict] file-path\|directory-path\|wildcard`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core
Compatibilidad:	Wildcard matching available in 2.0.41 and later, directory -wildcard matching available in 2.3.6 and later

This directive allows inclusion of other configuration files - from within the server configuration files.

- -

Shell-style (fnmatch()) wildcard characters can be used - in the filename or directory parts of the path to include several files - at once, in alphabetical order. In addition, if - Include points to a directory, rather than a file, - Apache httpd will read all files in that directory and any subdirectory. - However, including entire directories is not recommended, because it is - easy to accidentally leave temporary files in a directory that can cause - httpd to fail. Instead, we encourage you to use the - wildcard syntax shown below, to include files that match a particular - pattern, such as *.conf, for example.

- -

When a wildcard is specified for a file component of - the path, and no file matches the wildcard, the - Include - directive will be silently ignored. When a wildcard is - specified for a directory component of the path, and - no directory matches the wildcard, the - Include directive will - fail with an error saying the directory cannot be found. -

- -

For further control over the behaviour of the server when no files or - directories match, prefix the path with the modifiers optional - or strict. If optional is specified, any wildcard - file or directory that does not match will be silently ignored. If - strict is specified, any wildcard file or directory that does - not match at least one file will cause server startup to fail.

- -

When a directory or file component of the path is - specified exactly, and that directory or file does not exist, - Include directive will fail with an - error saying the file or directory cannot be found.

- -

The file path specified may be an absolute path, or may be relative - to the ServerRoot directory.

- -

Examples:

- -

- Include /usr/local/apache2/conf/ssl.conf - Include /usr/local/apache2/conf/vhosts/*.conf -

- -

Or, providing paths relative to your ServerRoot directory:

- -

- Include conf/ssl.conf - Include conf/vhosts/*.conf -

- -

Wildcards may be included in the directory or file portion of the - path. In the following example, the server will fail to load if no - directories match conf/vhosts/*, but will load successfully if no - files match *.conf.

- -

- Include conf/vhosts/*/vhost.conf - Include conf/vhosts/*/*.conf -

- -

In this example, the server will fail to load if either - conf/vhosts/* matches no directories, or if *.conf matches no files:

- -

- Include strict conf/vhosts/*/*.conf -

- -

In this example, the server load successfully if either conf/vhosts/* - matches no directories, or if *.conf matches no files:

- -

- Include optional conf/vhosts/*/*.conf -

- - -

Consulte también

apachectl

IncludeOptional Directiva

- - - - - - - -

Descripción:	Includes other configuration files from within -the server configuration files
Sintaxis:	`IncludeOptional file-path\|directory-path\|wildcard`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core
Compatibilidad:	Available in 2.3.6 and later

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

Consulte también

Include
apachectl

KeepAlive Directiva

- - - - - - - -

Descripción:	Enables HTTP persistent connections
Sintaxis:	`KeepAlive On\|Off`
Valor por defecto:	`KeepAlive On`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

The Keep-Alive extension to HTTP/1.0 and the persistent - connection feature of HTTP/1.1 provide long-lived HTTP sessions - which allow multiple requests to be sent over the same TCP - connection. In some cases this has been shown to result in an - almost 50% speedup in latency times for HTML documents with - many images. To enable Keep-Alive connections, set - KeepAlive On.

- -

For HTTP/1.0 clients, Keep-Alive connections will only be - used if they are specifically requested by a client. In - addition, a Keep-Alive connection with an HTTP/1.0 client can - only be used when the length of the content is known in - advance. This implies that dynamic content such as CGI output, - SSI pages, and server-generated directory listings will - generally not use Keep-Alive connections to HTTP/1.0 clients. - For HTTP/1.1 clients, persistent connections are the default - unless otherwise specified. If the client requests it, chunked - encoding will be used in order to send content of unknown - length over persistent connections.

- -

When a client uses a Keep-Alive connection it will be counted - as a single "request" for the MaxConnectionsPerChild directive, regardless - of how many requests are sent using the connection.

- -

Consulte también

MaxKeepAliveRequests

KeepAliveTimeout Directiva

- - - - - - - - -

Descripción:	Amount of time the server will wait for subsequent -requests on a persistent connection
Sintaxis:	`KeepAliveTimeout num[ms]`
Valor por defecto:	`KeepAliveTimeout 5`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Specifying a value in milliseconds is available in -Apache httpd 2.3.2 and later

The number of seconds Apache httpd will wait for a subsequent - request before closing the connection. By adding a postfix of ms the - timeout can be also set in milliseconds. Once a request has been - received, the timeout value specified by the - Timeout directive applies.

- -

Setting KeepAliveTimeout to a high value - may cause performance problems in heavily loaded servers. The - higher the timeout, the more server processes will be kept - occupied waiting on connections with idle clients.

- -

In a name-based virtual host context, the value of the first - defined virtual host (the default host) in a set of NameVirtualHost will be used. - The other values will be ignored.

- -

<Limit> Directiva

- - - - - - - -

Descripción:	Restrict enclosed access controls to only certain HTTP -methods
Sintaxis:	`<Limit method [method] ... > ... - </Limit>`
Contexto:	directory, .htaccess
Anula:	AuthConfig, Limit
Estado:	Core
Módulo:	core

Access controls are normally effective for - all access methods, and this is the usual - desired behavior. In the general case, access control - directives should not be placed within a - <Limit> section.

- -

The purpose of the <Limit> - directive is to restrict the effect of the access controls to the - nominated HTTP methods. For all other methods, the access - restrictions that are enclosed in the <Limit> bracket will have no - effect. The following example applies the access control - only to the methods POST, PUT, and - DELETE, leaving all other methods unprotected:

- -

- <Limit POST PUT DELETE> - - Require valid-user - - </Limit> -

- -

The method names listed can be one or more of: GET, - POST, PUT, DELETE, - CONNECT, OPTIONS, - PATCH, PROPFIND, PROPPATCH, - MKCOL, COPY, MOVE, - LOCK, and UNLOCK. The method name is - case-sensitive. If GET is used it will also - restrict HEAD requests. The TRACE method - cannot be limited (see TraceEnable).

- -

A <LimitExcept> section should always be - used in preference to a <Limit> - section when restricting access, since a <LimitExcept> section provides protection - against arbitrary methods.

- -

The <Limit> and - <LimitExcept> - directives may be nested. In this case, each successive level of - <Limit> or <LimitExcept> directives must - further restrict the set of methods to which access controls apply.

- -

When using - <Limit> or - <LimitExcept> directives with - the Require directive, - note that the first Require - to succeed authorizes the request, regardless of the presence of other - Require directives.

- -

For example, given the following configuration, all users will - be authorized for POST requests, and the - Require group editors directive will be ignored - in all cases:

- -

- <LimitExcept GET> - - Require valid-user - - </LimitExcept> - <Limit POST> - - Require group editors - - </Limit> -

- -

<LimitExcept> Directiva

- - - - - - - -

Descripción:	Restrict access controls to all HTTP methods -except the named ones
Sintaxis:	`<LimitExcept method [method] ... > ... - </LimitExcept>`
Contexto:	directory, .htaccess
Anula:	AuthConfig, Limit
Estado:	Core
Módulo:	core

<LimitExcept> and - </LimitExcept> are used to enclose - a group of access control directives which will then apply to any - HTTP access method not listed in the arguments; - i.e., it is the opposite of a <Limit> section and can be used to control - both standard and nonstandard/unrecognized methods. See the - documentation for <Limit> for more details.

- -

For example:

- -

- <LimitExcept POST GET> - - Require valid-user - - </LimitExcept> -

- - -

LimitInternalRecursion Directiva

- - - - - - - - -

Descripción:	Determine maximum number of internal redirects and nested -subrequests
Sintaxis:	`LimitInternalRecursion number [number]`
Valor por defecto:	`LimitInternalRecursion 10`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache httpd 2.0.47 and later

An internal redirect happens, for example, when using the Action directive, which internally - redirects the original request to a CGI script. A subrequest is Apache httpd's - mechanism to find out what would happen for some URI if it were requested. - For example, mod_dir uses subrequests to look for the - files listed in the DirectoryIndex - directive.

- -

LimitInternalRecursion prevents the server - from crashing when entering an infinite loop of internal redirects or - subrequests. Such loops are usually caused by misconfigurations.

- -

The directive stores two different limits, which are evaluated on - per-request basis. The first number is the maximum number of - internal redirects, that may follow each other. The second number - determines, how deep subrequests may be nested. If you specify only one - number, it will be assigned to both limits.

- -

Example

- LimitInternalRecursion 5 -

- -

LimitRequestBody Directiva

- - - - - - - - -

Descripción:	Restricts the total size of the HTTP request body sent -from the client
Sintaxis:	`LimitRequestBody bytes`
Valor por defecto:	`LimitRequestBody 0`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

This directive specifies the number of bytes from 0 - (meaning unlimited) to 2147483647 (2GB) that are allowed in a - request body. See the note below for the limited applicability - to proxy requests.

- -

The LimitRequestBody directive allows - the user to set a limit on the allowed size of an HTTP request - message body within the context in which the directive is given - (server, per-directory, per-file or per-location). If the client - request exceeds that limit, the server will return an error - response instead of servicing the request. The size of a normal - request message body will vary greatly depending on the nature of - the resource and the methods allowed on that resource. CGI scripts - typically use the message body for retrieving form information. - Implementations of the PUT method will require - a value at least as large as any representation that the server - wishes to accept for that resource.

- -

This directive gives the server administrator greater - control over abnormal client request behavior, which may be - useful for avoiding some forms of denial-of-service - attacks.

- -

If, for example, you are permitting file upload to a particular - location, and wish to limit the size of the uploaded file to 100K, - you might use the following directive:

- -

- LimitRequestBody 102400 -

- -

For a full description of how this directive is interpreted by - proxy requests, see the mod_proxy documentation.

- - -

LimitRequestFields Directiva

- - - - - - - -

Descripción:	Limits the number of HTTP request header fields that -will be accepted from the client
Sintaxis:	`LimitRequestFields number`
Valor por defecto:	`LimitRequestFields 100`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

Number is an integer from 0 (meaning unlimited) to - 32767. The default value is defined by the compile-time - constant DEFAULT_LIMIT_REQUEST_FIELDS (100 as - distributed).

- -

The LimitRequestFields directive allows - the server administrator to modify the limit on the number of - request header fields allowed in an HTTP request. A server needs - this value to be larger than the number of fields that a normal - client request might include. The number of request header fields - used by a client rarely exceeds 20, but this may vary among - different client implementations, often depending upon the extent - to which a user has configured their browser to support detailed - content negotiation. Optional HTTP extensions are often expressed - using request header fields.

- -

This directive gives the server administrator greater - control over abnormal client request behavior, which may be - useful for avoiding some forms of denial-of-service attacks. - The value should be increased if normal clients see an error - response from the server that indicates too many fields were - sent in the request.

- -

For example:

- -

- LimitRequestFields 50 -

- -

Warning

When name-based virtual hosting is used, the value for this - directive is taken from the default (first-listed) virtual host for the - NameVirtualHost the connection was mapped to.

- - -

LimitRequestFieldSize Directiva

- - - - - - - -

Descripción:	Limits the size of the HTTP request header allowed from the -client
Sintaxis:	`LimitRequestFieldSize bytes`
Valor por defecto:	`LimitRequestFieldSize 8190`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

This directive specifies the number of bytes - that will be allowed in an HTTP request header.

- -

The LimitRequestFieldSize directive - allows the server administrator to reduce or increase the limit - on the allowed size of an HTTP request header field. A server - needs this value to be large enough to hold any one header field - from a normal client request. The size of a normal request header - field will vary greatly among different client implementations, - often depending upon the extent to which a user has configured - their browser to support detailed content negotiation. SPNEGO - authentication headers can be up to 12392 bytes.

- -

This directive gives the server administrator greater - control over abnormal client request behavior, which may be - useful for avoiding some forms of denial-of-service attacks.

- -

For example:

- -

- LimitRequestFieldSize 4094 -

- -

Under normal conditions, the value should not be changed from - the default.

- -

Warning

When name-based virtual hosting is used, the value for this - directive is taken from the default (first-listed) virtual host for the - NameVirtualHost the connection was mapped to.

- - -

LimitRequestLine Directiva

- - - - - - - -

Descripción:	Limit the size of the HTTP request line that will be accepted -from the client
Sintaxis:	`LimitRequestLine bytes`
Valor por defecto:	`LimitRequestLine 8190`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

This directive sets the number of bytes that will be - allowed on the HTTP request-line.

- -

The LimitRequestLine directive allows - the server administrator to reduce or increase the limit on the allowed size - of a client's HTTP request-line. Since the request-line consists of the - HTTP method, URI, and protocol version, the - LimitRequestLine directive places a - restriction on the length of a request-URI allowed for a request - on the server. A server needs this value to be large enough to - hold any of its resource names, including any information that - might be passed in the query part of a GET request.

- -

This directive gives the server administrator greater - control over abnormal client request behavior, which may be - useful for avoiding some forms of denial-of-service attacks.

- -

For example:

- -

- LimitRequestLine 4094 -

- -

Under normal conditions, the value should not be changed from - the default.

- -

Warning

When name-based virtual hosting is used, the value for this - directive is taken from the default (first-listed) virtual host for the - NameVirtualHost the connection was mapped to.

- - -

LimitXMLRequestBody Directiva

- - - - - - - - -

Descripción:	Limits the size of an XML-based request body
Sintaxis:	`LimitXMLRequestBody bytes`
Valor por defecto:	`LimitXMLRequestBody 1000000`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

Limit (in bytes) on maximum size of an XML-based request - body. A value of 0 will disable any checking.

- -

Example:

- -

- LimitXMLRequestBody 0 -

- - -

<Location> Directiva

- - - - - - -

Descripción:	Applies the enclosed directives only to matching -URLs
Sintaxis:	`<Location - URL-path\|URL> ... </Location>`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

The <Location> directive - limits the scope of the enclosed directives by URL. It is similar to the - <Directory> - directive, and starts a subsection which is terminated with a - </Location> directive. <Location> sections are processed in the - order they appear in the configuration file, after the <Directory> sections and - .htaccess files are read, and after the <Files> sections.

- -

<Location> sections operate - completely outside the filesystem. This has several consequences. - Most importantly, <Location> - directives should not be used to control access to filesystem - locations. Since several different URLs may map to the same - filesystem location, such access controls may by circumvented.

- -

The enclosed directives will be applied to the request if the path component - of the URL meets any of the following criteria: -

The specified location matches exactly the path component of the URL. -
The specified location, which ends in a forward slash, is a prefix - of the path component of the URL (treated as a context root). -
The specified location, with the addition of a trailing slash, is a - prefix of the path component of the URL (also treated as a context root). -

- In the example below, where no trailing slash is used, requests to - /private1, /private1/ and /private1/file.txt will have the enclosed - directives applied, but /private1other would not. -

- <Location /private1> - ... -

- In the example below, where a trailing slash is used, requests to - /private2/ and /private2/file.txt will have the enclosed - directives applied, but /private2 and /private2other would not. -

- <Location /private2/> - ... -

- -

When to use `<Location>`

- -

Use <Location> to apply - directives to content that lives outside the filesystem. For - content that lives in the filesystem, use <Directory> and <Files>. An exception is - <Location />, which is an easy way to - apply a configuration to the entire server.

- -

For all origin (non-proxy) requests, the URL to be matched is a - URL-path of the form /path/. No scheme, hostname, - port, or query string may be included. For proxy requests, the - URL to be matched is of the form - scheme://servername/path, and you must include the - prefix.

- -

The URL may use wildcards. In a wild-card string, ? matches - any single character, and * matches any sequences of - characters. Neither wildcard character matches a / in the URL-path.

- -

Regular expressions - can also be used, with the addition of the ~ - character. For example:

- -

- <Location ~ "/(extra|special)/data"> -

- -

would match URLs that contained the substring /extra/data - or /special/data. The directive <LocationMatch> behaves - identical to the regex version of <Location>, and is preferred, for the - simple reason that ~ is hard to distinguish from - - in many fonts.

- -

The <Location> - functionality is especially useful when combined with the - SetHandler - directive. For example, to enable status requests, but allow them - only from browsers at example.com, you might use:

- -

- <Location /status> - - SetHandler server-status - Require host example.com - - </Location> -

- -

Note about / (slash)

The slash character has special meaning depending on where in a - URL it appears. People may be used to its behavior in the filesystem - where multiple adjacent slashes are frequently collapsed to a single - slash (i.e., /home///foo is the same as - /home/foo). In URL-space this is not necessarily true. - The <LocationMatch> - directive and the regex version of <Location> require you to explicitly specify multiple - slashes if that is your intention.

- -

For example, <LocationMatch ^/abc> would match - the request URL /abc but not the request URL - //abc. The (non-regex) <Location> directive behaves similarly when used for - proxy requests. But when (non-regex) <Location> is used for non-proxy requests it will - implicitly match multiple slashes with a single slash. For example, - if you specify <Location /abc/def> and the - request is to /abc//def then it will match.

- -

Consulte también

How <Directory>, <Location> - and <Files> sections work for an explanation of how these - different sections are combined when a request is received.
LocationMatch

<LocationMatch> Directiva

- - - - - - -

Descripción:	Applies the enclosed directives only to regular-expression -matching URLs
Sintaxis:	`<LocationMatch - regex> ... </LocationMatch>`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

The <LocationMatch> directive - limits the scope of the enclosed directives by URL, in an identical manner - to <Location>. However, - it takes a regular expression - as an argument instead of a simple string. For example:

- -

- <LocationMatch "/(extra|special)/data"> -

- -

would match URLs that contained the substring /extra/data - or /special/data.

- -

Consulte también

How <Directory>, <Location> - and <Files> sections work for an explanation of how these - different sections are combined when a request is received

LogLevel Directiva

- - - - - - - - -

Descripción:	Controls the verbosity of the ErrorLog
Sintaxis:	`LogLevel [module:]level - [module:level] ... -`
Valor por defecto:	`LogLevel warn`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core
Compatibilidad:	Per-module and per-directory configuration is available in - Apache HTTP Server 2.3.6 and later

LogLevel adjusts the verbosity of the - messages recorded in the error logs (see ErrorLog directive). The following - levels are available, in order of decreasing - significance:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Level	Description	Example
`emerg`	Emergencies - system is unusable.	"Child cannot open lock file. Exiting"
`alert`	Action must be taken immediately.	"getpwuid: couldn't determine user name from uid"
`crit`	Critical Conditions.	"socket: Failed to get a socket, exiting child"
`error`	Error conditions.	"Premature end of script headers"
`warn`	Warning conditions.	"child process 1234 did not exit, sending another - SIGHUP"
`notice`	Normal but significant condition.	"httpd: caught SIGBUS, attempting to dump core in - ..."
`info`	Informational.	"Server seems busy, (you may need to increase - StartServers, or Min/MaxSpareServers)..."
`debug`	Debug-level messages	"Opening config file ..."
`trace1`	Trace messages	"proxy: FTP: control connection complete"
`trace2`	Trace messages	"proxy: CONNECT: sending the CONNECT request to the remote proxy"
`trace3`	Trace messages	"openssl: Handshake: start"
`trace4`	Trace messages	"read from buffered SSL brigade, mode 0, 17 bytes"
`trace5`	Trace messages	"map lookup FAILED: map=rewritemap key=keyname"
`trace6`	Trace messages	"cache lookup FAILED, forcing new map lookup"
`trace7`	Trace messages, dumping large amounts of data	"\| 0000: 02 23 44 30 13 40 ac 34 df 3d bf 9a 19 49 39 15 \|"
`trace8`	Trace messages, dumping large amounts of data	"\| 0000: 02 23 44 30 13 40 ac 34 df 3d bf 9a 19 49 39 15 \|"

- -

When a particular level is specified, messages from all - other levels of higher significance will be reported as well. - E.g., when LogLevel info is specified, - then messages with log levels of notice and - warn will also be posted.

- -

Using a level of at least crit is - recommended.

- -

For example:

- -

- LogLevel notice -

- -

Note

When logging to a regular file messages of the level - notice cannot be suppressed and thus are always - logged. However, this doesn't apply when logging is done - using syslog.

- -

Specifying a level without a module name will reset the level - for all modules to that level. Specifying a level with a module - name will set the level for that module only. It is possible to - use the module source file name, the module identifier, or the - module identifier with the trailing _module omitted - as module specification. This means the following three specifications - are equivalent:

- -

- LogLevel info ssl:warn - LogLevel info mod_ssl.c:warn - LogLevel info ssl_module:warn -

- -

It is also possible to change the level per directory:

- -

- LogLevel info - <Directory /usr/local/apache/htdocs/app> - LogLevel debug - </Files> -

- -

- Per directory loglevel configuration only affects messages that are - logged after the request has been parsed and that are associated with - the request. Log messages which are associated with the connection or - the server are not affected. -

- -

LogLevelOverride Directiva

- - - - - - - - -

Descripción:	Override the verbosity of the ErrorLog for certain clients
Sintaxis:	`LogLevel ipaddress[/prefixlen] - [module:]level [module:level] ... -`
Valor por defecto:	`unset`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache HTTP Server 2.5.0 and later

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

Consulte también

LogLevel

MaxKeepAliveRequests Directiva

- - - - - - - -

Descripción:	Number of requests allowed on a persistent -connection
Sintaxis:	`MaxKeepAliveRequests number`
Valor por defecto:	`MaxKeepAliveRequests 100`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

The MaxKeepAliveRequests directive - limits the number of requests allowed per connection when - KeepAlive is on. If it is - set to 0, unlimited requests will be allowed. We - recommend that this setting be kept to a high value for maximum - server performance.

- -

For example:

- -

- MaxKeepAliveRequests 500 -

- -

MaxRangeOverlaps Directiva

- - - - - - - - -

Descripción:	Number of overlapping ranges (eg: `100-200,150-300`) allowed before returning the complete - resource
Sintaxis:	`MaxRangeOverlaps default \| unlimited \| none \| number-of-ranges`
Valor por defecto:	`MaxRangeOverlaps 20`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache HTTP Server 2.3.15 and later

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

MaxRangeReversals Directiva

- - - - - - - - -

Descripción:	Number of range reversals (eg: `100-200,50-70`) allowed before returning the complete - resource
Sintaxis:	`MaxRangeReversals default \| unlimited \| none \| number-of-ranges`
Valor por defecto:	`MaxRangeReversals 20`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache HTTP Server 2.3.15 and later

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

MaxRanges Directiva

- - - - - - - - -

Descripción:	Number of ranges allowed before returning the complete -resource
Sintaxis:	`MaxRanges default \| unlimited \| none \| number-of-ranges`
Valor por defecto:	`MaxRanges 200`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache HTTP Server 2.3.15 and later

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

MergeTrailers Directiva

- - - - - - - - -

Descripción:	Determines whether trailers are merged into headers
Sintaxis:	`MergeTrailers [on\|off]`
Valor por defecto:	`MergeTrailers off`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	2.4.11 and later

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

Mutex Directiva

- - - - - - - - -

Descripción:	Configures mutex mechanism and lock file directory for all -or specified mutexes
Sintaxis:	`Mutex mechanism [default\|mutex-name] ... [OmitPID]`
Valor por defecto:	`Mutex default`
Contexto:	server config
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache HTTP Server 2.3.4 and later

The Mutex directive sets the mechanism, - and optionally the lock file location, that httpd and modules use - to serialize access to resources. Specify default as - the first argument to change the settings for all mutexes; specify - a mutex name (see table below) as the first argument to override - defaults only for that mutex.

- -

The Mutex directive is typically used in - the following exceptional situations:

- -

change the mutex mechanism when the default mechanism selected - by APR has a functional or performance - problem
change the directory used by file-based mutexes when the - default directory does not support locking

- -

Supported modules

This directive only configures mutexes which have been registered - with the core server using the ap_mutex_register() API. - All modules bundled with httpd support the Mutex - directive, but third-party modules may not. Consult the documentation - of the third-party module, which must indicate the mutex name(s) which - can be configured if this directive is supported.

- -

The following mutex mechanisms are available:

default | yes -
This selects the default locking implementation, as determined by - APR. The default locking implementation can - be displayed by running httpd with the - -V option.
none | no -
This effectively disables the mutex, and is only allowed for a - mutex if the module indicates that it is a valid choice. Consult the - module documentation for more information.
posixsem -
This is a mutex variant based on a Posix semaphore.
- -
Warning
-
The semaphore ownership is not recovered if a thread in the process - holding the mutex segfaults, resulting in a hang of the web server.
-
-
sysvsem -
This is a mutex variant based on a SystemV IPC semaphore.
- -
Warning
-
It is possible to "leak" SysV semaphores if processes crash - before the semaphore is removed.
-
- -
Security
-
The semaphore API allows for a denial of service attack by any - CGIs running under the same uid as the webserver (i.e., - all CGIs, unless you use something like suexec - or cgiwrapper).
-
-
sem -
This selects the "best" available semaphore implementation, choosing - between Posix and SystemV IPC semaphores, in that order.
pthread -
This is a mutex variant based on cross-process Posix thread - mutexes.
- -
Warning
-
On most systems, if a child process terminates abnormally while - holding a mutex that uses this implementation, the server will deadlock - and stop responding to requests. When this occurs, the server will - require a manual restart to recover.
-
Solaris is a notable exception as it provides a mechanism which - usually allows the mutex to be recovered after a child process - terminates abnormally while holding a mutex.
-
If your system implements the - pthread_mutexattr_setrobust_np() function, you may be able - to use the pthread option safely.
-
-
fcntl:/path/to/mutex -
This is a mutex variant where a physical (lock-)file and the - fcntl() function are used as the mutex.
- -
Warning
-
When multiple mutexes based on this mechanism are used within - multi-threaded, multi-process environments, deadlock errors (EDEADLK) - can be reported for valid mutex operations if fcntl() - is not thread-aware, such as on Solaris.
-
-
flock:/path/to/mutex -
This is similar to the fcntl:/path/to/mutex method - with the exception that the flock() function is used to - provide file locking.
file:/path/to/mutex -
This selects the "best" available file locking implementation, - choosing between fcntl and flock, in that - order.

- -

Most mechanisms are only available on selected platforms, where the - underlying platform and APR support it. Mechanisms - which aren't available on all platforms are posixsem, - sysvsem, sem, pthread, fcntl, - flock, and file.

- -

With the file-based mechanisms fcntl and flock, - the path, if provided, is a directory where the lock file will be created. - The default directory is httpd's run-time file directory relative to - ServerRoot. Always use a local disk - filesystem for /path/to/mutex and never a directory residing - on a NFS- or AFS-filesystem. The basename of the file will be the mutex - type, an optional instance string provided by the module, and unless the - OmitPID keyword is specified, the process id of the httpd - parent process will be appended to to make the file name unique, avoiding - conflicts when multiple httpd instances share a lock file directory. For - example, if the mutex name is mpm-accept and the lock file - directory is /var/httpd/locks, the lock file name for the - httpd instance with parent process id 12345 would be - /var/httpd/locks/mpm-accept.12345.

- -

Security

It is best to avoid putting mutex files in a world-writable - directory such as /var/tmp because someone could create - a denial of service attack and prevent the server from starting by - creating a lockfile with the same name as the one the server will try - to create.

- -

The following table documents the names of mutexes used by httpd - and bundled modules.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Mutex name	Module(s)	Protected resource
`mpm-accept`	`prefork` and `worker` MPMs	incoming connections, to avoid the thundering herd problem; - for more information, refer to the - performance tuning - documentation
`authdigest-client`	`mod_auth_digest`	client list in shared memory
`authdigest-opaque`	`mod_auth_digest`	counter in shared memory
`ldap-cache`	`mod_ldap`	LDAP result cache
`rewrite-map`	`mod_rewrite`	communication with external mapping programs, to avoid - intermixed I/O from multiple requests
`ssl-cache`	`mod_ssl`	SSL session cache
`ssl-stapling`	`mod_ssl`	OCSP stapling response cache
`watchdog-callback`	`mod_watchdog`	callback function of a particular client module

- -

The OmitPID keyword suppresses the addition of the httpd - parent process id from the lock file name.

- -

In the following example, the mutex mechanism for the MPM accept - mutex will be changed from the compiled-in default to fcntl, - with the associated lock file created in directory - /var/httpd/locks. The mutex mechanism for all other mutexes - will be changed from the compiled-in default to sysvsem.

- -

- Mutex default sysvsem - Mutex mpm-accept fcntl:/var/httpd/locks -

- -

NameVirtualHost Directiva

- - - - - - -

Descripción:	Designates an IP address for name-virtual -hosting
Sintaxis:	`NameVirtualHost addr[:port]`
Contexto:	server config
Estado:	Core
Módulo:	core

- -

A single NameVirtualHost directive -identifies a set of identical virtual hosts on which the server will -further select from on the basis of the hostname -requested by the client. The NameVirtualHost -directive is a required directive if you want to configure -name-based virtual hosts.

- -

This directive, and the corresponding VirtualHost, -must be qualified with a port number if the server supports both HTTP -and HTTPS connections.

- -

Although addr can be a hostname, it is recommended -that you always use an IP address or a wildcard. A wildcard -NameVirtualHost matches only virtualhosts that also have a literal wildcard -as their argument.

- -

In cases where a firewall or other proxy receives the requests and -forwards them on a different IP address to the server, you must specify the -IP address of the physical interface on the machine which will be -servicing the requests.

- -

In the example below, requests received on interface 192.0.2.1 and port 80 -will only select among the first two virtual hosts. Requests received on -port 80 on any other interface will only select among the third and fourth -virtual hosts. In the common case where the interface isn't important -to the mapping, only the "*:80" NameVirtualHost and VirtualHost directives -are necessary.

- -

- NameVirtualHost 192.0.2.1:80 - NameVirtualHost *:80 - - <VirtualHost 192.0.2.1:80> - ServerName namebased-a.example.com - </VirtualHost> - - <VirtualHost 192.0.2.1:80> - Servername namebased-b.example.com - </VirtualHost> - - <VirtualHost *:80> - ServerName namebased-c.example.com - </VirtualHost> - - <VirtualHost *:80> - ServerName namebased-d.example.com - </VirtualHost> - - -

- -

If no matching virtual host is found, then the first listed - virtual host that matches the IP address and port will be used.

- - -

IPv6 addresses must be enclosed in square brackets, as shown - in the following example:

- -

- NameVirtualHost [2001:db8::a00:20ff:fea7:ccea]:8080 -

- -

Argument to `<VirtualHost>` - directive

Note that the argument to the <VirtualHost> directive must - exactly match the argument to the NameVirtualHost directive.

- -

- NameVirtualHost 192.0.2.2:80 - <VirtualHost 192.0.2.2:80> - # ... - </VirtualHost> -

- -

Consulte también

Virtual Hosts -documentation

Options Directiva

- - - - - - - - -

Descripción:	Configures what features are available in a particular -directory
Sintaxis:	`Options - [+\|-]option [[+\|-]option] ...`
Valor por defecto:	`Options All`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	Options
Estado:	Core
Módulo:	core

The Options directive controls which - server features are available in a particular directory.

- -

option can be set to None, in which - case none of the extra features are enabled, or one or more of - the following:

- -

All: All options except for MultiViews. This is the default - setting.
ExecCGI: - Execution of CGI scripts using mod_cgi - is permitted.
FollowSymLinks: - - The server will follow symbolic links in this directory. -
-
Even though the server follows the symlink it does not - change the pathname used to match against <Directory> sections.
-
Note also, that this option gets ignored if set - inside a <Location> - section.
-
Omitting this option should not be considered a security restriction, - since symlink testing is subject to race conditions that make it - circumventable.
-
Includes: - Server-side includes provided by mod_include - are permitted.
IncludesNOEXEC: - - Server-side includes are permitted, but the #exec - cmd and #exec cgi are disabled. It is still - possible to #include virtual CGI scripts from - ScriptAliased - directories.
Indexes: - If a URL which maps to a directory is requested, and there - is no DirectoryIndex - (e.g., index.html) in that directory, then - mod_autoindex will return a formatted listing - of the directory.
MultiViews: - Content negotiated - "MultiViews" are allowed using - mod_negotiation. -
Note

This option gets ignored if set - anywhere other than <Directory>, as mod_negotiation - needs real resources to compare against and evaluate from.
-
SymLinksIfOwnerMatch: The server will only follow symbolic links for which the - target file or directory is owned by the same user id as the - link. - -
Note

This option gets ignored if - set inside a <Location> section.
-
This option should not be considered a security restriction, - since symlink testing is subject to race conditions that make it - circumventable.
-

- -

Normally, if multiple Options could - apply to a directory, then the most specific one is used and - others are ignored; the options are not merged. (See how sections are merged.) - However if all the options on the - Options directive are preceded by a - + or - symbol, the options are - merged. Any options preceded by a + are added to the - options currently in force, and any options preceded by a - - are removed from the options currently in - force.

- -

Warning

Mixing Options with a + or - - with those without is not valid syntax, and is likely - to cause unexpected results.

- -

For example, without any + and - symbols:

- -

- <Directory /web/docs> - - Options Indexes FollowSymLinks - - </Directory> - - <Directory /web/docs/spec> - - Options Includes - - </Directory> -

- -

then only Includes will be set for the - /web/docs/spec directory. However if the second - Options directive uses the + and - - symbols:

- -

- <Directory /web/docs> - - Options Indexes FollowSymLinks - - </Directory> - - <Directory /web/docs/spec> - - Options +Includes -Indexes - - </Directory> -

- -

then the options FollowSymLinks and - Includes are set for the /web/docs/spec - directory.

- -

Note

Using -IncludesNOEXEC or - -Includes disables server-side includes completely - regardless of the previous setting.

- -

The default in the absence of any other settings is - All.

- -

Protocol Directiva

- - - - - - - -

Descripción:	Protocol for a listening socket
Sintaxis:	`Protocol protocol`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache 2.1.5 and later. -On Windows from Apache 2.3.3 and later.

This directive specifies the protocol used for a specific listening socket. - The protocol is used to determine which module should handle a request, and - to apply protocol specific optimizations with the AcceptFilter - directive.

- -

You only need to set the protocol if you are running on non-standard ports, otherwise http is assumed for port 80 and https for port 443.

- -

For example, if you are running https on a non-standard port, specify the protocol explicitly:

- -

- Protocol https -

- -

You can also specify the protocol using the Listen directive.

- -

Consulte también

AcceptFilter
Listen

Protocols Directiva

- - - - - - - - -

Descripción:	Protocols available for a server/virtual host
Sintaxis:	`Protocols protocol ...`
Valor por defecto:	`Protocols http/1.1`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Only available from Apache 2.4.17 and later.

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

Consulte también

ProtocolsHonorOrder

ProtocolsHonorOrder Directiva

- - - - - - - - -

Descripción:	Determines if order of Protocols determines precedence during negotiation
Sintaxis:	`ProtocolsHonorOrder On\|Off`
Valor por defecto:	`ProtocolsHonorOrder On`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Only available from Apache 2.4.17 and later.

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

Consulte también

Protocols

QualifyRedirectURL Directiva

- - - - - - - - - -

Descripción:	Controls whether the REDIRECT_URL environment variable is - fully qualified
Sintaxis:	`QualifyRedirectURL ON\|OFF`
Valor por defecto:	`QualifyRedirectURL OFF`
Contexto:	server config, virtual host, directory
Anula:	FileInfo
Estado:	Core
Módulo:	core
Compatibilidad:	Directive supported in 2.4.18 and later. 2.4.17 acted -as if 'QualifyRedirectURL ON' was configured.

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

RegisterHttpMethod Directiva

- - - - - - -

Descripción:	Register non-standard HTTP methods
Sintaxis:	`RegisterHttpMethod method [method [...]]`
Contexto:	server config
Estado:	Core
Módulo:	core

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

RLimitCPU Directiva

- - - - - - - - -

Descripción:	Limits the CPU consumption of processes launched -by Apache httpd children
Sintaxis:	`RLimitCPU seconds\|max [seconds\|max]`
Valor por defecto:	`Unset; uses operating system defaults`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

Takes 1 or 2 parameters. The first parameter sets the soft - resource limit for all processes and the second parameter sets - the maximum resource limit. Either parameter can be a number, - or max to indicate to the server that the limit should - be set to the maximum allowed by the operating system - configuration. Raising the maximum resource limit requires that - the server is running as root, or in the initial startup - phase.

- -

This applies to processes forked off from Apache httpd children - servicing requests, not the Apache httpd children themselves. This - includes CGI scripts and SSI exec commands, but not any - processes forked off from the Apache httpd parent such as piped - logs.

- -

CPU resource limits are expressed in seconds per - process.

- -

Consulte también

RLimitMEM
RLimitNPROC

RLimitMEM Directiva

- - - - - - - - -

Descripción:	Limits the memory consumption of processes launched -by Apache httpd children
Sintaxis:	`RLimitMEM bytes\|max [bytes\|max]`
Valor por defecto:	`Unset; uses operating system defaults`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

- -

Memory resource limits are expressed in bytes per - process.

- -

Consulte también

RLimitCPU
RLimitNPROC

RLimitNPROC Directiva

- - - - - - - - -

Descripción:	Limits the number of processes that can be launched by -processes launched by Apache httpd children
Sintaxis:	`RLimitNPROC number\|max [number\|max]`
Valor por defecto:	`Unset; uses operating system defaults`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

Takes 1 or 2 parameters. The first parameter sets the soft - resource limit for all processes and the second parameter sets - the maximum resource limit. Either parameter can be a number, - or max to indicate to the server that the limit - should be set to the maximum allowed by the operating system - configuration. Raising the maximum resource limit requires that - the server is running as root, or in the initial startup - phase.

- -

Process limits control the number of processes per user.

- -

Note

If CGI processes are not running - under user ids other than the web server user id, this directive - will limit the number of processes that the server itself can - create. Evidence of this situation will be indicated by - cannot fork messages in the - error_log.

- -

Consulte también

RLimitMEM
RLimitCPU

ScriptInterpreterSource Directiva

- - - - - - - - - -

Descripción:	Technique for locating the interpreter for CGI -scripts
Sintaxis:	`ScriptInterpreterSource Registry\|Registry-Strict\|Script`
Valor por defecto:	`ScriptInterpreterSource Script`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core
Compatibilidad:	Win32 only; -option `Registry-Strict` is available in Apache HTTP Server 2.0 and -later

This directive is used to control how Apache httpd finds the - interpreter used to run CGI scripts. The default setting is - Script. This causes Apache httpd to use the interpreter pointed to - by the shebang line (first line, starting with #!) in the - script. On Win32 systems this line usually looks like:

- -

- #!C:/Perl/bin/perl.exe -

- -

or, if perl is in the PATH, simply:

- -

- #!perl -

- -

Setting ScriptInterpreterSource Registry will - cause the Windows Registry tree HKEY_CLASSES_ROOT to be - searched using the script file extension (e.g., .pl) as a - search key. The command defined by the registry subkey - Shell\ExecCGI\Command or, if it does not exist, by the subkey - Shell\Open\Command is used to open the script file. If the - registry keys cannot be found, Apache httpd falls back to the behavior of the - Script option.

- -

Security

Be careful when using ScriptInterpreterSource - Registry with ScriptAlias'ed directories, because - Apache httpd will try to execute every file within this - directory. The Registry setting may cause undesired - program calls on files which are typically not executed. For - example, the default open command on .htm files on - most Windows systems will execute Microsoft Internet Explorer, so - any HTTP request for an .htm file existing within the - script directory would start the browser in the background on the - server. This is a good way to crash your system within a minute or - so.

- -

The option Registry-Strict which is new in Apache HTTP Server - 2.0 does the same thing as Registry but uses only the - subkey Shell\ExecCGI\Command. The - ExecCGI key is not a common one. It must be - configured manually in the windows registry and hence prevents - accidental program calls on your system.

- -

SeeRequestTail Directiva

- - - - - - - - -

Descripción:	Determine if mod_status displays the first 63 characters -of a request or the last 63, assuming the request itself is greater than -63 chars.
Sintaxis:	`SeeRequestTail On\|Off`
Valor por defecto:	`SeeRequestTail Off`
Contexto:	server config
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache httpd 2.2.7 and later.

mod_status with ExtendedStatus On - displays the actual request being handled. - For historical purposes, only 63 characters of the request - are actually stored for display purposes. This directive - controls whether the 1st 63 characters are stored (the previous - behavior and the default) or if the last 63 characters are. This - is only applicable, of course, if the length of the request is - 64 characters or greater.

- -

If Apache httpd is handling GET /disk1/storage/apache/htdocs/images/imagestore1/food/apples.jpg HTTP/1.1 mod_status displays as follows: -

- - - - - - - - - - -

Off (default)	GET /disk1/storage/apache/htdocs/images/imagestore1/food/apples
On	orage/apache/htdocs/images/imagestore1/food/apples.jpg HTTP/1.1

- - -

ServerAdmin Directiva

- - - - - - -

Descripción:	Email address that the server includes in error -messages sent to the client
Sintaxis:	`ServerAdmin email-address\|URL`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

The ServerAdmin sets the contact address - that the server includes in any error messages it returns to the - client. If the httpd doesn't recognize the supplied argument - as an URL, it - assumes, that it's an email-address and prepends it with - mailto: in hyperlink targets. However, it's recommended to - actually use an email address, since there are a lot of CGI scripts that - make that assumption. If you want to use an URL, it should point to another - server under your control. Otherwise users may not be able to contact you in - case of errors.

- -

It may be worth setting up a dedicated address for this, e.g.

- -

- ServerAdmin www-admin@foo.example.com -

as users do not always mention that they are talking about the - server!

- -

ServerAlias Directiva

- - - - - - -

Descripción:	Alternate names for a host used when matching requests -to name-virtual hosts
Sintaxis:	`ServerAlias hostname [hostname] ...`
Contexto:	virtual host
Estado:	Core
Módulo:	core

The ServerAlias directive sets the - alternate names for a host, for use with name-based virtual hosts. The - ServerAlias may include wildcards, if appropriate.

- -

- <VirtualHost *:80> - ServerName server.domain.com - ServerAlias server server2.domain.com server2 - ServerAlias *.example.com - UseCanonicalName Off - # ... - </VirtualHost> -

- -

Consulte también

ServerName Directiva

- - - - - - -

Descripción:	Hostname and port that the server uses to identify -itself
Sintaxis:	`ServerName [scheme://]fully-qualified-domain-name[:port]`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

The ServerName directive sets the - request scheme, hostname and - port that the server uses to identify itself. This is used when - creating redirection URLs.

- -

Additionally, ServerName is used (possibly - in conjunction with ServerAlias) to uniquely - identify a virtual host, when using name-based virtual hosts.

- -

For example, if the name of the - machine hosting the web server is simple.example.com, - but the machine also has the DNS alias www.example.com - and you wish the web server to be so identified, the following - directive should be used:

- -

- ServerName www.example.com:80 -

- -

The ServerName directive - may appear anywhere within the definition of a server. However, - each appearance overrides the previous appearance (within that - server).

- -

If no ServerName is specified, then the - server attempts to deduce the hostname by performing a reverse - lookup on the IP address. If no port is specified in the - ServerName, then the server will use the - port from the incoming request. For optimal reliability and - predictability, you should specify an explicit hostname and port - using the ServerName directive.

- -

If you are using name-based virtual hosts, - the ServerName inside a - <VirtualHost> - section specifies what hostname must appear in the request's - Host: header to match this virtual host.

- -

Sometimes, the server runs behind a device that processes SSL, - such as a reverse proxy, load balancer or SSL offload - appliance. When this is the case, specify the - https:// scheme and the port number to which the - clients connect in the ServerName directive - to make sure that the server generates the correct - self-referential URLs. -

- -

See the description of the - UseCanonicalName and - UseCanonicalPhysicalPort directives for - settings which determine whether self-referential URLs (e.g., by the - mod_dir module) will refer to the - specified port, or to the port number given in the client's request. -

- -

Failure to set ServerName to a name that - your server can resolve to an IP address will result in a startup - warning. httpd will then use whatever hostname it can - determine, using the system's hostname command. This - will almost never be the hostname you actually want.

- httpd: Could not reliably determine the server's fully qualified domain name, using rocinante.local for ServerName -

- - -

Consulte también

ServerPath Directiva

- - - - - - -

Descripción:	Legacy URL pathname for a name-based virtual host that -is accessed by an incompatible browser
Sintaxis:	`ServerPath URL-path`
Contexto:	virtual host
Estado:	Core
Módulo:	core

The ServerPath directive sets the legacy - URL pathname for a host, for use with name-based virtual hosts.

- -

Consulte también

Apache HTTP Server Virtual Host documentation

ServerRoot Directiva

- - - - - - - -

Descripción:	Base directory for the server installation
Sintaxis:	`ServerRoot directory-path`
Valor por defecto:	`ServerRoot /usr/local/apache`
Contexto:	server config
Estado:	Core
Módulo:	core

The ServerRoot directive sets the - directory in which the server lives. Typically it will contain the - subdirectories conf/ and logs/. Relative - paths in other configuration directives (such as Include or LoadModule, for example) are taken as - relative to this directory.

- -

Example

- ServerRoot /home/httpd -

- - -

Consulte también

the -d - option to httpd
the - security tips for information on how to properly set - permissions on the ServerRoot

ServerSignature Directiva

- - - - - - - - -

Descripción:	Configures the footer on server-generated documents
Sintaxis:	`ServerSignature On\|Off\|EMail`
Valor por defecto:	`ServerSignature Off`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

The ServerSignature directive allows the - configuration of a trailing footer line under server-generated - documents (error messages, mod_proxy ftp directory - listings, mod_info output, ...). The reason why you - would want to enable such a footer line is that in a chain of proxies, - the user often has no possibility to tell which of the chained servers - actually produced a returned error message.

- -

The Off - setting, which is the default, suppresses the footer line (and is - therefore compatible with the behavior of Apache-1.2 and - below). The On setting simply adds a line with the - server version number and ServerName of the serving virtual host, - and the EMail setting additionally creates a - "mailto:" reference to the ServerAdmin of the referenced - document.

- -

After version 2.0.44, the details of the server version number - presented are controlled by the ServerTokens directive.

- -

Consulte también

ServerTokens

ServerTokens Directiva

- - - - - - - -

Descripción:	Configures the `Server` HTTP response -header
Sintaxis:	`ServerTokens Major\|Minor\|Min[imal]\|Prod[uctOnly]\|OS\|Full`
Valor por defecto:	`ServerTokens Full`
Contexto:	server config
Estado:	Core
Módulo:	core

This directive controls whether Server response - header field which is sent back to clients includes a - description of the generic OS-type of the server as well as - information about compiled-in modules.

- -

ServerTokens Full (or not specified): Server sends (e.g.): Server: Apache/2.4.1 - (Unix) PHP/4.2.2 MyMod/1.2
ServerTokens Prod[uctOnly]: Server sends (e.g.): Server: - Apache
ServerTokens Major: Server sends (e.g.): Server: - Apache/2
ServerTokens Minor: Server sends (e.g.): Server: - Apache/2.4
ServerTokens Min[imal]: Server sends (e.g.): Server: - Apache/2.4.1
ServerTokens OS: Server sends (e.g.): Server: Apache/2.4.1 - (Unix)

- -

This setting applies to the entire server, and cannot be - enabled or disabled on a virtualhost-by-virtualhost basis.

- -

After version 2.0.44, this directive also controls the - information presented by the ServerSignature directive.

- -

Setting ServerTokens to less than - minimal is not recommended because it makes it more - difficult to debug interoperational problems. Also note that - disabling the Server: header does nothing at all to make your - server more secure; the idea of "security through obscurity" - is a myth and leads to a false sense of safety.

- - -

Consulte también

ServerSignature

SetHandler Directiva

- - - - - - - - -

Descripción:	Forces all matching files to be processed by a -handler
Sintaxis:	`SetHandler handler-name\|None`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core
Compatibilidad:	Moved into the core in Apache httpd 2.0

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 - handler-name. 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 httpd.conf:

- -

- <Location /status> - - SetHandler server-status - - </Location> -

- -

You can override an earlier defined SetHandler - directive by using the value None.

Note: because SetHandler overrides default handlers, - normal behaviour such as handling of URLs ending in a slash (/) as - directories or index files is suppressed.

- -

Consulte también

AddHandler

SetInputFilter Directiva

- - - - - - - -

Descripción:	Sets the filters that will process client requests and POST -input
Sintaxis:	`SetInputFilter filter[;filter...]`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core

The SetInputFilter directive sets the - filter or filters which will process client requests and POST - input when they are received by the server. This is in addition to - any filters defined elsewhere, including the - AddInputFilter - directive.

- -

If more than one filter is specified, they must be separated - by semicolons in the order in which they should process the - content.

- -

Consulte también

Filters documentation

SetOutputFilter Directiva

- - - - - - - -

Descripción:	Sets the filters that will process responses from the -server
Sintaxis:	`SetOutputFilter filter[;filter...]`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core

The SetOutputFilter directive sets the filters - which will process responses from the server before they are - sent to the client. This is in addition to any filters defined - elsewhere, including the - AddOutputFilter - directive.

- -

For example, the following configuration will process all files - in the /www/data/ directory for server-side - includes.

- -

- <Directory /www/data/> - - SetOutputFilter INCLUDES - - </Directory> -

- -

If more than one filter is specified, they must be separated - by semicolons in the order in which they should process the - content.

- -

Consulte también

Filters documentation

TimeOut Directiva

- - - - - - - -

Descripción:	Amount of time the server will wait for -certain events before failing a request
Sintaxis:	`TimeOut seconds`
Valor por defecto:	`TimeOut 60`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

The TimeOut directive defines the length - of time Apache httpd will wait for I/O in various circumstances:

- -

When reading data from the client, the length of time to - wait for a TCP packet to arrive if the read buffer is - empty.
When writing data to the client, the length of time to wait - for an acknowledgement of a packet if the send buffer is - full.
In mod_cgi, the length of time to wait for - output from a CGI script.
In mod_ext_filter, the length of time to - wait for output from a filtering process.
In mod_proxy, the default timeout value if - ProxyTimeout is not - configured.

- - -

TraceEnable Directiva

- - - - - - - - -

Descripción:	Determines the behaviour on `TRACE` requests
Sintaxis:	`TraceEnable [on\|off\|extended]`
Valor por defecto:	`TraceEnable on`
Contexto:	server config
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache HTTP Server 1.3.34, 2.0.55 and later

This directive overrides the behavior of TRACE for both - the core server and mod_proxy. The default - TraceEnable on permits TRACE requests per - RFC 2616, which disallows any request body to accompany the request. - TraceEnable off causes the core server and - mod_proxy to return a 405 (Method not - allowed) error to the client.

- -

Finally, for testing and diagnostic purposes only, request - bodies may be allowed using the non-compliant TraceEnable - extended directive. The core (as an origin server) will - restrict the request body to 64k (plus 8k for chunk headers if - Transfer-Encoding: chunked is used). The core will - reflect the full headers and all chunk headers with the response - body. As a proxy server, the request body is not restricted to 64k.

- -

UnDefine Directiva

- - - - - - -

Descripción:	Undefine the existence of a variable
Sintaxis:	`UnDefine parameter-name`
Contexto:	server config
Estado:	Core
Módulo:	core

Undoes the effect of a Define or - of passing a -D argument to httpd.

This directive can be used to toggle the use of <IfDefine> sections without needing to alter - -D arguments in any startup scripts.

- -

UseCanonicalName Directiva

- - - - - - - -

Descripción:	Configures how the server determines its own name and -port
Sintaxis:	`UseCanonicalName On\|Off\|DNS`
Valor por defecto:	`UseCanonicalName Off`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core

In many situations Apache httpd must construct a self-referential - URL -- that is, a URL that refers back to the same server. With - UseCanonicalName On Apache httpd will use the hostname and port - specified in the ServerName - directive to construct the canonical name for the server. This name - is used in all self-referential URLs, and for the values of - SERVER_NAME and SERVER_PORT in CGIs.

- -

With UseCanonicalName Off Apache httpd will form - self-referential URLs using the hostname and port supplied by - the client if any are supplied (otherwise it will use the - canonical name, as defined above). These values are the same - that are used to implement name-based virtual hosts, - and are available with the same clients. The CGI variables - SERVER_NAME and SERVER_PORT will be - constructed from the client supplied values as well.

- -

An example where this may be useful is on an intranet server - where you have users connecting to the machine using short - names such as www. You'll notice that if the users - type a shortname, and a URL which is a directory, such as - http://www/splat, without the trailing - slash then Apache httpd will redirect them to - http://www.domain.com/splat/. If you have - authentication enabled, this will cause the user to have to - authenticate twice (once for www and once again - for www.domain.com -- see the - FAQ on this subject for more information). But if - UseCanonicalName is set Off, then - Apache httpd will redirect to http://www/splat/.

- -

There is a third option, UseCanonicalName DNS, - which is intended for use with mass IP-based virtual hosting to - support ancient clients that do not provide a - Host: header. With this option Apache httpd does a - reverse DNS lookup on the server IP address that the client - connected to in order to work out self-referential URLs.

- -

Warning

If CGIs make assumptions about the values of SERVER_NAME - they may be broken by this option. The client is essentially free - to give whatever value they want as a hostname. But if the CGI is - only using SERVER_NAME to construct self-referential URLs - then it should be just fine.

- -

Consulte también

UseCanonicalPhysicalPort
ServerName
Listen

UseCanonicalPhysicalPort Directiva

- - - - - - - -

Descripción:	Configures how the server determines its own name and -port
Sintaxis:	`UseCanonicalPhysicalPort On\|Off`
Valor por defecto:	`UseCanonicalPhysicalPort Off`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core

In many situations Apache httpd must construct a self-referential - URL -- that is, a URL that refers back to the same server. With - UseCanonicalPhysicalPort On Apache httpd will, when - constructing the canonical port for the server to honor - the UseCanonicalName directive, - provide the actual physical port number being used by this request - as a potential port. With UseCanonicalPhysicalPort Off - Apache httpd will not ever use the actual physical port number, instead - relying on all configured information to construct a valid port number.

- -

Note

The ordering of when the physical port is used is as follows:

- UseCanonicalName On

Port provided in Servername
Physical port
Default port

- UseCanonicalName Off | DNS -

Parsed port from Host: header
Physical port
Port provided in Servername
Default port

- -

With UseCanonicalPhysicalPort Off, the - physical ports are removed from the ordering.

- - -

Consulte también

UseCanonicalName
ServerName
Listen

<VirtualHost> Directiva

- - - - - - -

Descripción:	Contains directives that apply only to a specific -hostname or IP address
Sintaxis:	`<VirtualHost - addr[:port] [addr[:port]] - ...> ... </VirtualHost>`
Contexto:	server config
Estado:	Core
Módulo:	core

<VirtualHost> and - </VirtualHost> are used to enclose a group of - directives that will apply only to a particular virtual host. Any - directive that is allowed in a virtual host context may be - used. When the server receives a request for a document on a - particular virtual host, it uses the configuration directives - enclosed in the <VirtualHost> - section. Addr can be:

- -

The IP address of the virtual host;
A fully qualified domain name for the IP address of the - virtual host (not recommended);
The character *, which is used only in combination with - NameVirtualHost * to match all IP addresses; or
The string _default_, which is used only - with IP virtual hosting to catch unmatched IP addresses.

- -

Example

- <VirtualHost 10.1.2.3> - - ServerAdmin webmaster@host.example.com - DocumentRoot /www/docs/host.example.com - ServerName host.example.com - ErrorLog logs/host.example.com-error_log - TransferLog logs/host.example.com-access_log - - </VirtualHost> -

- - -

IPv6 addresses must be specified in square brackets because - the optional port number could not be determined otherwise. An - IPv6 example is shown below:

- -

- <VirtualHost [2001:db8::a00:20ff:fea7:ccea]> - - ServerAdmin webmaster@host.example.com - DocumentRoot /www/docs/host.example.com - ServerName host.example.com - ErrorLog logs/host.example.com-error_log - TransferLog logs/host.example.com-access_log - - </VirtualHost> -

- -

Each Virtual Host must correspond to a different IP address, - different port number or a different host name for the server, - in the former case the server machine must be configured to - accept IP packets for multiple addresses. (If the machine does - not have multiple network interfaces, then this can be - accomplished with the ifconfig alias command -- if - your OS supports it).

- -

Note

The use of <VirtualHost> does - not affect what addresses Apache httpd listens on. You - may need to ensure that Apache httpd is listening on the correct addresses - using Listen.

- -

When using IP-based virtual hosting, the special name - _default_ can be specified in - which case this virtual host will match any IP address that is - not explicitly listed in another virtual host. In the absence - of any _default_ virtual host the "main" server config, - consisting of all those definitions outside any VirtualHost - section, is used when no IP-match occurs.

- -

You can specify a :port to change the port that is - matched. If unspecified then it defaults to the same port as the - most recent Listen - statement of the main server. You may also specify :* - to match all ports on that address. (This is recommended when used - with _default_.)

- -

A ServerName should be - specified inside each <VirtualHost> block. If it is absent, the - ServerName from the "main" - server configuration will be inherited.

- -

If no matching virtual host is found, then the first listed - virtual host that matches the IP address will be used. As a - consequence, the first listed virtual host is the default virtual - host.

- -

Security

See the security tips - document for details on why your security could be compromised if the - directory where log files are stored is writable by anyone other - than the user that starts the server.

- -

Consulte también

Apache HTTP Server Virtual Host documentation
Issues Regarding DNS and - Apache HTTP Server
Setting - which addresses and ports Apache HTTP Server uses
How <Directory>, <Location> - and <Files> sections work for an explanation of how these - different sections are combined when a request is received

Warning Directiva

- - - - - - - -

Descripción:	Warn from configuration parsing with a custom message
Sintaxis:	`Warning message`
Contexto:	server config, virtual host, directory, .htaccess
Estado:	Core
Módulo:	core
Compatibilidad:	2.5 and later

The documentation for this directive has - not been translated yet. Please have a look at the English - version.

Idiomas disponibles: de | - en | - es | - fr | - ja | - tr

Comentarios

+ --> +core - Servidor HTTP Apache Versión 2.5 + + + + + + + + +

+Apache > Servidor HTTP > Documentación > Versión 2.5 > Módulos

Funcionalidad Básica de Apache

Idiomas disponibles: de | + en | + es | + fr | + ja | + tr

Esta traducción podría estar + obsoleta. Consulte la versión en inglés de la + documentación para comprobar si se han producido cambios + recientemente.

+ +

Descripción:	Funcionalides básicas del Servidor HTTP Apache que siempre están presentes.
Estado:	Core

Directivas

AcceptFilter
AcceptPathInfo
AccessFileName
AddDefaultCharset
AllowEncodedSlashes
AllowOverride
AllowOverrideList
AsyncFilter
CGIMapExtension
CGIPassAuth
CGIVar
ContentDigest
DefaultRuntimeDir
DefaultType
Define
<Directory>
<DirectoryMatch>
DocumentRoot
<Else>
<ElseIf>
EnableMMAP
EnableSendfile
Error
ErrorDocument
ErrorLog
ErrorLogFormat
ExtendedStatus
FileETag
<Files>
<FilesMatch>
ForceType
GprofDir
HostnameLookups
<If>
<IfDefine>
<IfModule>
Include
IncludeOptional
KeepAlive
KeepAliveTimeout
<Limit>
<LimitExcept>
LimitInternalRecursion
LimitRequestBody
LimitRequestFields
LimitRequestFieldSize
LimitRequestLine
LimitXMLRequestBody
<Location>
<LocationMatch>
LogLevel
LogLevelOverride
MaxKeepAliveRequests
MaxRangeOverlaps
MaxRangeReversals
MaxRanges
MergeTrailers
Mutex
NameVirtualHost
Options
Protocol
Protocols
ProtocolsHonorOrder
QualifyRedirectURL
RegisterHttpMethod
RLimitCPU
RLimitMEM
RLimitNPROC
ScriptInterpreterSource
SeeRequestTail
ServerAdmin
ServerAlias
ServerName
ServerPath
ServerRoot
ServerSignature
ServerTokens
SetHandler
SetInputFilter
SetOutputFilter
TimeOut
TraceEnable
UnDefine
UseCanonicalName
UseCanonicalPhysicalPort
<VirtualHost>
Warning

Bugfix checklist

Consulte también

Comentarios

+ +

AcceptFilter Directiva

+ + + + + + +

Descripción:	Configura mejoras para un Protocolo de Escucha de Sockets
Sintaxis:	`AcceptFilter protocol accept_filter`
Contexto:	server config
Estado:	Core
Módulo:	core

Esta directiva hace posible mejoras específicas a nivel de sistema operativo + y a través del tipo de Protocolo para un socket que escucha. + La premisa básica es que el kernel no envíe un socket al servidor + hasta que o bien los datos se hayan recibido o bien se haya almacenado + en el buffer una Respuesta HTTP completa. + Actualmente sólo están soportados + + Accept Filters sobre FreeBSD, TCP_DEFER_ACCEPT sobre Linux, + y AcceptEx() sobre Windows.

+ +

El uso de none para un argumento desactiva cualquier filtro + aceptado para ese protocolo. Esto es útil para protocolos que requieren que un + servidor envíe datos primeros, tales como ftp: o nntp:

AcceptFilter nntp none

+ + +

Los nombres de protocolo por defecto son https para el puerto 443 + y http para todos los demás puertos. Para especificar que se está + utilizando otro protocolo con un puerto a la escucha, añade el argumento protocol + a la directiva Listen.

+ +

Los valores por defecto de FreeBDS son:

AcceptFilter http httpready
+AcceptFilter https dataready

+ + +

El filtro httpready almacena en el buffer peticiones HTTP completas + a nivel de kernel. Una vez que la petición es recibida, el kernel la envía al servidor. + Consulta la página man de + + accf_http(9) para más detalles. Puesto que las peticiones HTTPS + están encriptadas, sólo se utiliza el filtro + accf_data(9).

+ +

Los valores por defecto en Linux son:

AcceptFilter http data
+AcceptFilter https data

+ + +

En Linux, TCP_DEFER_ACCEPT no soporta el buffering en peticiones http. + Cualquier valor además de none habilitará + TCP_DEFER_ACCEPT en ese socket. Para más detalles + ver la página man de Linux + + tcp(7).

+ +

Los valores por defecto en Windows son:

AcceptFilter http data
+AcceptFilter https data

+ + +

Sobre Windows mpm_winnt interpreta el argumento AcceptFilter para conmutar la API + AcceptEx(), y no soporta el buffering sobre el protocolo http. Hay dos valores + que utilizan la API Windows AcceptEx() y que recuperan sockets de red + entre conexiones. data espera hasta que los datos han sido + transmitidos como se comentaba anteriormente, y el buffer inicial de datos y las + direcciones de red son recuperadas a partir de una única llamada AcceptEx(). + connect utiliza la API AcceptEx() API, y recupera también + las direcciones de red, pero a diferencia de none + la opción connect no espera a la transmisión inicial de los datos.

+ +

Sobre Windows, none usa accept() antes que AcceptEx() + y no recuperará sockets entre las conexiones. Lo que es útil para los adaptadores de + red con un soporte precario de drivers, así como para algunos proveedores de red + tales como drivers vpn, o filtros de spam, de virus o de spyware.

+ + +

Consulte también

Protocol

AcceptPathInfo Directiva

+ + + + + + + + +

Descripción:	Los recursos aceptan información sobre su ruta
Sintaxis:	`AcceptPathInfo On\|Off\|Default`
Valor por defecto:	`AcceptPathInfo Default`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core

+ +

Esta directiva controla si las peticiones que contienen información sobre la ruta + que sigue un fichero que existe (o un fichero que no existe pero en un directorio que + sí existe) serán aceptadas o denegadas. La información de ruta puede estar disponible + para los scripts en la variable de entorno PATH_INFO.

+ +

Por ejemplo, asumamos que la ubicación /test/ apunta a + un directorio que contiene únicamente el fichero + here.html. Entonces, las peticiones tanto para + /test/here.html/more como para + /test/nothere.html/more recogen + /more como PATH_INFO.

+ +

Los tres posibles argumentos para la directiva + AcceptPathInfo son los siguientes:

Off: Una petición sólo será aceptada si + se corresponde con una ruta literal que existe. Por lo tanto, una petición + con una información de ruta después del nombre de fichero tal como + /test/here.html/more en el ejemplo anterior devolverá + un error 404 NOT FOUND.
On: Una petición será aceptada si una + ruta principal de acceso se corresponde con un fichero que existe. El ejemplo + anterior /test/here.html/more será aceptado si + /test/here.html corresponde a un fichero válido.
Default: La gestión de las peticiones + con información de ruta está determinada por el controlador responsable de la petición. + El controlador principal para para ficheros normales rechaza por defecto + peticiones PATH_INFO. Los controladores que sirven scripts, tales como cgi-script e isapi-handler, normalmente aceptan + PATH_INFO por defecto.

+ +

El objetivo principal de la directiva AcceptPathInfo + es permitirnos sobrescribir la opción del controlador + de aceptar o rechazar PATH_INFO. Este tipo de reescritura se necesita, + por ejemplo, cuando utilizas un filtro, tal como + INCLUDES, para generar contenido + basado en PATH_INFO. El controlador principal normalmente rechazaría + la petición, de modo que puedes utilizar la siguiente configuración para habilitarla + como script:

+ +

<Files "mypaths.shtml">
+  Options +Includes
+  SetOutputFilter INCLUDES
+  AcceptPathInfo On
+</Files>

+ + + +

AccessFileName Directiva

+ + + + + + + +

Descripción:	Nombre del fichero distribuido de configuración
Sintaxis:	`AccessFileName filename [filename] ...`
Valor por defecto:	`AccessFileName .htaccess`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

Mientras que procesa una petición el servidor busca + el primer fichero de configuración existente dentro de un listado de nombres en + cada directorio de la ruta del documento, si los ficheros distribuidos + de configuración están habilitados para ese + directorio. Por ejemplo:

+ +

AccessFileName .acl

+ + +

Antes de servir el documento + /usr/local/web/index.html, el servidor leerá + /.acl, /usr/.acl, + /usr/local/.acl y /usr/local/web/.acl + para las directivas, salvo que estén deshabilitadas con:

+ +

<Directory "/">
+    AllowOverride None
+</Directory>

+ + + + +

Consulte también

AddDefaultCharset Directiva

+ + + + + + + + +

Descripción:	Juego de casrácteres que se le añade por defecto a una respuesta del tipo + contenido "content-type" es `text/plain` o `text/html`
Sintaxis:	`AddDefaultCharset On\|Off\|charset`
Valor por defecto:	`AddDefaultCharset Off`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core

Esta directiva especifica un valor por defecto para el tipo de soporte que + se usa como parámetro del juego de carácteres (el nombre de una + codificación de carácteres) para ser añadido a una respuesta si y solo si + el contenido de "content-type" es o text/plain o + text/html. Esto debería sobreescribir cualquier juego de + caracteres que se le especifique en el cuerpo de la respuesta mediante un + elemento META, aunque el comportamiento exacto depende a menudo + de la confuguracion del usuario cliente. Una configuración de + AddDefaultCharset Off deshabilita esta funcionalidad. + AddDefaultCharset On habilita un conjunto de caracteres por defecto + de iso-8859-1. Cualquier otro valor se asume que sea el charset + que va a ser usado, que debe ser uno de los juegos de carácteres + registradas por el IANA + para su uso en los tipos de medios de Internet (MIME types). + Por ejemplo:

+ +

AddDefaultCharset utf-8

+ + +

AddDefaultCharset debería ser utilizada sólo cuando + se sepa que todo el texto del recurso al que se le aplica se sabe que va a + estar en ese juego de caracteres y es inconveniente etiquetar los + documentos individualmente. Un ejemplo de ello es añadir el juego de caracteres + a recursos con contenido autogenerado, tales como scripts legados de CGI, + que pueden ser vulnerables a ataques de tipo XSS (Cross-Site Scripting), + debido a datos que incluye el usuario en la salida. Notese, sin embargo + una mejor solución es arreglar (o eliminar) dichos scripts, ya que + dejar por defecto un juego de carácteres no protege a los usuarios + que han habilitado la funcionalidad "auto-detect character encoding" en sus + navegadores. +

+ +

Consulte también

AddCharset

AllowEncodedSlashes Directiva

+ + + + + + + + +

Descripción:	Determina si Determines whether encoded path separators in URLs are allowed to +be passed through
Sintaxis:	`AllowEncodedSlashes On\|Off`
Valor por defecto:	`AllowEncodedSlashes Off`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache httpd 2.0.46 and later

The AllowEncodedSlashes directive allows URLs + which contain encoded path separators (%2F for / + and additionally %5C for \ on according systems) + to be used. Normally such URLs are refused with a 404 (Not found) error.

+ +

Turning AllowEncodedSlashes On is + mostly useful when used in conjunction with PATH_INFO.

+ +

Note

Allowing encoded slashes does not imply decoding. + Occurrences of %2F or %5C (only on + according systems) will be left as such in the otherwise decoded URL + string.

+ +

Consulte también

AcceptPathInfo

AllowOverride Directiva

+ + + + + + + +

Descripción:	Types of directives that are allowed in +`.htaccess` files
Sintaxis:	`AllowOverride All\|None\|directive-type +[directive-type] ...`
Valor por defecto:	`AllowOverride None (2.3.9 and later), AllowOverride All (2.3.8 and earlier)`
Contexto:	directory
Estado:	Core
Módulo:	core

When the server finds an .htaccess file (as + specified by AccessFileName) + it needs to know which directives declared in that file can override + earlier configuration directives.

+ +

Only available in <Directory> sections

+ AllowOverride is valid only in + <Directory> + sections specified without regular expressions, not in <Location>, <DirectoryMatch> or + <Files> sections. +

+ +

When this directive is set to None, then + .htaccess files are completely ignored. + In this case, the server will not even attempt to read + .htaccess files in the filesystem.

+ +

When this directive is set to All, then any + directive which has the .htaccess Context is allowed in + .htaccess files.

+ +

The directive-type can be one of the following + groupings of directives.

+ +

AuthConfig: + + Allow use of the authorization directives (AuthDBMGroupFile, + AuthDBMUserFile, + AuthGroupFile, + AuthName, + AuthType, AuthUserFile, Require, etc.).
FileInfo: + Allow use of the directives controlling document types + (ErrorDocument, + ForceType, + LanguagePriority, + SetHandler, + SetInputFilter, + SetOutputFilter, and + mod_mime Add* and Remove* directives), + document meta data (Header, RequestHeader, SetEnvIf, SetEnvIfNoCase, BrowserMatch, CookieExpires, CookieDomain, CookieStyle, CookieTracking, CookieName), + mod_rewrite directives RewriteEngine, RewriteOptions, RewriteBase, RewriteCond, RewriteRule) and + Action from + mod_actions. +
Indexes: + Allow use of the directives controlling directory indexing + (AddDescription, + AddIcon, AddIconByEncoding, + AddIconByType, + DefaultIcon, DirectoryIndex, FancyIndexing, HeaderName, IndexIgnore, IndexOptions, ReadmeName, + etc.).
Limit: + Allow use of the directives controlling host access (Allow, Deny and Order).
Options[=Option,...]: + Allow use of the directives controlling specific directory + features (Options and + XBitHack). + An equal sign may be given followed by a comma (but no spaces) + separated lists of options that may be set using the Options command.

+ +

Example:

+ +

+ AllowOverride AuthConfig Indexes +

+ +

In the example above all directives that are neither in the group + AuthConfig nor Indexes cause an internal + server error.

+ +

For security and performance reasons, do not set + AllowOverride to anything other than None + in your <Directory /> block. Instead, find (or + create) the <Directory> block that refers to the + directory where you're actually planning to place a + .htaccess file.

+ +

Consulte también

AllowOverrideList Directiva

+ + + + + + + +

Descripción:	Individual directives that are allowed in +`.htaccess` files
Sintaxis:	`AllowOverrideList None\|directive +[directive-type] ...`
Valor por defecto:	`AllowOverrideList None`
Contexto:	directory
Estado:	Core
Módulo:	core

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

Consulte también

AsyncFilter Directiva

+ + + + + + + + +

Descripción:	Set the minimum filter type eligible for asynchronous handling
Sintaxis:	`AsyncFilter request\|connection\|network`
Valor por defecto:	`AsyncFilter request`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Only available from Apache 2.5.0 and later.

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

CGIMapExtension Directiva

+ + + + + + + + +

Descripción:	Technique for locating the interpreter for CGI +scripts
Sintaxis:	`CGIMapExtension cgi-path .extension`
Contexto:	directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core
Compatibilidad:	NetWare only

This directive is used to control how Apache httpd finds the + interpreter used to run CGI scripts. For example, setting + CGIMapExtension sys:\foo.nlm .foo will + cause all CGI script files with a .foo extension to + be passed to the FOO interpreter.

+ +

CGIPassAuth Directiva

+ + + + + + + + + +

Descripción:	Enables passing HTTP authorization headers to scripts as CGI +variables
Sintaxis:	`CGIPassAuth On\|Off`
Valor por defecto:	`CGIPassAuth Off`
Contexto:	directory, .htaccess
Anula:	AuthConfig
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache HTTP Server 2.4.13 and later

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

CGIVar Directiva

+ + + + + + + + +

Descripción:	Controls how some CGI variables are set
Sintaxis:	`CGIVar variable rule`
Contexto:	directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache HTTP Server 2.4.21 and later

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

ContentDigest Directiva

+ + + + + + + + +

Descripción:	Enables the generation of `Content-MD5` HTTP Response +headers
Sintaxis:	`ContentDigest On\|Off`
Valor por defecto:	`ContentDigest Off`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	Options
Estado:	Core
Módulo:	core

This directive enables the generation of + Content-MD5 headers as defined in RFC1864 + respectively RFC2616.

+ +

MD5 is an algorithm for computing a "message digest" + (sometimes called "fingerprint") of arbitrary-length data, with + a high degree of confidence that any alterations in the data + will be reflected in alterations in the message digest.

+ +

The Content-MD5 header provides an end-to-end + message integrity check (MIC) of the entity-body. A proxy or + client may check this header for detecting accidental + modification of the entity-body in transit. Example header:

+ +

+ Content-MD5: AuLb7Dp1rqtRtxz2m9kRpA== +

+ +

Note that this can cause performance problems on your server + since the message digest is computed on every request (the + values are not cached).

+ +

Content-MD5 is only sent for documents served + by the core, and not by any module. For example, + SSI documents, output from CGI scripts, and byte range responses + do not have this header.

+ +

DefaultRuntimeDir Directiva

+ + + + + + + + +

Descripción:	Base directory for the server run-time files
Sintaxis:	`DefaultRuntimeDir directory-path`
Valor por defecto:	`DefaultRuntimeDir DEFAULT_REL_RUNTIMEDIR (logs/)`
Contexto:	server config
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache 2.4.2 and later

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

Consulte también

the + security tips for information on how to properly set + permissions on the ServerRoot

DefaultType Directiva

+ + + + + + + + + +

Descripción:	This directive has no effect other than to emit warnings +if the value is not `none`. In prior versions, DefaultType +would specify a default media type to assign to response content for +which no other media type configuration could be found. +
Sintaxis:	`DefaultType media-type\|none`
Valor por defecto:	`DefaultType none`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core
Compatibilidad:	The argument `none` is available in Apache httpd 2.2.7 and later. All other choices are DISABLED for 2.3.x and later.

This directive has been disabled. For backwards compatibility + of configuration files, it may be specified with the value + none, meaning no default media type. For example:

+ +

+ DefaultType None +

+ +

DefaultType None is only available in + httpd-2.2.7 and later.

+ +

Use the mime.types configuration file and the + AddType to configure media + type assignments via file extensions, or the + ForceType directive to configure + the media type for specific resources. Otherwise, the server will + send the response without a Content-Type header field and the + recipient may attempt to guess the media type.

+ +

Define Directiva

+ + + + + + +

Descripción:	Define the existence of a variable
Sintaxis:	`Define parameter-name`
Contexto:	server config
Estado:	Core
Módulo:	core

Equivalent to passing the -D argument to httpd.

This directive can be used to toggle the use of <IfDefine> sections without needing to alter + -D arguments in any startup scripts.

+ +

<Directory> Directiva

+ + + + + + +

Descripción:	Enclose a group of directives that apply only to the +named file-system directory, sub-directories, and their contents.
Sintaxis:	`<Directory directory-path> +... </Directory>`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

<Directory> and + </Directory> are used to enclose a group of + directives that will apply only to the named directory, + sub-directories of that directory, and the files within the respective + directories. Any directive that is allowed + in a directory context may be used. Directory-path is + either the full path to a directory, or a wild-card string using + Unix shell-style matching. In a wild-card string, ? matches + any single character, and * matches any sequences of + characters. You may also use [] character ranges. None + of the wildcards match a `/' character, so <Directory + /*/public_html> will not match + /home/user/public_html, but <Directory + /home/*/public_html> will match. Example:

+ +

+ <Directory /usr/local/httpd/htdocs> + + Options Indexes FollowSymLinks + + </Directory> +

+ +

Be careful with the directory-path arguments: + They have to literally match the filesystem path which Apache httpd uses + to access the files. Directives applied to a particular + <Directory> will not apply to files accessed from + that same directory via a different path, such as via different symbolic + links.

+ +

Regular + expressions can also be used, with the addition of the + ~ character. For example:

+ +

+ <Directory ~ "^/www/.*/[0-9]{3}"> +

+ +

would match directories in /www/ that consisted of + three numbers.

+ +

If multiple (non-regular expression) <Directory> sections + match the directory (or one of its parents) containing a document, + then the directives are applied in the order of shortest match + first, interspersed with the directives from the .htaccess files. For example, + with

+ +

+ <Directory /> + + AllowOverride None + + </Directory> + + <Directory /home/> + + AllowOverride FileInfo + + </Directory> +

+ +

for access to the document /home/web/dir/doc.html + the steps are:

+ +

Apply directive AllowOverride None + (disabling .htaccess files).
Apply directive AllowOverride FileInfo (for + directory /home).
Apply any FileInfo directives in + /home/.htaccess, /home/web/.htaccess and + /home/web/dir/.htaccess in that order.

+ +

Regular expressions are not considered until after all of the + normal sections have been applied. Then all of the regular + expressions are tested in the order they appeared in the + configuration file. For example, with

+ +

+ <Directory ~ abc$> + + # ... directives here ... + + </Directory> +

+ +

the regular expression section won't be considered until after + all normal <Directory>s and + .htaccess files have been applied. Then the regular + expression will match on /home/abc/public_html/abc and + the corresponding <Directory> will + be applied.

+ +

Note that the default access for + <Directory /> is Allow from All. + This means that Apache httpd will serve any file mapped from an URL. It is + recommended that you change this with a block such + as

+ +

+ <Directory /> + + Order Deny,Allow + Deny from All + + </Directory> +

+ +

and then override this for directories you + want accessible. See the Security Tips page for more + details.

+ +

The directory sections occur in the httpd.conf file. + <Directory> directives + cannot nest, and cannot appear in a <Limit> or <LimitExcept> section.

+ +

Consulte también

How <Directory>, + <Location> and <Files> sections work for an + explanation of how these different sections are combined when a + request is received

<DirectoryMatch> Directiva

+ + + + + + +

Descripción:	Enclose directives that apply to +the contents of file-system directories matching a regular expression.
Sintaxis:	`<DirectoryMatch regex> +... </DirectoryMatch>`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

<DirectoryMatch> and + </DirectoryMatch> are used to enclose a group + of directives which will apply only to the named directory (and the files within), + the same as <Directory>. + However, it takes as an argument a + regular expression. For example:

+ +

+ <DirectoryMatch "^/www/(.+/)?[0-9]{3}"> +

+ +

would match directories in /www/ that consisted of three + numbers.

+ +

Compatability

+ Prior to 2.3.9, this directive implicitly applied to sub-directories + (like <Directory>) and + could not match the end of line symbol ($). In 2.3.9 and later, + only directories that match the expression are affected by the enclosed + directives. +

+ +

Trailing Slash

+ This directive applies to requests for directories that may or may + not end in a trailing slash, so expressions that are anchored to the + end of line ($) must be written with care. +

+ +

Consulte también

<Directory> for +a description of how regular expressions are mixed in with normal +<Directory>s
How <Directory>, <Location> and +<Files> sections work for an explanation of how these different +sections are combined when a request is received

DocumentRoot Directiva

+ + + + + + + +

Descripción:	Directory that forms the main document tree visible +from the web
Sintaxis:	`DocumentRoot directory-path`
Valor por defecto:	`DocumentRoot /usr/local/apache/htdocs`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

This directive sets the directory from which httpd + will serve files. Unless matched by a directive like Alias, the server appends the + path from the requested URL to the document root to make the + path to the document. Example:

+ +

+ DocumentRoot /usr/web +

+ +

then an access to + http://www.my.host.com/index.html refers to + /usr/web/index.html. If the directory-path is + not absolute then it is assumed to be relative to the ServerRoot.

+ +

The DocumentRoot should be specified without + a trailing slash.

+ +

Consulte también

Mapping URLs to Filesystem +Locations

<Else> Directiva

+ + + + + + + +

Descripción:	Contains directives that apply only if the condition of a +previous `<If>` or +`<ElseIf>` section is not +satisfied by a request at runtime
Sintaxis:	`<Else> ... </Else>`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

Consulte también

<If>
<ElseIf>
How <Directory>, <Location>, + <Files> sections work for an explanation of how these + different sections are combined when a request is received. + <If>, + <ElseIf>, and + <Else> are applied last.

<ElseIf> Directiva

+ + + + + + + +

Descripción:	Contains directives that apply only if a condition is satisfied +by a request at runtime while the condition of a previous +`<If>` or +`<ElseIf>` section is not +satisfied
Sintaxis:	`<ElseIf expression> ... </ElseIf>`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

Consulte también

Expressions in Apache HTTP Server, +for a complete reference and more examples.
<If>
<Else>
How <Directory>, <Location>, + <Files> sections work for an explanation of how these + different sections are combined when a request is received. + <If>, + <ElseIf>, and + <Else> are applied last.

EnableMMAP Directiva

+ + + + + + + + +

Descripción:	Use memory-mapping to read files during delivery
Sintaxis:	`EnableMMAP On\|Off`
Valor por defecto:	`EnableMMAP On`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core

This directive controls whether the httpd may use + memory-mapping if it needs to read the contents of a file during + delivery. By default, when the handling of a request requires + access to the data within a file -- for example, when delivering a + server-parsed file using mod_include -- Apache httpd + memory-maps the file if the OS supports it.

+ +

This memory-mapping sometimes yields a performance improvement. + But in some environments, it is better to disable the memory-mapping + to prevent operational problems:

+ +

On some multiprocessor systems, memory-mapping can reduce the + performance of the httpd.
Deleting or truncating a file while httpd + has it memory-mapped can cause httpd to + crash with a segmentation fault. +

+ +

For server configurations that are vulnerable to these problems, + you should disable memory-mapping of delivered files by specifying:

+ +

+ EnableMMAP Off +

+ +

For NFS mounted files, this feature may be disabled explicitly for + the offending files by specifying:

+ +

+ <Directory "/path-to-nfs-files"> + + EnableMMAP Off + + </Directory> +

+ +

EnableSendfile Directiva

+ + + + + + + + + +

Descripción:	Use the kernel sendfile support to deliver files to the client
Sintaxis:	`EnableSendfile On\|Off`
Valor por defecto:	`EnableSendfile Off`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core
Compatibilidad:	Available in version 2.0.44 and later. Default changed to Off in +version 2.3.9.

This directive controls whether httpd may use the + sendfile support from the kernel to transmit file contents to the client. + By default, when the handling of a request requires no access + to the data within a file -- for example, when delivering a + static file -- Apache httpd uses sendfile to deliver the file contents + without ever reading the file if the OS supports it.

+ +

This sendfile mechanism avoids separate read and send operations, + and buffer allocations. But on some platforms or within some + filesystems, it is better to disable this feature to avoid + operational problems:

+ +

Some platforms may have broken sendfile support that the build + system did not detect, especially if the binaries were built on + another box and moved to such a machine with broken sendfile + support.
On Linux the use of sendfile triggers TCP-checksum + offloading bugs on certain networking cards when using IPv6.
On Linux on Itanium, sendfile may be unable to handle files + over 2GB in size.
With a network-mounted DocumentRoot (e.g., NFS, SMB, CIFS, FUSE), + the kernel may be unable to serve the network file through + its own cache.

+ +

For server configurations that are not vulnerable to these problems, + you may enable this feature by specifying:

+ +

+ EnableSendfile On +

+ +

For network mounted files, this feature may be disabled explicitly + for the offending files by specifying:

+ +

+ <Directory "/path-to-nfs-files"> + + EnableSendfile Off + + </Directory> +

Please note that the per-directory and .htaccess configuration + of EnableSendfile is not supported by + mod_cache_disk. + Only global definition of EnableSendfile + is taken into account by the module. +

+ +

Error Directiva

+ + + + + + + +

Descripción:	Abort configuration parsing with a custom error message
Sintaxis:	`Error message`
Contexto:	server config, virtual host, directory, .htaccess
Estado:	Core
Módulo:	core
Compatibilidad:	2.3.9 and later

If an error can be detected within the configuration, this + directive can be used to generate a custom error message, and halt + configuration parsing. The typical use is for reporting required + modules which are missing from the configuration.

+ +

Example

+ # ensure that mod_include is loaded + <IfModule !include_module> + Error mod_include is required by mod_foo. Load it with LoadModule. + </IfModule> + + # ensure that exactly one of SSL,NOSSL is defined + <IfDefine SSL> + <IfDefine NOSSL> + Error Both SSL and NOSSL are defined. Define only one of them. + </IfDefine> + </IfDefine> + <IfDefine !SSL> + <IfDefine !NOSSL> + Error Either SSL or NOSSL must be defined. + </IfDefine> + </IfDefine> +

+ + +

ErrorDocument Directiva

+ + + + + + + +

Descripción:	What the server will return to the client +in case of an error
Sintaxis:	`ErrorDocument error-code document`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core

In the event of a problem or error, Apache httpd can be configured + to do one of four things,

+ +

output a simple hardcoded error message
output a customized message
redirect to a local URL-path to handle the + problem/error
redirect to an external URL to handle the + problem/error

+ +

The first option is the default, while options 2-4 are + configured using the ErrorDocument + directive, which is followed by the HTTP response code and a URL + or a message. Apache httpd will sometimes offer additional information + regarding the problem/error.

+ +

URLs can begin with a slash (/) for local web-paths (relative + to the DocumentRoot), or be a + full URL which the client can resolve. Alternatively, a message + can be provided to be displayed by the browser. Examples:

+ +

+ ErrorDocument 500 http://foo.example.com/cgi-bin/tester + ErrorDocument 404 /cgi-bin/bad_urls.pl + ErrorDocument 401 /subscription_info.html + ErrorDocument 403 "Sorry can't allow you access today" +

+ +

Additionally, the special value default can be used + to specify Apache httpd's simple hardcoded message. While not required + under normal circumstances, default will restore + Apache httpd's simple hardcoded message for configurations that would + otherwise inherit an existing ErrorDocument.

+ +

+ ErrorDocument 404 /cgi-bin/bad_urls.pl + <Directory /web/docs> + + ErrorDocument 404 default + + </Directory> +

+ +

Note that when you specify an ErrorDocument + that points to a remote URL (ie. anything with a method such as + http in front of it), Apache HTTP Server will send a redirect to the + client to tell it where to find the document, even if the + document ends up being on the same server. This has several + implications, the most important being that the client will not + receive the original error status code, but instead will + receive a redirect status code. This in turn can confuse web + robots and other clients which try to determine if a URL is + valid using the status code. In addition, if you use a remote + URL in an ErrorDocument 401, the client will not + know to prompt the user for a password since it will not + receive the 401 status code. Therefore, if you use an + ErrorDocument 401 directive then it must refer to a local + document.

+ +

Microsoft Internet Explorer (MSIE) will by default ignore + server-generated error messages when they are "too small" and substitute + its own "friendly" error messages. The size threshold varies depending on + the type of error, but in general, if you make your error document + greater than 512 bytes, then MSIE will show the server-generated + error rather than masking it. More information is available in + Microsoft Knowledge Base article Q294807.

+ +

Although most error messages can be overriden, there are certain + circumstances where the internal messages are used regardless of the + setting of ErrorDocument. In + particular, if a malformed request is detected, normal request processing + will be immediately halted and the internal error message returned. + This is necessary to guard against security problems caused by + bad requests.

+ +

If you are using mod_proxy, you may wish to enable + ProxyErrorOverride so that you can provide + custom error messages on behalf of your Origin servers. If you don't enable ProxyErrorOverride, + Apache httpd will not generate custom error documents for proxied content.

+ +

Consulte también

documentation of + customizable responses

ErrorLog Directiva

+ + + + + + + +

Descripción:	Location where the server will log errors
Sintaxis:	`ErrorLog file-path\|syslog[:facility]`
Valor por defecto:	`ErrorLog logs/error_log (Unix) ErrorLog logs/error.log (Windows and OS/2)`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

The ErrorLog directive sets the name of + the file to which the server will log any errors it encounters. If + the file-path is not absolute then it is assumed to be + relative to the ServerRoot.

+ +

Example

+ ErrorLog /var/log/httpd/error_log +

+ +

If the file-path + begins with a pipe character "|" then it is assumed to be a + command to spawn to handle the error log.

+ +

Example

+ ErrorLog "|/usr/local/bin/httpd_errors" +

+ +

See the notes on piped logs for + more information.

+ +

Using syslog instead of a filename enables logging + via syslogd(8) if the system supports it. The default is to use + syslog facility local7, but you can override this by + using the syslog:facility syntax where + facility can be one of the names usually documented in + syslog(1). The facility is effectively global, and if it is changed + in individual virtual hosts, the final facility specified affects the + entire server.

+ +

Example

+ ErrorLog syslog:user +

+ +

SECURITY: See the security tips + document for details on why your security could be compromised + if the directory where log files are stored is writable by + anyone other than the user that starts the server.

Note

When entering a file path on non-Unix platforms, care should be taken + to make sure that only forward slashed are used even though the platform + may allow the use of back slashes. In general it is a good idea to always + use forward slashes throughout the configuration files.

+ +

Consulte también

LogLevel
Apache HTTP Server Log Files

ErrorLogFormat Directiva

+ + + + + + + +

Descripción:	Format specification for error log entries
Sintaxis:	`ErrorLog [connection\|request] format`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache httpd 2.3.9 and later

ErrorLogFormat allows to specify what + supplementary information is logged in the error log in addition to the + actual log message.

+ +

Simple example

+ ErrorLogFormat "[%t] [%l] [pid %P] %F: %E: [client %a] %M" +

+ +

Specifying connection or request as first + paramter allows to specify additional formats, causing additional + information to be logged when the first message is logged for a specific + connection or request, respectivly. This additional information is only + logged once per connection/request. If a connection or request is processed + without causing any log message, the additional information is not logged + either.

+ +

It can happen that some format string items do not produce output. For + example, the Referer header is only present if the log message is + associated to a request and the log message happens at a time when the + Referer header has already been read from the client. If no output is + produced, the default behaviour is to delete everything from the preceeding + space character to the next space character. This means the log line is + implicitly divided into fields on non-whitespace to whitespace transitions. + If a format string item does not produce output, the whole field is + ommitted. For example, if the remote address %a in the log + format [%t] [%l] [%a] %M is not available, the surrounding + brackets are not logged either. Space characters can be escaped with a + backslash to prevent them from delimiting a field. The combination '% ' + (percent space) is a zero-witdh field delimiter that does not produce any + output.

+ +

The above behaviour can be changed by adding modifiers to the format + string item. A - (minus) modifier causes a minus to be logged if the + respective item does not produce any output. In once-per-connection/request + formats, it is also possible to use the + (plus) modifier. If an + item with the plus modifier does not produce any output, the whole line is + ommitted.

+ +

A number as modifier can be used to assign a log severity level to a + format item. The item will only be logged if the severity of the log + message is not higher than the specified log severity level. The number can + range from 1 (alert) over 4 (warn) and 7 (debug) to 15 (trace8).

+ +

Some format string items accept additional parameters in braces.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Format String	Description
`%%`	The percent sign
`%...a`	Remote IP-address and port
`%...A`	Local IP-address and port
`%...{name}e`	Request environment variable `name`
`%...E`	APR/OS error status code and string
`%...F`	Source file name and line number of the log call
`%...{name}i`	Request header `name`
`%...k`	Number of keep-alive requests on this connection
`%...l`	Loglevel of the message
`%...L`	Log ID of the request
`%...{c}L`	Log ID of the connection
`%...{C}L`	Log ID of the connection if used in connection scope, empty otherwise
`%...m`	Name of the module logging the message
`%M`	The actual log message
`%...{name}n`	Request note `name`
`%...P`	Process ID of current process
`%...T`	Thread ID of current thread
`%...t`	The current time
`%...{u}t`	The current time including micro-seconds
`%...{cu}t`	The current time in compact ISO 8601 format, including + micro-seconds
`%...v`	The canonical `ServerName` + of the current server.
`%...V`	The server name of the server serving the request according to the + `UseCanonicalName` + setting.
`\` (backslash space)	Non-field delimiting space
`%` (percent space)	Field delimiter (no output)

+ +

The log ID format %L produces a unique id for a connection + or request. This can be used to correlate which log lines belong to the + same connection or request, which request happens on which connection. + A %L format string is also available in + mod_log_config, to allow to correlate access log entries + with error log lines. If mod_unique_id is loaded, its + unique id will be used as log ID for requests.

+ +

Example (somewhat similar to default format)

+ ErrorLogFormat "[%{u}t] [%-m:%l] [pid %P] %7F: %E: [client\ %a] + %M% ,\ referer\ %{Referer}i" +

+ +

Example (similar to the 2.2.x format)

+ ErrorLogFormat "[%t] [%l] %7F: %E: [client\ %a] + %M% ,\ referer\ %{Referer}i" +

+ +

Advanced example with request/connection log IDs

+ ErrorLogFormat "[%{uc}t] [%-m:%-l] [R:%L] [C:%{C}L] %7F: %E: %M" + ErrorLogFormat request "[%{uc}t] [R:%L] Request %k on C:%{c}L pid:%P tid:%T" + ErrorLogFormat request "[%{uc}t] [R:%L] UA:'%+{User-Agent}i'" + ErrorLogFormat request "[%{uc}t] [R:%L] Referer:'%+{Referer}i'" + ErrorLogFormat connection "[%{uc}t] [C:%{c}L] local\ %a remote\ %A" +

+ + +

Consulte también

ExtendedStatus Directiva

+ + + + + + + +

Descripción:	Keep track of extended status information for each +request
Sintaxis:	`ExtendedStatus On\|Off`
Valor por defecto:	`ExtendedStatus Off[*]`
Contexto:	server config
Estado:	Core
Módulo:	core

This option tracks additional data per worker about the + currently executing request, and a utilization summary; you + can see these variables during runtime by configuring + mod_status. Note that other modules may + rely on this scoreboard.

+ +

This setting applies to the entire server, and cannot be + enabled or disabled on a virtualhost-by-virtualhost basis. + The collection of extended status information can slow down + the server. Also note that this setting cannot be changed + during a graceful restart.

+ +

Note that loading mod_status will change + the default behavior to ExtendedStatus On, while other + third party modules may do the same. Such modules rely on + collecting detailed information about the state of all workers. + The default is changed by mod_status beginning + with version 2.3.6; the previous default was always Off.

+ + +

FileETag Directiva

+ + + + + + + + +

Descripción:	File attributes used to create the ETag +HTTP response header for static files
Sintaxis:	`FileETag component ...`
Valor por defecto:	`FileETag INode MTime Size`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core

+ The FileETag directive configures the file + attributes that are used to create the ETag (entity + tag) response header field when the document is based on a static file. + (The ETag value is used in cache management to save + network bandwidth.) The + FileETag directive allows you to choose + which of these -- if any -- should be used. The recognized keywords are: +

+ +

INode: The file's i-node number will be included in the calculation
MTime: The date and time the file was last modified will be included
Size: The number of bytes in the file will be included
All: All available fields will be used. This is equivalent to: +
FileETag INode MTime Size
None: If a document is file-based, no ETag field will be + included in the response

+ +

The INode, MTime, and Size + keywords may be prefixed with either + or -, + which allow changes to be made to the default setting inherited + from a broader scope. Any keyword appearing without such a prefix + immediately and completely cancels the inherited setting.

+ +

If a directory's configuration includes + FileETag INode MTime Size, and a + subdirectory's includes FileETag -INode, + the setting for that subdirectory (which will be inherited by + any sub-subdirectories that don't override it) will be equivalent to + FileETag MTime Size.

Warning

+ Do not change the default for directories or locations that have WebDAV + enabled and use mod_dav_fs as a storage provider. + mod_dav_fs uses INode MTime Size + as a fixed format for ETag comparisons on conditional requests. + These conditional requests will break if the ETag format is + changed via FileETag. +

Server Side Includes

+ An ETag is not generated for responses parsed by mod_include, + since the response entity can change without a change of the INode, MTime, or Size + of the static file with embedded SSI directives. +

+ + +

<Files> Directiva

+ + + + + + + +

Descripción:	Contains directives that apply to matched +filenames
Sintaxis:	`<Files filename> ... </Files>`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

The <Files> directive + limits the scope of the enclosed directives by filename. It is comparable + to the <Directory> + and <Location> + directives. It should be matched with a </Files> + directive. The directives given within this section will be applied to + any object with a basename (last component of filename) matching the + specified filename. <Files> + sections are processed in the order they appear in the + configuration file, after the <Directory> sections and + .htaccess files are read, but before <Location> sections. Note + that <Files> can be nested + inside <Directory> sections to restrict the + portion of the filesystem they apply to.

+ +

The filename argument should include a filename, or + a wild-card string, where ? matches any single character, + and * matches any sequences of characters. + Regular expressions + can also be used, with the addition of the + ~ character. For example:

+ +

+ <Files ~ "\.(gif|jpe?g|png)$"> +

+ +

would match most common Internet graphics formats. <FilesMatch> is preferred, + however.

+ +

Note that unlike <Directory> and <Location> sections, <Files> sections can be used inside + .htaccess files. This allows users to control access to + their own files, at a file-by-file level.

+ + +

Consulte también

How <Directory>, <Location> + and <Files> sections work for an explanation of how these + different sections are combined when a request is received

<FilesMatch> Directiva

+ + + + + + + +

Descripción:	Contains directives that apply to regular-expression matched +filenames
Sintaxis:	`<FilesMatch regex> ... </FilesMatch>`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

The <FilesMatch> directive + limits the scope of the enclosed directives by filename, just as the + <Files> directive + does. However, it accepts a regular + expression. For example:

+ +

+ <FilesMatch "\.(gif|jpe?g|png)$"> +

+ +

would match most common Internet graphics formats.

+ +

Consulte también

How <Directory>, <Location> + and <Files> sections work for an explanation of how these + different sections are combined when a request is received

ForceType Directiva

+ + + + + + + + +

Descripción:	Forces all matching files to be served with the specified +media type in the HTTP Content-Type header field
Sintaxis:	`ForceType media-type\|None`
Contexto:	directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core
Compatibilidad:	Moved to the core in Apache httpd 2.0

When placed into an .htaccess file or a + <Directory>, or + <Location> or + <Files> + section, this directive forces all matching files to be served + with the content type identification given by + media-type. For example, if you had a directory full of + GIF files, but did not want to label them all with .gif, + you might want to use:

+ +

+ ForceType image/gif +

+ +

Note that this directive overrides other indirect media type + associations defined in mime.types or via the + AddType.

+ +

You can also override more general + ForceType settings + by using the value of None:

+ +

+ # force all files to be image/gif: + <Location /images> + + ForceType image/gif + + </Location> + + # but normal mime-type associations here: + <Location /images/mixed> + + ForceType None + + </Location> +

+ +

This directive primarily overrides the content types generated for + static files served out of the filesystem. For resources other than + static files, where the generator of the response typically specifies + a Content-Type, this directive has no effect.

+ + +

GprofDir Directiva

+ + + + + + +

Descripción:	Directory to write gmon.out profiling data to.
Sintaxis:	`GprofDir /tmp/gprof/\|/tmp/gprof/%`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

When the server has been compiled with gprof profiling support, + GprofDir causes gmon.out files to + be written to the specified directory when the process exits. If the + argument ends with a percent symbol ('%'), subdirectories are created + for each process id.

+ +

This directive currently only works with the prefork + MPM.

+ +

HostnameLookups Directiva

+ + + + + + + +

Descripción:	Enables DNS lookups on client IP addresses
Sintaxis:	`HostnameLookups On\|Off\|Double`
Valor por defecto:	`HostnameLookups Off`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core

This directive enables DNS lookups so that host names can be + logged (and passed to CGIs/SSIs in REMOTE_HOST). + The value Double refers to doing double-reverse + DNS lookup. That is, after a reverse lookup is performed, a forward + lookup is then performed on that result. At least one of the IP + addresses in the forward lookup must match the original + address. (In "tcpwrappers" terminology this is called + PARANOID.)

+ +

Regardless of the setting, when mod_authz_host is + used for controlling access by hostname, a double reverse lookup + will be performed. This is necessary for security. Note that the + result of this double-reverse isn't generally available unless you + set HostnameLookups Double. For example, if only + HostnameLookups On and a request is made to an object + that is protected by hostname restrictions, regardless of whether + the double-reverse fails or not, CGIs will still be passed the + single-reverse result in REMOTE_HOST.

+ +

The default is Off in order to save the network + traffic for those sites that don't truly need the reverse + lookups done. It is also better for the end users because they + don't have to suffer the extra latency that a lookup entails. + Heavily loaded sites should leave this directive + Off, since DNS lookups can take considerable + amounts of time. The utility logresolve, compiled by + default to the bin subdirectory of your installation + directory, can be used to look up host names from logged IP addresses + offline.

+ +

<If> Directiva

+ + + + + + + +

Descripción:	Contains directives that apply only if a condition is +satisfied by a request at runtime
Sintaxis:	`<If expression> ... </If>`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

The <If> directive + evaluates an expression at runtime, and applies the enclosed + directives if and only if the expression evaluates to true. + For example:

+ +

+ <If "$req{Host} = ''"> +

+ +

would match HTTP/1.0 requests without a Host: header.

+ +

You may compare the value of any variable in the request headers + ($req), response headers ($resp) or environment ($env) in your + expression.

+ +

Apart from =, If can use the IN + operator to compare if the expression is in a given range:

+ +

+ <If %{REQUEST_METHOD} IN GET,HEAD,OPTIONS> +

+ + +

Consulte también

Expressions in Apache HTTP Server, +for a complete reference and more examples.
How <Directory>, <Location>, + <Files> sections work for an explanation of how these + different sections are combined when a request is received. + <If> has the same precedence + and usage as <Files>

<IfDefine> Directiva

+ + + + + + + +

Descripción:	Encloses directives that will be processed only +if a test is true at startup
Sintaxis:	`<IfDefine [!]parameter-name> ... + </IfDefine>`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

The <IfDefine test>...</IfDefine> + section is used to mark directives that are conditional. The + directives within an <IfDefine> + section are only processed if the test is true. If + test is false, everything between the start and end markers is + ignored.

+ +

The test in the <IfDefine> section directive can be one of two forms:

+ +

parameter-name
!parameter-name

+ +

In the former case, the directives between the start and end + markers are only processed if the parameter named + parameter-name is defined. The second format reverses + the test, and only processes the directives if + parameter-name is not defined.

+ +

The parameter-name argument is a define as given on the + httpd command line via -Dparameter + at the time the server was started or by the Define directive.

+ +

<IfDefine> sections are + nest-able, which can be used to implement simple + multiple-parameter tests. Example:

+ +

+ httpd -DReverseProxy -DUseCache -DMemCache ... + + # httpd.conf + <IfDefine ReverseProxy> + + LoadModule proxy_module modules/mod_proxy.so + LoadModule proxy_http_module modules/mod_proxy_http.so + <IfDefine UseCache> + + LoadModule cache_module modules/mod_cache.so + <IfDefine MemCache> + + LoadModule mem_cache_module modules/mod_mem_cache.so + + </IfDefine> + <IfDefine !MemCache> + + LoadModule cache_disk_module modules/mod_cache_disk.so + + </IfDefine> + + </IfDefine> + + </IfDefine> +

+ +

<IfModule> Directiva

+ + + + + + + + +

Descripción:	Encloses directives that are processed conditional on the +presence or absence of a specific module
Sintaxis:	`<IfModule [!]module-file\|module-identifier> ... + </IfModule>`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core
Compatibilidad:	Module identifiers are available in version 2.1 and +later.

The <IfModule test>...</IfModule> + section is used to mark directives that are conditional on the presence of + a specific module. The directives within an <IfModule> section are only processed if the test + is true. If test is false, everything between the start and + end markers is ignored.

+ +

The test in the <IfModule> section directive can be one of two forms:

+ +

module
!module

+ +

In the former case, the directives between the start and end + markers are only processed if the module named module + is included in Apache httpd -- either compiled in or + dynamically loaded using LoadModule. The second format reverses the test, + and only processes the directives if module is + not included.

+ +

The module argument can be either the module identifier or + the file name of the module, at the time it was compiled. For example, + rewrite_module is the identifier and + mod_rewrite.c is the file name. If a module consists of + several source files, use the name of the file containing the string + STANDARD20_MODULE_STUFF.

+ +

<IfModule> sections are + nest-able, which can be used to implement simple multiple-module + tests.

+ +

This section should only be used if you need to have one + configuration file that works whether or not a specific module + is available. In normal operation, directives need not be + placed in <IfModule> + sections.

+ +

Include Directiva

+ + + + + + + +

Descripción:	Includes other configuration files from within +the server configuration files
Sintaxis:	`Include [optional\|strict] file-path\|directory-path\|wildcard`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core
Compatibilidad:	Wildcard matching available in 2.0.41 and later, directory +wildcard matching available in 2.3.6 and later

This directive allows inclusion of other configuration files + from within the server configuration files.

+ +

Shell-style (fnmatch()) wildcard characters can be used + in the filename or directory parts of the path to include several files + at once, in alphabetical order. In addition, if + Include points to a directory, rather than a file, + Apache httpd will read all files in that directory and any subdirectory. + However, including entire directories is not recommended, because it is + easy to accidentally leave temporary files in a directory that can cause + httpd to fail. Instead, we encourage you to use the + wildcard syntax shown below, to include files that match a particular + pattern, such as *.conf, for example.

+ +

When a wildcard is specified for a file component of + the path, and no file matches the wildcard, the + Include + directive will be silently ignored. When a wildcard is + specified for a directory component of the path, and + no directory matches the wildcard, the + Include directive will + fail with an error saying the directory cannot be found. +

+ +

For further control over the behaviour of the server when no files or + directories match, prefix the path with the modifiers optional + or strict. If optional is specified, any wildcard + file or directory that does not match will be silently ignored. If + strict is specified, any wildcard file or directory that does + not match at least one file will cause server startup to fail.

+ +

When a directory or file component of the path is + specified exactly, and that directory or file does not exist, + Include directive will fail with an + error saying the file or directory cannot be found.

+ +

The file path specified may be an absolute path, or may be relative + to the ServerRoot directory.

+ +

Examples:

+ +

+ Include /usr/local/apache2/conf/ssl.conf + Include /usr/local/apache2/conf/vhosts/*.conf +

+ +

Or, providing paths relative to your ServerRoot directory:

+ +

+ Include conf/ssl.conf + Include conf/vhosts/*.conf +

+ +

Wildcards may be included in the directory or file portion of the + path. In the following example, the server will fail to load if no + directories match conf/vhosts/*, but will load successfully if no + files match *.conf.

+ +

+ Include conf/vhosts/*/vhost.conf + Include conf/vhosts/*/*.conf +

+ +

In this example, the server will fail to load if either + conf/vhosts/* matches no directories, or if *.conf matches no files:

+ +

+ Include strict conf/vhosts/*/*.conf +

+ +

In this example, the server load successfully if either conf/vhosts/* + matches no directories, or if *.conf matches no files:

+ +

+ Include optional conf/vhosts/*/*.conf +

+ + +

Consulte también

apachectl

IncludeOptional Directiva

+ + + + + + + +

Descripción:	Includes other configuration files from within +the server configuration files
Sintaxis:	`IncludeOptional file-path\|directory-path\|wildcard`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core
Compatibilidad:	Available in 2.3.6 and later

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

Consulte también

Include
apachectl

KeepAlive Directiva

+ + + + + + + +

Descripción:	Enables HTTP persistent connections
Sintaxis:	`KeepAlive On\|Off`
Valor por defecto:	`KeepAlive On`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

The Keep-Alive extension to HTTP/1.0 and the persistent + connection feature of HTTP/1.1 provide long-lived HTTP sessions + which allow multiple requests to be sent over the same TCP + connection. In some cases this has been shown to result in an + almost 50% speedup in latency times for HTML documents with + many images. To enable Keep-Alive connections, set + KeepAlive On.

+ +

For HTTP/1.0 clients, Keep-Alive connections will only be + used if they are specifically requested by a client. In + addition, a Keep-Alive connection with an HTTP/1.0 client can + only be used when the length of the content is known in + advance. This implies that dynamic content such as CGI output, + SSI pages, and server-generated directory listings will + generally not use Keep-Alive connections to HTTP/1.0 clients. + For HTTP/1.1 clients, persistent connections are the default + unless otherwise specified. If the client requests it, chunked + encoding will be used in order to send content of unknown + length over persistent connections.

+ +

When a client uses a Keep-Alive connection it will be counted + as a single "request" for the MaxConnectionsPerChild directive, regardless + of how many requests are sent using the connection.

+ +

Consulte también

MaxKeepAliveRequests

KeepAliveTimeout Directiva

+ + + + + + + + +

Descripción:	Amount of time the server will wait for subsequent +requests on a persistent connection
Sintaxis:	`KeepAliveTimeout num[ms]`
Valor por defecto:	`KeepAliveTimeout 5`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Specifying a value in milliseconds is available in +Apache httpd 2.3.2 and later

The number of seconds Apache httpd will wait for a subsequent + request before closing the connection. By adding a postfix of ms the + timeout can be also set in milliseconds. Once a request has been + received, the timeout value specified by the + Timeout directive applies.

+ +

Setting KeepAliveTimeout to a high value + may cause performance problems in heavily loaded servers. The + higher the timeout, the more server processes will be kept + occupied waiting on connections with idle clients.

+ +

In a name-based virtual host context, the value of the first + defined virtual host (the default host) in a set of NameVirtualHost will be used. + The other values will be ignored.

+ +

<Limit> Directiva

+ + + + + + + +

Descripción:	Restrict enclosed access controls to only certain HTTP +methods
Sintaxis:	`<Limit method [method] ... > ... + </Limit>`
Contexto:	directory, .htaccess
Anula:	AuthConfig, Limit
Estado:	Core
Módulo:	core

Access controls are normally effective for + all access methods, and this is the usual + desired behavior. In the general case, access control + directives should not be placed within a + <Limit> section.

+ +

The purpose of the <Limit> + directive is to restrict the effect of the access controls to the + nominated HTTP methods. For all other methods, the access + restrictions that are enclosed in the <Limit> bracket will have no + effect. The following example applies the access control + only to the methods POST, PUT, and + DELETE, leaving all other methods unprotected:

+ +

+ <Limit POST PUT DELETE> + + Require valid-user + + </Limit> +

+ +

The method names listed can be one or more of: GET, + POST, PUT, DELETE, + CONNECT, OPTIONS, + PATCH, PROPFIND, PROPPATCH, + MKCOL, COPY, MOVE, + LOCK, and UNLOCK. The method name is + case-sensitive. If GET is used it will also + restrict HEAD requests. The TRACE method + cannot be limited (see TraceEnable).

+ +

A <LimitExcept> section should always be + used in preference to a <Limit> + section when restricting access, since a <LimitExcept> section provides protection + against arbitrary methods.

+ +

The <Limit> and + <LimitExcept> + directives may be nested. In this case, each successive level of + <Limit> or <LimitExcept> directives must + further restrict the set of methods to which access controls apply.

+ +

When using + <Limit> or + <LimitExcept> directives with + the Require directive, + note that the first Require + to succeed authorizes the request, regardless of the presence of other + Require directives.

+ +

For example, given the following configuration, all users will + be authorized for POST requests, and the + Require group editors directive will be ignored + in all cases:

+ +

+ <LimitExcept GET> + + Require valid-user + + </LimitExcept> + <Limit POST> + + Require group editors + + </Limit> +

+ +

<LimitExcept> Directiva

+ + + + + + + +

Descripción:	Restrict access controls to all HTTP methods +except the named ones
Sintaxis:	`<LimitExcept method [method] ... > ... + </LimitExcept>`
Contexto:	directory, .htaccess
Anula:	AuthConfig, Limit
Estado:	Core
Módulo:	core

<LimitExcept> and + </LimitExcept> are used to enclose + a group of access control directives which will then apply to any + HTTP access method not listed in the arguments; + i.e., it is the opposite of a <Limit> section and can be used to control + both standard and nonstandard/unrecognized methods. See the + documentation for <Limit> for more details.

+ +

For example:

+ +

+ <LimitExcept POST GET> + + Require valid-user + + </LimitExcept> +

+ + +

LimitInternalRecursion Directiva

+ + + + + + + + +

Descripción:	Determine maximum number of internal redirects and nested +subrequests
Sintaxis:	`LimitInternalRecursion number [number]`
Valor por defecto:	`LimitInternalRecursion 10`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache httpd 2.0.47 and later

An internal redirect happens, for example, when using the Action directive, which internally + redirects the original request to a CGI script. A subrequest is Apache httpd's + mechanism to find out what would happen for some URI if it were requested. + For example, mod_dir uses subrequests to look for the + files listed in the DirectoryIndex + directive.

+ +

LimitInternalRecursion prevents the server + from crashing when entering an infinite loop of internal redirects or + subrequests. Such loops are usually caused by misconfigurations.

+ +

The directive stores two different limits, which are evaluated on + per-request basis. The first number is the maximum number of + internal redirects, that may follow each other. The second number + determines, how deep subrequests may be nested. If you specify only one + number, it will be assigned to both limits.

+ +

Example

+ LimitInternalRecursion 5 +

+ +

LimitRequestBody Directiva

+ + + + + + + + +

Descripción:	Restricts the total size of the HTTP request body sent +from the client
Sintaxis:	`LimitRequestBody bytes`
Valor por defecto:	`LimitRequestBody 0`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

This directive specifies the number of bytes from 0 + (meaning unlimited) to 2147483647 (2GB) that are allowed in a + request body. See the note below for the limited applicability + to proxy requests.

+ +

The LimitRequestBody directive allows + the user to set a limit on the allowed size of an HTTP request + message body within the context in which the directive is given + (server, per-directory, per-file or per-location). If the client + request exceeds that limit, the server will return an error + response instead of servicing the request. The size of a normal + request message body will vary greatly depending on the nature of + the resource and the methods allowed on that resource. CGI scripts + typically use the message body for retrieving form information. + Implementations of the PUT method will require + a value at least as large as any representation that the server + wishes to accept for that resource.

+ +

This directive gives the server administrator greater + control over abnormal client request behavior, which may be + useful for avoiding some forms of denial-of-service + attacks.

+ +

If, for example, you are permitting file upload to a particular + location, and wish to limit the size of the uploaded file to 100K, + you might use the following directive:

+ +

+ LimitRequestBody 102400 +

+ +

For a full description of how this directive is interpreted by + proxy requests, see the mod_proxy documentation.

+ + +

LimitRequestFields Directiva

+ + + + + + + +

Descripción:	Limits the number of HTTP request header fields that +will be accepted from the client
Sintaxis:	`LimitRequestFields number`
Valor por defecto:	`LimitRequestFields 100`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

Number is an integer from 0 (meaning unlimited) to + 32767. The default value is defined by the compile-time + constant DEFAULT_LIMIT_REQUEST_FIELDS (100 as + distributed).

+ +

The LimitRequestFields directive allows + the server administrator to modify the limit on the number of + request header fields allowed in an HTTP request. A server needs + this value to be larger than the number of fields that a normal + client request might include. The number of request header fields + used by a client rarely exceeds 20, but this may vary among + different client implementations, often depending upon the extent + to which a user has configured their browser to support detailed + content negotiation. Optional HTTP extensions are often expressed + using request header fields.

+ +

This directive gives the server administrator greater + control over abnormal client request behavior, which may be + useful for avoiding some forms of denial-of-service attacks. + The value should be increased if normal clients see an error + response from the server that indicates too many fields were + sent in the request.

+ +

For example:

+ +

+ LimitRequestFields 50 +

+ +

Warning

When name-based virtual hosting is used, the value for this + directive is taken from the default (first-listed) virtual host for the + NameVirtualHost the connection was mapped to.

+ + +

LimitRequestFieldSize Directiva

+ + + + + + + +

Descripción:	Limits the size of the HTTP request header allowed from the +client
Sintaxis:	`LimitRequestFieldSize bytes`
Valor por defecto:	`LimitRequestFieldSize 8190`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

This directive specifies the number of bytes + that will be allowed in an HTTP request header.

+ +

The LimitRequestFieldSize directive + allows the server administrator to reduce or increase the limit + on the allowed size of an HTTP request header field. A server + needs this value to be large enough to hold any one header field + from a normal client request. The size of a normal request header + field will vary greatly among different client implementations, + often depending upon the extent to which a user has configured + their browser to support detailed content negotiation. SPNEGO + authentication headers can be up to 12392 bytes.

+ +

This directive gives the server administrator greater + control over abnormal client request behavior, which may be + useful for avoiding some forms of denial-of-service attacks.

+ +

For example:

+ +

+ LimitRequestFieldSize 4094 +

+ +

Under normal conditions, the value should not be changed from + the default.

+ +

Warning

When name-based virtual hosting is used, the value for this + directive is taken from the default (first-listed) virtual host for the + NameVirtualHost the connection was mapped to.

+ + +

LimitRequestLine Directiva

+ + + + + + + +

Descripción:	Limit the size of the HTTP request line that will be accepted +from the client
Sintaxis:	`LimitRequestLine bytes`
Valor por defecto:	`LimitRequestLine 8190`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

This directive sets the number of bytes that will be + allowed on the HTTP request-line.

+ +

The LimitRequestLine directive allows + the server administrator to reduce or increase the limit on the allowed size + of a client's HTTP request-line. Since the request-line consists of the + HTTP method, URI, and protocol version, the + LimitRequestLine directive places a + restriction on the length of a request-URI allowed for a request + on the server. A server needs this value to be large enough to + hold any of its resource names, including any information that + might be passed in the query part of a GET request.

+ +

This directive gives the server administrator greater + control over abnormal client request behavior, which may be + useful for avoiding some forms of denial-of-service attacks.

+ +

For example:

+ +

+ LimitRequestLine 4094 +

+ +

Under normal conditions, the value should not be changed from + the default.

+ +

Warning

When name-based virtual hosting is used, the value for this + directive is taken from the default (first-listed) virtual host for the + NameVirtualHost the connection was mapped to.

+ + +

LimitXMLRequestBody Directiva

+ + + + + + + + +

Descripción:	Limits the size of an XML-based request body
Sintaxis:	`LimitXMLRequestBody bytes`
Valor por defecto:	`LimitXMLRequestBody 1000000`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

Limit (in bytes) on maximum size of an XML-based request + body. A value of 0 will disable any checking.

+ +

Example:

+ +

+ LimitXMLRequestBody 0 +

+ + +

<Location> Directiva

+ + + + + + +

Descripción:	Applies the enclosed directives only to matching +URLs
Sintaxis:	`<Location + URL-path\|URL> ... </Location>`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

The <Location> directive + limits the scope of the enclosed directives by URL. It is similar to the + <Directory> + directive, and starts a subsection which is terminated with a + </Location> directive. <Location> sections are processed in the + order they appear in the configuration file, after the <Directory> sections and + .htaccess files are read, and after the <Files> sections.

+ +

<Location> sections operate + completely outside the filesystem. This has several consequences. + Most importantly, <Location> + directives should not be used to control access to filesystem + locations. Since several different URLs may map to the same + filesystem location, such access controls may by circumvented.

+ +

The enclosed directives will be applied to the request if the path component + of the URL meets any of the following criteria: +

The specified location matches exactly the path component of the URL. +
The specified location, which ends in a forward slash, is a prefix + of the path component of the URL (treated as a context root). +
The specified location, with the addition of a trailing slash, is a + prefix of the path component of the URL (also treated as a context root). +

+ In the example below, where no trailing slash is used, requests to + /private1, /private1/ and /private1/file.txt will have the enclosed + directives applied, but /private1other would not. +

+ <Location /private1> + ... +

+ In the example below, where a trailing slash is used, requests to + /private2/ and /private2/file.txt will have the enclosed + directives applied, but /private2 and /private2other would not. +

+ <Location /private2/> + ... +

+ +

When to use `<Location>`

+ +

Use <Location> to apply + directives to content that lives outside the filesystem. For + content that lives in the filesystem, use <Directory> and <Files>. An exception is + <Location />, which is an easy way to + apply a configuration to the entire server.

+ +

For all origin (non-proxy) requests, the URL to be matched is a + URL-path of the form /path/. No scheme, hostname, + port, or query string may be included. For proxy requests, the + URL to be matched is of the form + scheme://servername/path, and you must include the + prefix.

+ +

The URL may use wildcards. In a wild-card string, ? matches + any single character, and * matches any sequences of + characters. Neither wildcard character matches a / in the URL-path.

+ +

Regular expressions + can also be used, with the addition of the ~ + character. For example:

+ +

+ <Location ~ "/(extra|special)/data"> +

+ +

would match URLs that contained the substring /extra/data + or /special/data. The directive <LocationMatch> behaves + identical to the regex version of <Location>, and is preferred, for the + simple reason that ~ is hard to distinguish from + - in many fonts.

+ +

The <Location> + functionality is especially useful when combined with the + SetHandler + directive. For example, to enable status requests, but allow them + only from browsers at example.com, you might use:

+ +

+ <Location /status> + + SetHandler server-status + Require host example.com + + </Location> +

+ +

Note about / (slash)

The slash character has special meaning depending on where in a + URL it appears. People may be used to its behavior in the filesystem + where multiple adjacent slashes are frequently collapsed to a single + slash (i.e., /home///foo is the same as + /home/foo). In URL-space this is not necessarily true. + The <LocationMatch> + directive and the regex version of <Location> require you to explicitly specify multiple + slashes if that is your intention.

+ +

For example, <LocationMatch ^/abc> would match + the request URL /abc but not the request URL + //abc. The (non-regex) <Location> directive behaves similarly when used for + proxy requests. But when (non-regex) <Location> is used for non-proxy requests it will + implicitly match multiple slashes with a single slash. For example, + if you specify <Location /abc/def> and the + request is to /abc//def then it will match.

+ +

Consulte también

How <Directory>, <Location> + and <Files> sections work for an explanation of how these + different sections are combined when a request is received.
LocationMatch

<LocationMatch> Directiva

+ + + + + + +

Descripción:	Applies the enclosed directives only to regular-expression +matching URLs
Sintaxis:	`<LocationMatch + regex> ... </LocationMatch>`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

The <LocationMatch> directive + limits the scope of the enclosed directives by URL, in an identical manner + to <Location>. However, + it takes a regular expression + as an argument instead of a simple string. For example:

+ +

+ <LocationMatch "/(extra|special)/data"> +

+ +

would match URLs that contained the substring /extra/data + or /special/data.

+ +

Consulte también

How <Directory>, <Location> + and <Files> sections work for an explanation of how these + different sections are combined when a request is received

LogLevel Directiva

+ + + + + + + + +

Descripción:	Controls the verbosity of the ErrorLog
Sintaxis:	`LogLevel [module:]level + [module:level] ... +`
Valor por defecto:	`LogLevel warn`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core
Compatibilidad:	Per-module and per-directory configuration is available in + Apache HTTP Server 2.3.6 and later

LogLevel adjusts the verbosity of the + messages recorded in the error logs (see ErrorLog directive). The following + levels are available, in order of decreasing + significance:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Level	Description	Example
`emerg`	Emergencies - system is unusable.	"Child cannot open lock file. Exiting"
`alert`	Action must be taken immediately.	"getpwuid: couldn't determine user name from uid"
`crit`	Critical Conditions.	"socket: Failed to get a socket, exiting child"
`error`	Error conditions.	"Premature end of script headers"
`warn`	Warning conditions.	"child process 1234 did not exit, sending another + SIGHUP"
`notice`	Normal but significant condition.	"httpd: caught SIGBUS, attempting to dump core in + ..."
`info`	Informational.	"Server seems busy, (you may need to increase + StartServers, or Min/MaxSpareServers)..."
`debug`	Debug-level messages	"Opening config file ..."
`trace1`	Trace messages	"proxy: FTP: control connection complete"
`trace2`	Trace messages	"proxy: CONNECT: sending the CONNECT request to the remote proxy"
`trace3`	Trace messages	"openssl: Handshake: start"
`trace4`	Trace messages	"read from buffered SSL brigade, mode 0, 17 bytes"
`trace5`	Trace messages	"map lookup FAILED: map=rewritemap key=keyname"
`trace6`	Trace messages	"cache lookup FAILED, forcing new map lookup"
`trace7`	Trace messages, dumping large amounts of data	"\| 0000: 02 23 44 30 13 40 ac 34 df 3d bf 9a 19 49 39 15 \|"
`trace8`	Trace messages, dumping large amounts of data	"\| 0000: 02 23 44 30 13 40 ac 34 df 3d bf 9a 19 49 39 15 \|"

+ +

When a particular level is specified, messages from all + other levels of higher significance will be reported as well. + E.g., when LogLevel info is specified, + then messages with log levels of notice and + warn will also be posted.

+ +

Using a level of at least crit is + recommended.

+ +

For example:

+ +

+ LogLevel notice +

+ +

Note

When logging to a regular file messages of the level + notice cannot be suppressed and thus are always + logged. However, this doesn't apply when logging is done + using syslog.

+ +

Specifying a level without a module name will reset the level + for all modules to that level. Specifying a level with a module + name will set the level for that module only. It is possible to + use the module source file name, the module identifier, or the + module identifier with the trailing _module omitted + as module specification. This means the following three specifications + are equivalent:

+ +

+ LogLevel info ssl:warn + LogLevel info mod_ssl.c:warn + LogLevel info ssl_module:warn +

+ +

It is also possible to change the level per directory:

+ +

+ LogLevel info + <Directory /usr/local/apache/htdocs/app> + LogLevel debug + </Files> +

+ +

+ Per directory loglevel configuration only affects messages that are + logged after the request has been parsed and that are associated with + the request. Log messages which are associated with the connection or + the server are not affected. +

+ +

LogLevelOverride Directiva

+ + + + + + + + +

Descripción:	Override the verbosity of the ErrorLog for certain clients
Sintaxis:	`LogLevel ipaddress[/prefixlen] + [module:]level [module:level] ... +`
Valor por defecto:	`unset`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache HTTP Server 2.5.0 and later

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

Consulte también

LogLevel

MaxKeepAliveRequests Directiva

+ + + + + + + +

Descripción:	Number of requests allowed on a persistent +connection
Sintaxis:	`MaxKeepAliveRequests number`
Valor por defecto:	`MaxKeepAliveRequests 100`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

The MaxKeepAliveRequests directive + limits the number of requests allowed per connection when + KeepAlive is on. If it is + set to 0, unlimited requests will be allowed. We + recommend that this setting be kept to a high value for maximum + server performance.

+ +

For example:

+ +

+ MaxKeepAliveRequests 500 +

+ +

MaxRangeOverlaps Directiva

+ + + + + + + + +

Descripción:	Number of overlapping ranges (eg: `100-200,150-300`) allowed before returning the complete + resource
Sintaxis:	`MaxRangeOverlaps default \| unlimited \| none \| number-of-ranges`
Valor por defecto:	`MaxRangeOverlaps 20`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache HTTP Server 2.3.15 and later

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

MaxRangeReversals Directiva

+ + + + + + + + +

Descripción:	Number of range reversals (eg: `100-200,50-70`) allowed before returning the complete + resource
Sintaxis:	`MaxRangeReversals default \| unlimited \| none \| number-of-ranges`
Valor por defecto:	`MaxRangeReversals 20`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache HTTP Server 2.3.15 and later

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

MaxRanges Directiva

+ + + + + + + + +

Descripción:	Number of ranges allowed before returning the complete +resource
Sintaxis:	`MaxRanges default \| unlimited \| none \| number-of-ranges`
Valor por defecto:	`MaxRanges 200`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache HTTP Server 2.3.15 and later

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

MergeTrailers Directiva

+ + + + + + + + +

Descripción:	Determines whether trailers are merged into headers
Sintaxis:	`MergeTrailers [on\|off]`
Valor por defecto:	`MergeTrailers off`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	2.4.11 and later

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

Mutex Directiva

+ + + + + + + + +

Descripción:	Configures mutex mechanism and lock file directory for all +or specified mutexes
Sintaxis:	`Mutex mechanism [default\|mutex-name] ... [OmitPID]`
Valor por defecto:	`Mutex default`
Contexto:	server config
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache HTTP Server 2.3.4 and later

The Mutex directive sets the mechanism, + and optionally the lock file location, that httpd and modules use + to serialize access to resources. Specify default as + the first argument to change the settings for all mutexes; specify + a mutex name (see table below) as the first argument to override + defaults only for that mutex.

+ +

The Mutex directive is typically used in + the following exceptional situations:

+ +

change the mutex mechanism when the default mechanism selected + by APR has a functional or performance + problem
change the directory used by file-based mutexes when the + default directory does not support locking

+ +

Supported modules

This directive only configures mutexes which have been registered + with the core server using the ap_mutex_register() API. + All modules bundled with httpd support the Mutex + directive, but third-party modules may not. Consult the documentation + of the third-party module, which must indicate the mutex name(s) which + can be configured if this directive is supported.

+ +

The following mutex mechanisms are available:

default | yes +
This selects the default locking implementation, as determined by + APR. The default locking implementation can + be displayed by running httpd with the + -V option.
none | no +
This effectively disables the mutex, and is only allowed for a + mutex if the module indicates that it is a valid choice. Consult the + module documentation for more information.
posixsem +
This is a mutex variant based on a Posix semaphore.
+ +
Warning
+
The semaphore ownership is not recovered if a thread in the process + holding the mutex segfaults, resulting in a hang of the web server.
+
+
sysvsem +
This is a mutex variant based on a SystemV IPC semaphore.
+ +
Warning
+
It is possible to "leak" SysV semaphores if processes crash + before the semaphore is removed.
+
+ +
Security
+
The semaphore API allows for a denial of service attack by any + CGIs running under the same uid as the webserver (i.e., + all CGIs, unless you use something like suexec + or cgiwrapper).
+
+
sem +
This selects the "best" available semaphore implementation, choosing + between Posix and SystemV IPC semaphores, in that order.
pthread +
This is a mutex variant based on cross-process Posix thread + mutexes.
+ +
Warning
+
On most systems, if a child process terminates abnormally while + holding a mutex that uses this implementation, the server will deadlock + and stop responding to requests. When this occurs, the server will + require a manual restart to recover.
+
Solaris is a notable exception as it provides a mechanism which + usually allows the mutex to be recovered after a child process + terminates abnormally while holding a mutex.
+
If your system implements the + pthread_mutexattr_setrobust_np() function, you may be able + to use the pthread option safely.
+
+
fcntl:/path/to/mutex +
This is a mutex variant where a physical (lock-)file and the + fcntl() function are used as the mutex.
+ +
Warning
+
When multiple mutexes based on this mechanism are used within + multi-threaded, multi-process environments, deadlock errors (EDEADLK) + can be reported for valid mutex operations if fcntl() + is not thread-aware, such as on Solaris.
+
+
flock:/path/to/mutex +
This is similar to the fcntl:/path/to/mutex method + with the exception that the flock() function is used to + provide file locking.
file:/path/to/mutex +
This selects the "best" available file locking implementation, + choosing between fcntl and flock, in that + order.

+ +

Most mechanisms are only available on selected platforms, where the + underlying platform and APR support it. Mechanisms + which aren't available on all platforms are posixsem, + sysvsem, sem, pthread, fcntl, + flock, and file.

+ +

With the file-based mechanisms fcntl and flock, + the path, if provided, is a directory where the lock file will be created. + The default directory is httpd's run-time file directory relative to + ServerRoot. Always use a local disk + filesystem for /path/to/mutex and never a directory residing + on a NFS- or AFS-filesystem. The basename of the file will be the mutex + type, an optional instance string provided by the module, and unless the + OmitPID keyword is specified, the process id of the httpd + parent process will be appended to to make the file name unique, avoiding + conflicts when multiple httpd instances share a lock file directory. For + example, if the mutex name is mpm-accept and the lock file + directory is /var/httpd/locks, the lock file name for the + httpd instance with parent process id 12345 would be + /var/httpd/locks/mpm-accept.12345.

+ +

Security

It is best to avoid putting mutex files in a world-writable + directory such as /var/tmp because someone could create + a denial of service attack and prevent the server from starting by + creating a lockfile with the same name as the one the server will try + to create.

+ +

The following table documents the names of mutexes used by httpd + and bundled modules.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Mutex name	Module(s)	Protected resource
`mpm-accept`	`prefork` and `worker` MPMs	incoming connections, to avoid the thundering herd problem; + for more information, refer to the + performance tuning + documentation
`authdigest-client`	`mod_auth_digest`	client list in shared memory
`authdigest-opaque`	`mod_auth_digest`	counter in shared memory
`ldap-cache`	`mod_ldap`	LDAP result cache
`rewrite-map`	`mod_rewrite`	communication with external mapping programs, to avoid + intermixed I/O from multiple requests
`ssl-cache`	`mod_ssl`	SSL session cache
`ssl-stapling`	`mod_ssl`	OCSP stapling response cache
`watchdog-callback`	`mod_watchdog`	callback function of a particular client module

+ +

The OmitPID keyword suppresses the addition of the httpd + parent process id from the lock file name.

+ +

In the following example, the mutex mechanism for the MPM accept + mutex will be changed from the compiled-in default to fcntl, + with the associated lock file created in directory + /var/httpd/locks. The mutex mechanism for all other mutexes + will be changed from the compiled-in default to sysvsem.

+ +

+ Mutex default sysvsem + Mutex mpm-accept fcntl:/var/httpd/locks +

+ +

NameVirtualHost Directiva

+ + + + + + +

Descripción:	Designates an IP address for name-virtual +hosting
Sintaxis:	`NameVirtualHost addr[:port]`
Contexto:	server config
Estado:	Core
Módulo:	core

+ +

A single NameVirtualHost directive +identifies a set of identical virtual hosts on which the server will +further select from on the basis of the hostname +requested by the client. The NameVirtualHost +directive is a required directive if you want to configure +name-based virtual hosts.

+ +

This directive, and the corresponding VirtualHost, +must be qualified with a port number if the server supports both HTTP +and HTTPS connections.

+ +

Although addr can be a hostname, it is recommended +that you always use an IP address or a wildcard. A wildcard +NameVirtualHost matches only virtualhosts that also have a literal wildcard +as their argument.

+ +

In cases where a firewall or other proxy receives the requests and +forwards them on a different IP address to the server, you must specify the +IP address of the physical interface on the machine which will be +servicing the requests.

+ +

In the example below, requests received on interface 192.0.2.1 and port 80 +will only select among the first two virtual hosts. Requests received on +port 80 on any other interface will only select among the third and fourth +virtual hosts. In the common case where the interface isn't important +to the mapping, only the "*:80" NameVirtualHost and VirtualHost directives +are necessary.

+ +

+ NameVirtualHost 192.0.2.1:80 + NameVirtualHost *:80 + + <VirtualHost 192.0.2.1:80> + ServerName namebased-a.example.com + </VirtualHost> + + <VirtualHost 192.0.2.1:80> + Servername namebased-b.example.com + </VirtualHost> + + <VirtualHost *:80> + ServerName namebased-c.example.com + </VirtualHost> + + <VirtualHost *:80> + ServerName namebased-d.example.com + </VirtualHost> + + +

+ +

If no matching virtual host is found, then the first listed + virtual host that matches the IP address and port will be used.

+ + +

IPv6 addresses must be enclosed in square brackets, as shown + in the following example:

+ +

+ NameVirtualHost [2001:db8::a00:20ff:fea7:ccea]:8080 +

+ +

Argument to `<VirtualHost>` + directive

Note that the argument to the <VirtualHost> directive must + exactly match the argument to the NameVirtualHost directive.

+ +

+ NameVirtualHost 192.0.2.2:80 + <VirtualHost 192.0.2.2:80> + # ... + </VirtualHost> +

+ +

Consulte también

Virtual Hosts +documentation

Options Directiva

+ + + + + + + + +

Descripción:	Configures what features are available in a particular +directory
Sintaxis:	`Options + [+\|-]option [[+\|-]option] ...`
Valor por defecto:	`Options All`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	Options
Estado:	Core
Módulo:	core

The Options directive controls which + server features are available in a particular directory.

+ +

option can be set to None, in which + case none of the extra features are enabled, or one or more of + the following:

+ +

All: All options except for MultiViews. This is the default + setting.
ExecCGI: + Execution of CGI scripts using mod_cgi + is permitted.
FollowSymLinks: + + The server will follow symbolic links in this directory. +
+
Even though the server follows the symlink it does not + change the pathname used to match against <Directory> sections.
+
Note also, that this option gets ignored if set + inside a <Location> + section.
+
Omitting this option should not be considered a security restriction, + since symlink testing is subject to race conditions that make it + circumventable.
+
Includes: + Server-side includes provided by mod_include + are permitted.
IncludesNOEXEC: + + Server-side includes are permitted, but the #exec + cmd and #exec cgi are disabled. It is still + possible to #include virtual CGI scripts from + ScriptAliased + directories.
Indexes: + If a URL which maps to a directory is requested, and there + is no DirectoryIndex + (e.g., index.html) in that directory, then + mod_autoindex will return a formatted listing + of the directory.
MultiViews: + Content negotiated + "MultiViews" are allowed using + mod_negotiation. +
Note

This option gets ignored if set + anywhere other than <Directory>, as mod_negotiation + needs real resources to compare against and evaluate from.
+
SymLinksIfOwnerMatch: The server will only follow symbolic links for which the + target file or directory is owned by the same user id as the + link. + +
Note

This option gets ignored if + set inside a <Location> section.
+
This option should not be considered a security restriction, + since symlink testing is subject to race conditions that make it + circumventable.
+

+ +

Normally, if multiple Options could + apply to a directory, then the most specific one is used and + others are ignored; the options are not merged. (See how sections are merged.) + However if all the options on the + Options directive are preceded by a + + or - symbol, the options are + merged. Any options preceded by a + are added to the + options currently in force, and any options preceded by a + - are removed from the options currently in + force.

+ +

Warning

Mixing Options with a + or + - with those without is not valid syntax, and is likely + to cause unexpected results.

+ +

For example, without any + and - symbols:

+ +

+ <Directory /web/docs> + + Options Indexes FollowSymLinks + + </Directory> + + <Directory /web/docs/spec> + + Options Includes + + </Directory> +

+ +

then only Includes will be set for the + /web/docs/spec directory. However if the second + Options directive uses the + and + - symbols:

+ +

+ <Directory /web/docs> + + Options Indexes FollowSymLinks + + </Directory> + + <Directory /web/docs/spec> + + Options +Includes -Indexes + + </Directory> +

+ +

then the options FollowSymLinks and + Includes are set for the /web/docs/spec + directory.

+ +

Note

Using -IncludesNOEXEC or + -Includes disables server-side includes completely + regardless of the previous setting.

+ +

The default in the absence of any other settings is + All.

+ +

Protocol Directiva

+ + + + + + + +

Descripción:	Protocol for a listening socket
Sintaxis:	`Protocol protocol`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache 2.1.5 and later. +On Windows from Apache 2.3.3 and later.

This directive specifies the protocol used for a specific listening socket. + The protocol is used to determine which module should handle a request, and + to apply protocol specific optimizations with the AcceptFilter + directive.

+ +

You only need to set the protocol if you are running on non-standard ports, otherwise http is assumed for port 80 and https for port 443.

+ +

For example, if you are running https on a non-standard port, specify the protocol explicitly:

+ +

+ Protocol https +

+ +

You can also specify the protocol using the Listen directive.

+ +

Consulte también

AcceptFilter
Listen

Protocols Directiva

+ + + + + + + + +

Descripción:	Protocols available for a server/virtual host
Sintaxis:	`Protocols protocol ...`
Valor por defecto:	`Protocols http/1.1`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Only available from Apache 2.4.17 and later.

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

Consulte también

ProtocolsHonorOrder

ProtocolsHonorOrder Directiva

+ + + + + + + + +

Descripción:	Determines if order of Protocols determines precedence during negotiation
Sintaxis:	`ProtocolsHonorOrder On\|Off`
Valor por defecto:	`ProtocolsHonorOrder On`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core
Compatibilidad:	Only available from Apache 2.4.17 and later.

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

Consulte también

Protocols

QualifyRedirectURL Directiva

+ + + + + + + + + +

Descripción:	Controls whether the REDIRECT_URL environment variable is + fully qualified
Sintaxis:	`QualifyRedirectURL ON\|OFF`
Valor por defecto:	`QualifyRedirectURL OFF`
Contexto:	server config, virtual host, directory
Anula:	FileInfo
Estado:	Core
Módulo:	core
Compatibilidad:	Directive supported in 2.4.18 and later. 2.4.17 acted +as if 'QualifyRedirectURL ON' was configured.

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

RegisterHttpMethod Directiva

+ + + + + + +

Descripción:	Register non-standard HTTP methods
Sintaxis:	`RegisterHttpMethod method [method [...]]`
Contexto:	server config
Estado:	Core
Módulo:	core

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

RLimitCPU Directiva

+ + + + + + + + +

Descripción:	Limits the CPU consumption of processes launched +by Apache httpd children
Sintaxis:	`RLimitCPU seconds\|max [seconds\|max]`
Valor por defecto:	`Unset; uses operating system defaults`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

Takes 1 or 2 parameters. The first parameter sets the soft + resource limit for all processes and the second parameter sets + the maximum resource limit. Either parameter can be a number, + or max to indicate to the server that the limit should + be set to the maximum allowed by the operating system + configuration. Raising the maximum resource limit requires that + the server is running as root, or in the initial startup + phase.

+ +

This applies to processes forked off from Apache httpd children + servicing requests, not the Apache httpd children themselves. This + includes CGI scripts and SSI exec commands, but not any + processes forked off from the Apache httpd parent such as piped + logs.

+ +

CPU resource limits are expressed in seconds per + process.

+ +

Consulte también

RLimitMEM
RLimitNPROC

RLimitMEM Directiva

+ + + + + + + + +

Descripción:	Limits the memory consumption of processes launched +by Apache httpd children
Sintaxis:	`RLimitMEM bytes\|max [bytes\|max]`
Valor por defecto:	`Unset; uses operating system defaults`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

+ +

Memory resource limits are expressed in bytes per + process.

+ +

Consulte también

RLimitCPU
RLimitNPROC

RLimitNPROC Directiva

+ + + + + + + + +

Descripción:	Limits the number of processes that can be launched by +processes launched by Apache httpd children
Sintaxis:	`RLimitNPROC number\|max [number\|max]`
Valor por defecto:	`Unset; uses operating system defaults`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

Takes 1 or 2 parameters. The first parameter sets the soft + resource limit for all processes and the second parameter sets + the maximum resource limit. Either parameter can be a number, + or max to indicate to the server that the limit + should be set to the maximum allowed by the operating system + configuration. Raising the maximum resource limit requires that + the server is running as root, or in the initial startup + phase.

+ +

Process limits control the number of processes per user.

+ +

Note

If CGI processes are not running + under user ids other than the web server user id, this directive + will limit the number of processes that the server itself can + create. Evidence of this situation will be indicated by + cannot fork messages in the + error_log.

+ +

Consulte también

RLimitMEM
RLimitCPU

ScriptInterpreterSource Directiva

+ + + + + + + + + +

Descripción:	Technique for locating the interpreter for CGI +scripts
Sintaxis:	`ScriptInterpreterSource Registry\|Registry-Strict\|Script`
Valor por defecto:	`ScriptInterpreterSource Script`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core
Compatibilidad:	Win32 only; +option `Registry-Strict` is available in Apache HTTP Server 2.0 and +later

This directive is used to control how Apache httpd finds the + interpreter used to run CGI scripts. The default setting is + Script. This causes Apache httpd to use the interpreter pointed to + by the shebang line (first line, starting with #!) in the + script. On Win32 systems this line usually looks like:

+ +

+ #!C:/Perl/bin/perl.exe +

+ +

or, if perl is in the PATH, simply:

+ +

+ #!perl +

+ +

Setting ScriptInterpreterSource Registry will + cause the Windows Registry tree HKEY_CLASSES_ROOT to be + searched using the script file extension (e.g., .pl) as a + search key. The command defined by the registry subkey + Shell\ExecCGI\Command or, if it does not exist, by the subkey + Shell\Open\Command is used to open the script file. If the + registry keys cannot be found, Apache httpd falls back to the behavior of the + Script option.

+ +

Security

Be careful when using ScriptInterpreterSource + Registry with ScriptAlias'ed directories, because + Apache httpd will try to execute every file within this + directory. The Registry setting may cause undesired + program calls on files which are typically not executed. For + example, the default open command on .htm files on + most Windows systems will execute Microsoft Internet Explorer, so + any HTTP request for an .htm file existing within the + script directory would start the browser in the background on the + server. This is a good way to crash your system within a minute or + so.

+ +

The option Registry-Strict which is new in Apache HTTP Server + 2.0 does the same thing as Registry but uses only the + subkey Shell\ExecCGI\Command. The + ExecCGI key is not a common one. It must be + configured manually in the windows registry and hence prevents + accidental program calls on your system.

+ +

SeeRequestTail Directiva

+ + + + + + + + +

Descripción:	Determine if mod_status displays the first 63 characters +of a request or the last 63, assuming the request itself is greater than +63 chars.
Sintaxis:	`SeeRequestTail On\|Off`
Valor por defecto:	`SeeRequestTail Off`
Contexto:	server config
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache httpd 2.2.7 and later.

mod_status with ExtendedStatus On + displays the actual request being handled. + For historical purposes, only 63 characters of the request + are actually stored for display purposes. This directive + controls whether the 1st 63 characters are stored (the previous + behavior and the default) or if the last 63 characters are. This + is only applicable, of course, if the length of the request is + 64 characters or greater.

+ +

If Apache httpd is handling GET /disk1/storage/apache/htdocs/images/imagestore1/food/apples.jpg HTTP/1.1 mod_status displays as follows: +

+ + + + + + + + + + +

Off (default)	GET /disk1/storage/apache/htdocs/images/imagestore1/food/apples
On	orage/apache/htdocs/images/imagestore1/food/apples.jpg HTTP/1.1

+ + +

ServerAdmin Directiva

+ + + + + + +

Descripción:	Email address that the server includes in error +messages sent to the client
Sintaxis:	`ServerAdmin email-address\|URL`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

The ServerAdmin sets the contact address + that the server includes in any error messages it returns to the + client. If the httpd doesn't recognize the supplied argument + as an URL, it + assumes, that it's an email-address and prepends it with + mailto: in hyperlink targets. However, it's recommended to + actually use an email address, since there are a lot of CGI scripts that + make that assumption. If you want to use an URL, it should point to another + server under your control. Otherwise users may not be able to contact you in + case of errors.

+ +

It may be worth setting up a dedicated address for this, e.g.

+ +

+ ServerAdmin www-admin@foo.example.com +

as users do not always mention that they are talking about the + server!

+ +

ServerAlias Directiva

+ + + + + + +

Descripción:	Alternate names for a host used when matching requests +to name-virtual hosts
Sintaxis:	`ServerAlias hostname [hostname] ...`
Contexto:	virtual host
Estado:	Core
Módulo:	core

The ServerAlias directive sets the + alternate names for a host, for use with name-based virtual hosts. The + ServerAlias may include wildcards, if appropriate.

+ +

+ <VirtualHost *:80> + ServerName server.domain.com + ServerAlias server server2.domain.com server2 + ServerAlias *.example.com + UseCanonicalName Off + # ... + </VirtualHost> +

+ +

Consulte también

ServerName Directiva

+ + + + + + +

Descripción:	Hostname and port that the server uses to identify +itself
Sintaxis:	`ServerName [scheme://]fully-qualified-domain-name[:port]`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

The ServerName directive sets the + request scheme, hostname and + port that the server uses to identify itself. This is used when + creating redirection URLs.

+ +

Additionally, ServerName is used (possibly + in conjunction with ServerAlias) to uniquely + identify a virtual host, when using name-based virtual hosts.

+ +

For example, if the name of the + machine hosting the web server is simple.example.com, + but the machine also has the DNS alias www.example.com + and you wish the web server to be so identified, the following + directive should be used:

+ +

+ ServerName www.example.com:80 +

+ +

The ServerName directive + may appear anywhere within the definition of a server. However, + each appearance overrides the previous appearance (within that + server).

+ +

If no ServerName is specified, then the + server attempts to deduce the hostname by performing a reverse + lookup on the IP address. If no port is specified in the + ServerName, then the server will use the + port from the incoming request. For optimal reliability and + predictability, you should specify an explicit hostname and port + using the ServerName directive.

+ +

If you are using name-based virtual hosts, + the ServerName inside a + <VirtualHost> + section specifies what hostname must appear in the request's + Host: header to match this virtual host.

+ +

Sometimes, the server runs behind a device that processes SSL, + such as a reverse proxy, load balancer or SSL offload + appliance. When this is the case, specify the + https:// scheme and the port number to which the + clients connect in the ServerName directive + to make sure that the server generates the correct + self-referential URLs. +

+ +

See the description of the + UseCanonicalName and + UseCanonicalPhysicalPort directives for + settings which determine whether self-referential URLs (e.g., by the + mod_dir module) will refer to the + specified port, or to the port number given in the client's request. +

+ +

Failure to set ServerName to a name that + your server can resolve to an IP address will result in a startup + warning. httpd will then use whatever hostname it can + determine, using the system's hostname command. This + will almost never be the hostname you actually want.

+ httpd: Could not reliably determine the server's fully qualified domain name, using rocinante.local for ServerName +

+ + +

Consulte también

ServerPath Directiva

+ + + + + + +

Descripción:	Legacy URL pathname for a name-based virtual host that +is accessed by an incompatible browser
Sintaxis:	`ServerPath URL-path`
Contexto:	virtual host
Estado:	Core
Módulo:	core

The ServerPath directive sets the legacy + URL pathname for a host, for use with name-based virtual hosts.

+ +

Consulte también

Apache HTTP Server Virtual Host documentation

ServerRoot Directiva

+ + + + + + + +

Descripción:	Base directory for the server installation
Sintaxis:	`ServerRoot directory-path`
Valor por defecto:	`ServerRoot /usr/local/apache`
Contexto:	server config
Estado:	Core
Módulo:	core

The ServerRoot directive sets the + directory in which the server lives. Typically it will contain the + subdirectories conf/ and logs/. Relative + paths in other configuration directives (such as Include or LoadModule, for example) are taken as + relative to this directory.

+ +

Example

+ ServerRoot /home/httpd +

+ + +

Consulte también

the -d + option to httpd
the + security tips for information on how to properly set + permissions on the ServerRoot

ServerSignature Directiva

+ + + + + + + + +

Descripción:	Configures the footer on server-generated documents
Sintaxis:	`ServerSignature On\|Off\|EMail`
Valor por defecto:	`ServerSignature Off`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	All
Estado:	Core
Módulo:	core

The ServerSignature directive allows the + configuration of a trailing footer line under server-generated + documents (error messages, mod_proxy ftp directory + listings, mod_info output, ...). The reason why you + would want to enable such a footer line is that in a chain of proxies, + the user often has no possibility to tell which of the chained servers + actually produced a returned error message.

+ +

The Off + setting, which is the default, suppresses the footer line (and is + therefore compatible with the behavior of Apache-1.2 and + below). The On setting simply adds a line with the + server version number and ServerName of the serving virtual host, + and the EMail setting additionally creates a + "mailto:" reference to the ServerAdmin of the referenced + document.

+ +

After version 2.0.44, the details of the server version number + presented are controlled by the ServerTokens directive.

+ +

Consulte también

ServerTokens

ServerTokens Directiva

+ + + + + + + +

Descripción:	Configures the `Server` HTTP response +header
Sintaxis:	`ServerTokens Major\|Minor\|Min[imal]\|Prod[uctOnly]\|OS\|Full`
Valor por defecto:	`ServerTokens Full`
Contexto:	server config
Estado:	Core
Módulo:	core

This directive controls whether Server response + header field which is sent back to clients includes a + description of the generic OS-type of the server as well as + information about compiled-in modules.

+ +

ServerTokens Full (or not specified): Server sends (e.g.): Server: Apache/2.4.1 + (Unix) PHP/4.2.2 MyMod/1.2
ServerTokens Prod[uctOnly]: Server sends (e.g.): Server: + Apache
ServerTokens Major: Server sends (e.g.): Server: + Apache/2
ServerTokens Minor: Server sends (e.g.): Server: + Apache/2.4
ServerTokens Min[imal]: Server sends (e.g.): Server: + Apache/2.4.1
ServerTokens OS: Server sends (e.g.): Server: Apache/2.4.1 + (Unix)

+ +

This setting applies to the entire server, and cannot be + enabled or disabled on a virtualhost-by-virtualhost basis.

+ +

After version 2.0.44, this directive also controls the + information presented by the ServerSignature directive.

+ +

Setting ServerTokens to less than + minimal is not recommended because it makes it more + difficult to debug interoperational problems. Also note that + disabling the Server: header does nothing at all to make your + server more secure; the idea of "security through obscurity" + is a myth and leads to a false sense of safety.

+ + +

Consulte también

ServerSignature

SetHandler Directiva

+ + + + + + + + +

Descripción:	Forces all matching files to be processed by a +handler
Sintaxis:	`SetHandler handler-name\|None`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core
Compatibilidad:	Moved into the core in Apache httpd 2.0

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 + handler-name. 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 httpd.conf:

+ +

+ <Location /status> + + SetHandler server-status + + </Location> +

+ +

You can override an earlier defined SetHandler + directive by using the value None.

Note: because SetHandler overrides default handlers, + normal behaviour such as handling of URLs ending in a slash (/) as + directories or index files is suppressed.

+ +

Consulte también

AddHandler

SetInputFilter Directiva

+ + + + + + + +

Descripción:	Sets the filters that will process client requests and POST +input
Sintaxis:	`SetInputFilter filter[;filter...]`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core

The SetInputFilter directive sets the + filter or filters which will process client requests and POST + input when they are received by the server. This is in addition to + any filters defined elsewhere, including the + AddInputFilter + directive.

+ +

If more than one filter is specified, they must be separated + by semicolons in the order in which they should process the + content.

+ +

Consulte también

Filters documentation

SetOutputFilter Directiva

+ + + + + + + +

Descripción:	Sets the filters that will process responses from the +server
Sintaxis:	`SetOutputFilter filter[;filter...]`
Contexto:	server config, virtual host, directory, .htaccess
Anula:	FileInfo
Estado:	Core
Módulo:	core

The SetOutputFilter directive sets the filters + which will process responses from the server before they are + sent to the client. This is in addition to any filters defined + elsewhere, including the + AddOutputFilter + directive.

+ +

For example, the following configuration will process all files + in the /www/data/ directory for server-side + includes.

+ +

+ <Directory /www/data/> + + SetOutputFilter INCLUDES + + </Directory> +

+ +

If more than one filter is specified, they must be separated + by semicolons in the order in which they should process the + content.

+ +

Consulte también

Filters documentation

TimeOut Directiva

+ + + + + + + +

Descripción:	Amount of time the server will wait for +certain events before failing a request
Sintaxis:	`TimeOut seconds`
Valor por defecto:	`TimeOut 60`
Contexto:	server config, virtual host
Estado:	Core
Módulo:	core

The TimeOut directive defines the length + of time Apache httpd will wait for I/O in various circumstances:

+ +

When reading data from the client, the length of time to + wait for a TCP packet to arrive if the read buffer is + empty.
When writing data to the client, the length of time to wait + for an acknowledgement of a packet if the send buffer is + full.
In mod_cgi, the length of time to wait for + output from a CGI script.
In mod_ext_filter, the length of time to + wait for output from a filtering process.
In mod_proxy, the default timeout value if + ProxyTimeout is not + configured.

+ + +

TraceEnable Directiva

+ + + + + + + + +

Descripción:	Determines the behaviour on `TRACE` requests
Sintaxis:	`TraceEnable [on\|off\|extended]`
Valor por defecto:	`TraceEnable on`
Contexto:	server config
Estado:	Core
Módulo:	core
Compatibilidad:	Available in Apache HTTP Server 1.3.34, 2.0.55 and later

This directive overrides the behavior of TRACE for both + the core server and mod_proxy. The default + TraceEnable on permits TRACE requests per + RFC 2616, which disallows any request body to accompany the request. + TraceEnable off causes the core server and + mod_proxy to return a 405 (Method not + allowed) error to the client.

+ +

Finally, for testing and diagnostic purposes only, request + bodies may be allowed using the non-compliant TraceEnable + extended directive. The core (as an origin server) will + restrict the request body to 64k (plus 8k for chunk headers if + Transfer-Encoding: chunked is used). The core will + reflect the full headers and all chunk headers with the response + body. As a proxy server, the request body is not restricted to 64k.

+ +

UnDefine Directiva

+ + + + + + +

Descripción:	Undefine the existence of a variable
Sintaxis:	`UnDefine parameter-name`
Contexto:	server config
Estado:	Core
Módulo:	core

Undoes the effect of a Define or + of passing a -D argument to httpd.

This directive can be used to toggle the use of <IfDefine> sections without needing to alter + -D arguments in any startup scripts.

+ +

UseCanonicalName Directiva

+ + + + + + + +

Descripción:	Configures how the server determines its own name and +port
Sintaxis:	`UseCanonicalName On\|Off\|DNS`
Valor por defecto:	`UseCanonicalName Off`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core

In many situations Apache httpd must construct a self-referential + URL -- that is, a URL that refers back to the same server. With + UseCanonicalName On Apache httpd will use the hostname and port + specified in the ServerName + directive to construct the canonical name for the server. This name + is used in all self-referential URLs, and for the values of + SERVER_NAME and SERVER_PORT in CGIs.

+ +

With UseCanonicalName Off Apache httpd will form + self-referential URLs using the hostname and port supplied by + the client if any are supplied (otherwise it will use the + canonical name, as defined above). These values are the same + that are used to implement name-based virtual hosts, + and are available with the same clients. The CGI variables + SERVER_NAME and SERVER_PORT will be + constructed from the client supplied values as well.

+ +

An example where this may be useful is on an intranet server + where you have users connecting to the machine using short + names such as www. You'll notice that if the users + type a shortname, and a URL which is a directory, such as + http://www/splat, without the trailing + slash then Apache httpd will redirect them to + http://www.domain.com/splat/. If you have + authentication enabled, this will cause the user to have to + authenticate twice (once for www and once again + for www.domain.com -- see the + FAQ on this subject for more information). But if + UseCanonicalName is set Off, then + Apache httpd will redirect to http://www/splat/.

+ +

There is a third option, UseCanonicalName DNS, + which is intended for use with mass IP-based virtual hosting to + support ancient clients that do not provide a + Host: header. With this option Apache httpd does a + reverse DNS lookup on the server IP address that the client + connected to in order to work out self-referential URLs.

+ +

Warning

If CGIs make assumptions about the values of SERVER_NAME + they may be broken by this option. The client is essentially free + to give whatever value they want as a hostname. But if the CGI is + only using SERVER_NAME to construct self-referential URLs + then it should be just fine.

+ +

Consulte también

UseCanonicalPhysicalPort
ServerName
Listen

UseCanonicalPhysicalPort Directiva

+ + + + + + + +

Descripción:	Configures how the server determines its own name and +port
Sintaxis:	`UseCanonicalPhysicalPort On\|Off`
Valor por defecto:	`UseCanonicalPhysicalPort Off`
Contexto:	server config, virtual host, directory
Estado:	Core
Módulo:	core

In many situations Apache httpd must construct a self-referential + URL -- that is, a URL that refers back to the same server. With + UseCanonicalPhysicalPort On Apache httpd will, when + constructing the canonical port for the server to honor + the UseCanonicalName directive, + provide the actual physical port number being used by this request + as a potential port. With UseCanonicalPhysicalPort Off + Apache httpd will not ever use the actual physical port number, instead + relying on all configured information to construct a valid port number.

+ +

Note

The ordering of when the physical port is used is as follows:

+ UseCanonicalName On

Port provided in Servername
Physical port
Default port

+ UseCanonicalName Off | DNS +

Parsed port from Host: header
Physical port
Port provided in Servername
Default port

+ +

With UseCanonicalPhysicalPort Off, the + physical ports are removed from the ordering.

+ + +

Consulte también

UseCanonicalName
ServerName
Listen

<VirtualHost> Directiva

+ + + + + + +

Descripción:	Contains directives that apply only to a specific +hostname or IP address
Sintaxis:	`<VirtualHost + addr[:port] [addr[:port]] + ...> ... </VirtualHost>`
Contexto:	server config
Estado:	Core
Módulo:	core

<VirtualHost> and + </VirtualHost> are used to enclose a group of + directives that will apply only to a particular virtual host. Any + directive that is allowed in a virtual host context may be + used. When the server receives a request for a document on a + particular virtual host, it uses the configuration directives + enclosed in the <VirtualHost> + section. Addr can be:

+ +

The IP address of the virtual host;
A fully qualified domain name for the IP address of the + virtual host (not recommended);
The character *, which is used only in combination with + NameVirtualHost * to match all IP addresses; or
The string _default_, which is used only + with IP virtual hosting to catch unmatched IP addresses.

+ +

Example

+ <VirtualHost 10.1.2.3> + + ServerAdmin webmaster@host.example.com + DocumentRoot /www/docs/host.example.com + ServerName host.example.com + ErrorLog logs/host.example.com-error_log + TransferLog logs/host.example.com-access_log + + </VirtualHost> +

+ + +

IPv6 addresses must be specified in square brackets because + the optional port number could not be determined otherwise. An + IPv6 example is shown below:

+ +

+ <VirtualHost [2001:db8::a00:20ff:fea7:ccea]> + + ServerAdmin webmaster@host.example.com + DocumentRoot /www/docs/host.example.com + ServerName host.example.com + ErrorLog logs/host.example.com-error_log + TransferLog logs/host.example.com-access_log + + </VirtualHost> +

+ +

Each Virtual Host must correspond to a different IP address, + different port number or a different host name for the server, + in the former case the server machine must be configured to + accept IP packets for multiple addresses. (If the machine does + not have multiple network interfaces, then this can be + accomplished with the ifconfig alias command -- if + your OS supports it).

+ +

Note

The use of <VirtualHost> does + not affect what addresses Apache httpd listens on. You + may need to ensure that Apache httpd is listening on the correct addresses + using Listen.

+ +

When using IP-based virtual hosting, the special name + _default_ can be specified in + which case this virtual host will match any IP address that is + not explicitly listed in another virtual host. In the absence + of any _default_ virtual host the "main" server config, + consisting of all those definitions outside any VirtualHost + section, is used when no IP-match occurs.

+ +

You can specify a :port to change the port that is + matched. If unspecified then it defaults to the same port as the + most recent Listen + statement of the main server. You may also specify :* + to match all ports on that address. (This is recommended when used + with _default_.)

+ +

A ServerName should be + specified inside each <VirtualHost> block. If it is absent, the + ServerName from the "main" + server configuration will be inherited.

+ +

If no matching virtual host is found, then the first listed + virtual host that matches the IP address will be used. As a + consequence, the first listed virtual host is the default virtual + host.

+ +

Security

See the security tips + document for details on why your security could be compromised if the + directory where log files are stored is writable by anyone other + than the user that starts the server.

+ +

Consulte también

Apache HTTP Server Virtual Host documentation
Issues Regarding DNS and + Apache HTTP Server
Setting + which addresses and ports Apache HTTP Server uses
How <Directory>, <Location> + and <Files> sections work for an explanation of how these + different sections are combined when a request is received

Warning Directiva

+ + + + + + + +

Descripción:	Warn from configuration parsing with a custom message
Sintaxis:	`Warning message`
Contexto:	server config, virtual host, directory, .htaccess
Estado:	Core
Módulo:	core
Compatibilidad:	2.5 and later

The documentation for this directive has + not been translated yet. Please have a look at the English + version.

Idiomas disponibles: de | + en | + es | + fr | + ja | + tr

Comentarios

- \ No newline at end of file +//--> + diff --git a/docs/manual/new_features_2_2.xml.es b/docs/manual/new_features_2_2.xml.es index a2e137d23e..9f3127408d 100644 --- a/docs/manual/new_features_2_2.xml.es +++ b/docs/manual/new_features_2_2.xml.es @@ -1,287 +1,287 @@ - - - - - - - - - - -InformaciÃ³n General sobre las Nuevas CaracterÃsticas en Apache HTTP Server 2.2 - -

Este documento describe algunos de los principales cambios entre las versiones 2.0 y - 2.2 del Servidor Apache HTTP. Para las nuevas caracterÃsticas desde la versiÃ³n 1.3, - consulte 2.0 nuevas caracterÃsticas. -

- -

- Mejoras principales -

AutenticaciÃ³n y AutorizaciÃ³n: El paquete de los mÃ³dulos de autenticaciÃ³n y autorizaciÃ³n se han - refactorizado. El nuevo mÃ³dulo mod_authn_alias (eliminados en las - versiones 2.3/2.4) puede simplificar de gran forma algunas configuraciones - de autenticaciÃ³n. Vea tambiÃ©n el cambio de nombres de - los mÃ³dulos, y los cambios para desarrolladores - para mÃ¡s informaciÃ³n sobre los cambios de como afectan a los usuarios, - y a los que desarrollan mÃ³dulos. -
CachÃ©: mod_cache, mod_cache_disk, y - mod_mem_cache (eliminados en las versiones 2.3/2.4) han sufrido muchos - cambios, y ahora se consideran en calidad de producciÃ³n. - El programa htcacheclean se ha introducido - para limpiar los setups de mod_cache_disk. -
ConfiguraciÃ³n: La capa de la configuraciÃ³n por defecto, se ha simplificado y - modularizado. Se pueden utilizar fragmentos de configuraciÃ³n para - habilitar las funciones de uso comÃºn que ahora se incluyen con Apache, - y pueden ser fÃ¡cilmente aÃ±adidos a la configuraciÃ³n del servidor - principal.
DetenciÃ³n con elegancia: Los mÃ³dulos prefork, worker y - event MPMs(mÃ³dulos de procesos mÃºltiples) ahora - permiten a httpd ser apagado/parado con elegancia - mediante la seÃ±al - graceful-stop. - La directiva GracefulShutdownTimeout se ha aÃ±adidos - para especificar un tiempo opcional, tras el cual el - httpd se pararÃ¡ independientemente del estado de - cualquier peticiÃ³n que se estÃ© sirviendo.
Funcionalidad del Proxy: El nuevo mÃ³dulo mod_proxy_balancer proporciona un - servicio de balanceo de carga para el mÃ³dulo mod_proxy. - El nuevo mÃ³dulo mod_proxy_ajp aÃ±ade soporte para el - Protocolo JServ versiÃ³n 1.3 de Apache usado por - Apache Tomcat.
ActualizaciÃ³n de la LibrerÃa de Expresiones Regulares: Se ha incluido la versiÃ³n 5.0 de - LibrerÃa de Expresiones Regulares - Compatibles Perl (PCRE). El programa httpd - puede ser configurado para que use una instalaciÃ³n en el sistema - de PCRE pasandole como parÃ¡metro --with-pcre - al configure.
Filtrado Inteligente: mod_filter introduce una configuraciÃ³n dinÃ¡mica - a la cadena de filtro de salida. Habilita que los filtros sean insertados - de forma condicional, basado en cualquier cabecera de peticiÃ³n o respuesta - o una variable de entorno, y prescinde de las dependencias mÃ¡s problemÃ¡ticas - asÃ como problemas de ordenaciÃ³n en la arquitectura 2.0.
Soporte de Grandes Ficheros: httpd es creado ahora con soporte para ficheros - mayores de 2GB en los sistemas Unix modernos de 32-bits. TambiÃ©n el soporte - para el manejo de cuerpos de respuesta >2GB ha sido aÃ±adido.
Eventos MPM: El mÃ³dulo event MPM usa un hilo separado para el manejo - de las peticiones Keep Alive y aceptar las conexiones. Las peticiones de - Keep Alive tradicionalmente han requerido un "worker" de httpd para su manejo. - Este "worker" dedicado no puede ser utilizado otra vez hasta que el Keep Alive - haya expirado su tiempo de conexiÃ³n. -
Soporte de Base de Datos SQL: El mÃ³dulo mod_dbd, junto con el framework - apr_dbd, nos trae soporte directo de SQL para los mÃ³dulos - que lo necesitan. Es compatible con la agrupaciÃ³n de conexiones - en procesos MPM.

- -

- Mejoras en MÃ³dulos -

AutenticaciÃ³n y AutorizaciÃ³n: Los mÃ³dulos en el directorio aaa se han renombrado y ofrecen mejor - soporte para la autenticaciÃ³n implÃcita (digest). - Por ejemplo: - mod_auth se ha dividido ahora en - mod_auth_basic y - mod_authn_file; mod_auth_dbm ahora - se llama mod_authn_dbm; mod_access ha - sido renombrado a mod_authz_host. TambiÃ©n hay un nuevo - mÃ³dulo mod_authn_alias( ya eliminado en las versiones 2.3/2.4) para - simplificar algunas configuraciones de autenticaciÃ³n. -
mod_authnz_ldap: Este mÃ³dulo se ha traÃdo de la versiÃ³n 2.0 del mÃ³dulo - mod_auth_ldap a la versiÃ³n 2.2 del framework de - AutenticaciÃ³n/AutorizaciÃ³n. Las nuevas caracterÃsticas - incluyen el uso de valores de LDAP y filtros de bÃºsqueda complejos - para la directiva - Require.
mod_authz_owner: Un nuevo mÃ³dulo que autoriza el acceso a ficheros basÃ¡ndose en el - propietario del fichero en el sistema operativo. -
mod_version: Este nuevo mÃ³dulo permite que se habiliten bloques de configuraciÃ³n - dependiendo de la versiÃ³n del servidor. -
mod_info: Se ha aÃ±adido un nuevo argumento al config que muestra - las configuraciones de las directivas que se le pasan a Apache, incluyendo - los nombres de los ficheros y en que linea se encuentra dicha configuraciÃ³n. - Este mÃ³dulo ademÃ¡s muestra en orden todas las peticiones de hooks y informaciÃ³n - adicional a la hora de compilar, similar a httpd -V.
mod_ssl: Se ha aÃ±adido soporte para el - RFC 2817, que permite - conexiones para que se actualicen de texto plano al cifrado TLS.
mod_imagemap: mod_imap Se ha renombrado a - mod_imagemap para evitar confusiÃ³n en el usuario. -

- -

- Mejoras de Programas -

httpd: Se ha aÃ±adido una nueva opciÃ³n en la lÃnea de comandos -M, - dicha opciÃ³n lista todos los mÃ³dulos que se cargan basÃ¡ndose en la - configuraciÃ³n actual. A diferencia de la opciÃ³n -l, esta lista - incluye los DSOs cargados mediante el mÃ³dulomod_so. -
httxt2dbm: Un nuevo programa para generar archivos dbm desde archivos de texto - como entrada, para su uso en - RewriteMap - con el mapa de tipo dbm.

- -

- Cambios para desarrolladores de MÃ³dulos -

APR 1.0 API

Apache 2.2 usa la API de APR. Todas las funciones y sÃmbolos obsoletas - se han eliminado de APR y - APR-Util. Para mas detalles sobre dichos cambios - vaya a la - pÃ¡gina de APR.

AutenticaciÃ³n y AutorizaciÃ³n

El paquete de mÃ³dulos de autenticaciÃ³n y autorizaciÃ³n se han renombrado - como se muestra en las siguientes lÃneas: -

mod_auth_* -> MÃ³dulos que implementan un mecanismo de - autenticaciÃ³n por HTTP.
mod_authn_* -> MÃ³dulos que proporcionan un backend - proveedor de autenticaciÃ³n.
mod_authz_* -> MÃ³dulos que implementan autorizaciÃ³n - (o acceso)
mod_authnz_* -> MÃ³dulo que implementa ambas opciones - autenticaciÃ³n & autorizaciÃ³n

- Hay un nuevo esquema de proveedor de la autenticaciÃ³n en el backend - lo que facilita en gran medida la construcciÃ³n de nuevos motores - de autenticaciÃ³n. -

Registro de errores de ConexiÃ³n

Una nueva funciÃ³n ap_log_cerror ha sido aÃ±adida para - registrar los errores que ocurren en la conexiÃ³n del cliente. Cuando se - registra el error, el mensaje incluye la direcciÃ³n IP del cliente.

AÃ±adido Hooks para la configuraciÃ³n de Test

Un nuevo hook, test_config se ha aÃ±adido para ayudar a - los mÃ³dulos que necesitan ejecutar sÃ³lo cÃ³digo especial cuando el usuario - pasa como parÃ¡metro -t a httpd.

ConfiguraciÃ³n de tamaÃ±o de pila para los procesos MPM's

Una nueva directiva, ThreadStackSize se ha aÃ±adido para configurar - el tamaÃ±o de la pila de todos los hilos de MPMs. Esta directiva - es requerida por algÃºn mÃ³dulo de terceros en plataformas que tienen - por defecto una pila con un tamaÃ±o pequeÃ±o.

Manejo de protocolo para los filtros de salida

En el pasado, cada filtro ha sido responsable de garantizar - que genera las cabeceras de respuesta correctas donde les afecta. - Los filtros ahora delegan la administraciÃ³n comÃºn del protocolo - a los mÃ³dulos - mod_filter, usando llamadas a - ap_register_output_filter_protocol Ã³ - ap_filter_protocol.

Monitor de hooks aÃ±adido

Monitor hook habilita a los mÃ³dulos a ejecutar tareas regulares - o programadas en el proceso padre (raÃz).

Cambio de expresiones regulares en la API

La cabecera pcreposix.h ya no esta disponible; - se ha cambiado por la nueva ap_regex.h. La - implementaciÃ³n POSIX.2 de regex.h expuesta por la cabecera - antigua, estÃ¡ ahora disponible en el espacio de nombre con ap_ - en la cabecera ap_regex.h. llama a regcomp, - regexec y asÃ sucesivamente pueden ser sustituidos por - llamadas a ap_regcomp, ap_regexec.

DBD Framework (API de base de datos SQL)

Con Apache 1.x y 2.0, algunos mÃ³dulos que requieren un - backend de SQL deben tomar la responsabilidad de gestionar por sÃ - mismos. Aparte de reinventar la rueda, esto puede llegar a ser - ineficiente, por ejemplo cuando varios mÃ³dulos cada uno mantiene su propia conexiÃ³n. -

- -

Las versiones de Apache posteriores a la 2.1 proporciona la API de ap_dbd - para el manejo de las conexiones a las bases de datos (incluyendo estrategia - optimizadas para los hilos o no de MPMs), mientras que las versiones de - APR 1.2 y posteriores proporciona la API apr_dbd para - interactuar con la base de datos.

- -

Los nuevos mÃ³dulos DEBEN usar estas APIs para todas las operaciones en - bases de datos SQL. Aplicaciones existentes DEBEN ser actualizadas para - que lo usen cuando sea posible, de forma transparente o como opciÃ³n recomendada - para sus usuarios.

+ + + + + + + + + + +InformaciÃ³n General sobre las Nuevas CaracterÃsticas en Apache HTTP Server 2.2 + +

Este documento describe algunos de los principales cambios entre las versiones 2.0 y + 2.2 del Servidor Apache HTTP. Para las nuevas caracterÃsticas desde la versiÃ³n 1.3, + consulte 2.0 nuevas caracterÃsticas. +

+ +

+ Mejoras principales +

AutenticaciÃ³n y AutorizaciÃ³n: El paquete de los mÃ³dulos de autenticaciÃ³n y autorizaciÃ³n se han + refactorizado. El nuevo mÃ³dulo mod_authn_alias (eliminados en las + versiones 2.3/2.4) puede simplificar de gran forma algunas configuraciones + de autenticaciÃ³n. Vea tambiÃ©n el cambio de nombres de + los mÃ³dulos, y los cambios para desarrolladores + para mÃ¡s informaciÃ³n sobre los cambios de como afectan a los usuarios, + y a los que desarrollan mÃ³dulos. +
CachÃ©: mod_cache, mod_cache_disk, y + mod_mem_cache (eliminados en las versiones 2.3/2.4) han sufrido muchos + cambios, y ahora se consideran en calidad de producciÃ³n. + El programa htcacheclean se ha introducido + para limpiar los setups de mod_cache_disk. +
ConfiguraciÃ³n: La capa de la configuraciÃ³n por defecto, se ha simplificado y + modularizado. Se pueden utilizar fragmentos de configuraciÃ³n para + habilitar las funciones de uso comÃºn que ahora se incluyen con Apache, + y pueden ser fÃ¡cilmente aÃ±adidos a la configuraciÃ³n del servidor + principal.
DetenciÃ³n con elegancia: Los mÃ³dulos prefork, worker y + event MPMs(mÃ³dulos de procesos mÃºltiples) ahora + permiten a httpd ser apagado/parado con elegancia + mediante la seÃ±al + graceful-stop. + La directiva GracefulShutdownTimeout se ha aÃ±adidos + para especificar un tiempo opcional, tras el cual el + httpd se pararÃ¡ independientemente del estado de + cualquier peticiÃ³n que se estÃ© sirviendo.
Funcionalidad del Proxy: El nuevo mÃ³dulo mod_proxy_balancer proporciona un + servicio de balanceo de carga para el mÃ³dulo mod_proxy. + El nuevo mÃ³dulo mod_proxy_ajp aÃ±ade soporte para el + Protocolo JServ versiÃ³n 1.3 de Apache usado por + Apache Tomcat.
ActualizaciÃ³n de la LibrerÃa de Expresiones Regulares: Se ha incluido la versiÃ³n 5.0 de + LibrerÃa de Expresiones Regulares + Compatibles Perl (PCRE). El programa httpd + puede ser configurado para que use una instalaciÃ³n en el sistema + de PCRE pasandole como parÃ¡metro --with-pcre + al configure.
Filtrado Inteligente: mod_filter introduce una configuraciÃ³n dinÃ¡mica + a la cadena de filtro de salida. Habilita que los filtros sean insertados + de forma condicional, basado en cualquier cabecera de peticiÃ³n o respuesta + o una variable de entorno, y prescinde de las dependencias mÃ¡s problemÃ¡ticas + asÃ como problemas de ordenaciÃ³n en la arquitectura 2.0.
Soporte de Grandes Ficheros: httpd es creado ahora con soporte para ficheros + mayores de 2GB en los sistemas Unix modernos de 32-bits. TambiÃ©n el soporte + para el manejo de cuerpos de respuesta >2GB ha sido aÃ±adido.
Eventos MPM: El mÃ³dulo event MPM usa un hilo separado para el manejo + de las peticiones Keep Alive y aceptar las conexiones. Las peticiones de + Keep Alive tradicionalmente han requerido un "worker" de httpd para su manejo. + Este "worker" dedicado no puede ser utilizado otra vez hasta que el Keep Alive + haya expirado su tiempo de conexiÃ³n. +
Soporte de Base de Datos SQL: El mÃ³dulo mod_dbd, junto con el framework + apr_dbd, nos trae soporte directo de SQL para los mÃ³dulos + que lo necesitan. Es compatible con la agrupaciÃ³n de conexiones + en procesos MPM.

+ +

+ Mejoras en MÃ³dulos +

AutenticaciÃ³n y AutorizaciÃ³n: Los mÃ³dulos en el directorio aaa se han renombrado y ofrecen mejor + soporte para la autenticaciÃ³n implÃcita (digest). + Por ejemplo: + mod_auth se ha dividido ahora en + mod_auth_basic y + mod_authn_file; mod_auth_dbm ahora + se llama mod_authn_dbm; mod_access ha + sido renombrado a mod_authz_host. TambiÃ©n hay un nuevo + mÃ³dulo mod_authn_alias( ya eliminado en las versiones 2.3/2.4) para + simplificar algunas configuraciones de autenticaciÃ³n. +
mod_authnz_ldap: Este mÃ³dulo se ha traÃdo de la versiÃ³n 2.0 del mÃ³dulo + mod_auth_ldap a la versiÃ³n 2.2 del framework de + AutenticaciÃ³n/AutorizaciÃ³n. Las nuevas caracterÃsticas + incluyen el uso de valores de LDAP y filtros de bÃºsqueda complejos + para la directiva + Require.
mod_authz_owner: Un nuevo mÃ³dulo que autoriza el acceso a ficheros basÃ¡ndose en el + propietario del fichero en el sistema operativo. +
mod_version: Este nuevo mÃ³dulo permite que se habiliten bloques de configuraciÃ³n + dependiendo de la versiÃ³n del servidor. +
mod_info: Se ha aÃ±adido un nuevo argumento al config que muestra + las configuraciones de las directivas que se le pasan a Apache, incluyendo + los nombres de los ficheros y en que linea se encuentra dicha configuraciÃ³n. + Este mÃ³dulo ademÃ¡s muestra en orden todas las peticiones de hooks y informaciÃ³n + adicional a la hora de compilar, similar a httpd -V.
mod_ssl: Se ha aÃ±adido soporte para el + RFC 2817, que permite + conexiones para que se actualicen de texto plano al cifrado TLS.
mod_imagemap: mod_imap Se ha renombrado a + mod_imagemap para evitar confusiÃ³n en el usuario. +

+ +

+ Mejoras de Programas +

httpd: Se ha aÃ±adido una nueva opciÃ³n en la lÃnea de comandos -M, + dicha opciÃ³n lista todos los mÃ³dulos que se cargan basÃ¡ndose en la + configuraciÃ³n actual. A diferencia de la opciÃ³n -l, esta lista + incluye los DSOs cargados mediante el mÃ³dulomod_so. +
httxt2dbm: Un nuevo programa para generar archivos dbm desde archivos de texto + como entrada, para su uso en + RewriteMap + con el mapa de tipo dbm.

+ +

+ Cambios para desarrolladores de MÃ³dulos +

APR 1.0 API

Apache 2.2 usa la API de APR. Todas las funciones y sÃmbolos obsoletas + se han eliminado de APR y + APR-Util. Para mas detalles sobre dichos cambios + vaya a la + pÃ¡gina de APR.

AutenticaciÃ³n y AutorizaciÃ³n

El paquete de mÃ³dulos de autenticaciÃ³n y autorizaciÃ³n se han renombrado + como se muestra en las siguientes lÃneas: +

mod_auth_* -> MÃ³dulos que implementan un mecanismo de + autenticaciÃ³n por HTTP.
mod_authn_* -> MÃ³dulos que proporcionan un backend + proveedor de autenticaciÃ³n.
mod_authz_* -> MÃ³dulos que implementan autorizaciÃ³n + (o acceso)
mod_authnz_* -> MÃ³dulo que implementa ambas opciones + autenticaciÃ³n & autorizaciÃ³n

+ Hay un nuevo esquema de proveedor de la autenticaciÃ³n en el backend + lo que facilita en gran medida la construcciÃ³n de nuevos motores + de autenticaciÃ³n. +

Registro de errores de ConexiÃ³n

Una nueva funciÃ³n ap_log_cerror ha sido aÃ±adida para + registrar los errores que ocurren en la conexiÃ³n del cliente. Cuando se + registra el error, el mensaje incluye la direcciÃ³n IP del cliente.

AÃ±adido Hooks para la configuraciÃ³n de Test

Un nuevo hook, test_config se ha aÃ±adido para ayudar a + los mÃ³dulos que necesitan ejecutar sÃ³lo cÃ³digo especial cuando el usuario + pasa como parÃ¡metro -t a httpd.

ConfiguraciÃ³n de tamaÃ±o de pila para los procesos MPM's

Una nueva directiva, ThreadStackSize se ha aÃ±adido para configurar + el tamaÃ±o de la pila de todos los hilos de MPMs. Esta directiva + es requerida por algÃºn mÃ³dulo de terceros en plataformas que tienen + por defecto una pila con un tamaÃ±o pequeÃ±o.

Manejo de protocolo para los filtros de salida

En el pasado, cada filtro ha sido responsable de garantizar + que genera las cabeceras de respuesta correctas donde les afecta. + Los filtros ahora delegan la administraciÃ³n comÃºn del protocolo + a los mÃ³dulos + mod_filter, usando llamadas a + ap_register_output_filter_protocol Ã³ + ap_filter_protocol.

Monitor de hooks aÃ±adido

Monitor hook habilita a los mÃ³dulos a ejecutar tareas regulares + o programadas en el proceso padre (raÃz).

Cambio de expresiones regulares en la API

La cabecera pcreposix.h ya no esta disponible; + se ha cambiado por la nueva ap_regex.h. La + implementaciÃ³n POSIX.2 de regex.h expuesta por la cabecera + antigua, estÃ¡ ahora disponible en el espacio de nombre con ap_ + en la cabecera ap_regex.h. llama a regcomp, + regexec y asÃ sucesivamente pueden ser sustituidos por + llamadas a ap_regcomp, ap_regexec.

DBD Framework (API de base de datos SQL)

Con Apache 1.x y 2.0, algunos mÃ³dulos que requieren un + backend de SQL deben tomar la responsabilidad de gestionar por sÃ + mismos. Aparte de reinventar la rueda, esto puede llegar a ser + ineficiente, por ejemplo cuando varios mÃ³dulos cada uno mantiene su propia conexiÃ³n. +

+ +

Las versiones de Apache posteriores a la 2.1 proporciona la API de ap_dbd + para el manejo de las conexiones a las bases de datos (incluyendo estrategia + optimizadas para los hilos o no de MPMs), mientras que las versiones de + APR 1.2 y posteriores proporciona la API apr_dbd para + interactuar con la base de datos.

+ +

Los nuevos mÃ³dulos DEBEN usar estas APIs para todas las operaciones en + bases de datos SQL. Aplicaciones existentes DEBEN ser actualizadas para + que lo usen cuando sea posible, de forma transparente o como opciÃ³n recomendada + para sus usuarios.

\ No newline at end of file diff --git a/docs/manual/new_features_2_4.xml.es b/docs/manual/new_features_2_4.xml.es index f8f6b73d23..cf01fa9c4f 100644 --- a/docs/manual/new_features_2_4.xml.es +++ b/docs/manual/new_features_2_4.xml.es @@ -1,416 +1,416 @@ - - - - - - - - - - - -InformaciÃ³n General sobre las Nuevas CaracterÃsticas en Apache HTTP Server 2.4 - -

Este documento describe algunos de los principales cambios entre las versiones - 2.2 y 2.4 del Servidor Apache HTTP. Para las nuevas caracterÃsticas desde - versiÃ³n 2.0, consulte el documento 2.2 nuevas caracterÃsticas.

- -

- Mejoras en el Core -

Cargas de MPM en Tiempo de EjecuciÃ³n: MÃºltiples MPMs ahora se pueden construir - como mÃ³dulos dinÃ¡micos de forma que pueden ser cargados en tiempo de compilaciÃ³n. - El MPM de elecciÃ³n se puede configurar en tiempo de ejecuciÃ³n a travÃ©s - de LoadModule .
Evento MPM: El Evento MPM ya no es experimental, lo cuÃ¡l ahora estÃ¡ totalmente soportado.
Soporte AsÃncrono (Asynchronous): Mejor soporte para lectura y escritura asÃncrona para soporte de MPM y - otras plataformas.
ConfiguraciÃ³n del Nivel de Log (LogLevel) por MÃ³dulo y Directorio: El LogLevel puede ser configurado ahora - por mÃ³dulo y por directorio. Nuevos niveles de trace1 - a trace8 se han aÃ±adido por encima de la etiqueta de nivel de - registro de log debug.
Secciones de ConfiguraciÃ³n por PeticiÃ³n: If, - ElseIf, - y Else se pueden usar - para establecer los criterios de configuraciÃ³n por cada peticiÃ³n.
Analizador de ExpresiÃ³n de Uso General: Un nuevo analizador de expresiones permite especificar - condiciones complejas utilizando una sintaxis comÃºn - en directivas como - SetEnvIfExpr, - RewriteCond, - Header, - If, - entre otras. -
KeepAliveTimeout en Milisegundos: Ahora es posible especificar KeepAliveTimeout en milisegundos. -
Directiva NameVirtualHost: Ya no es necesario y ahora estÃ¡ en desuso.
Anular ConfiguraciÃ³n: La nueva directiva AllowOverrideList - permite un control mÃ¡s exhaustivo de que directivas se permiten en los archivos .htaccess.
Variables de los Archivos de ConfiguraciÃ³n: Ahora es posible Definir - variables en la configuraciÃ³n, lo que permite una representaciÃ³n mÃ¡s clara - si el mismo valor se utiliza en muchos lugares en la configuraciÃ³n. -
ReducciÃ³n del Uso de Memoria: A pesar de muchas de las nuevas caracterÃsticas, 2.4.x tiende a usar menos - memoria que la versiÃ³n 2.2.x.

- -

- Nuevos MÃ³dulos -

mod_proxy_fcgi: Protocolo FastCGI backend paramod_proxy
mod_proxy_scgi: Protocolo SCGI backend para mod_proxy
mod_proxy_express: Proporciona una configuraciÃ³n masiva y dinÃ¡mica de proxys inversos para - mod_proxy
mod_remoteip: Reemplaza la direcciÃ³n IP remota cliente aparente y nombre de host para la solicitud - con la lista de direcciones IP presentada por un proxy o un balanceador de carga a travÃ©s de - las cabeceras de solicitud.
mod_heartmonitor, - mod_lbmethod_heartbeat: Permite a mod_proxy_balancer basar las decisiones del balanceo de - carga segÃºn el nÃºmero de conexiones activas en los servidores de back-end.
mod_proxy_html: antiguamente un mÃ³dulo de terceros, esto apoya la fijaciÃ³n de enlaces HTML en un proxy inverso, -situaciÃ³n en la que el servidor genera URLs que no son vÃ¡lidos para los clientes del proxy.
mod_sed: Un reemplazo avanzado de mod_substitute, permite editar el - cuerpo de la respuesta con el poder lleno de sed.
mod_auth_form: Habilitar la autenticaciÃ³n basada en formularios.
mod_session: Permite el uso de estado de sesiÃ³n para clientes, utilizando cookies o el - almacenamiento en una base de datos.
mod_allowmethods: Nuevo mÃ³dulo para restringir ciertos mÃ©todos HTTP sin interferir con - autenticaciÃ³n o autorizaciÃ³n.
mod_lua: Embebe el lenguajeLua en httpd, - para la configuraciÃ³n y las funciones lÃ³gicas de negocios pequeÃ±os. (Experimental)
mod_log_debug: Permite aÃ±adir mensajes de depuraciÃ³n personalizados en las diferentes fases del procesamiento de la solicitud.
mod_buffer: Proporciona almacenamiento en bÃºfer para los filtros de entrada y salida de las pilas
mod_data: Convierte la respuesta del cuerpo en una direcciÃ³n URL de datos RFC2397
mod_ratelimit: Proporciona limitaciÃ³n de velocidad en el ancho de banda para los clientes
mod_request: Proporciona filtros para manejar y hacer el cuerpo de la peticiÃ³n HTTP disponibles
mod_reflector: Proporciona ReflexiÃ³n del cuerpo de la peticiÃ³n como una respuesta a travÃ©s de la pila de filtro de salida.
mod_slotmem_shm: Proporciona un proveedor de memoria compartida basada en la ranura (ala the scoreboard).
mod_xml2enc: Anteriormente un mÃ³dulo de terceros, que apoya la internacionalizaciÃ³n en - mÃ³dulos de filtro (markup-aware) basada en libxml2.
mod_macro (disponible desde la versiÃ³n 2.4.5): Provee macros para los archivos de configuraciÃ³n
mod_proxy_wstunnel (disponible desde la versiÃ³n 2.4.5): Soporte a tÃºneles web-socket.
mod_authnz_fcgi (disponible desde la versiÃ³n 2.4.10): Habilitar aplicaciones autorizadas FastCGI para autenticar y/o autorizar a los clientes.
mod_http2 (disponible desde la versiÃ³n 2.4.17): Soporte para la capa HTTP/2

- -

- Mejoras de MÃ³dulos. -

mod_ssl: mod_ssl ahora puede ser configurado para utilizar un servidor - OCSP para comprobar el estado de validez de un certificado de cliente. La respuesta por - defecto es configurable, junto con la decisiÃ³n sobre si se debe preferir el "responder" - designado en el certificado de cliente en sÃ.; mod_ssl ahora tambiÃ©n es compatible con "OCSP stapling", - una respuesta de OCSP al inicial TLS "Handshake" con marca de tiempo - firmado por la CA , en el que el servidor obtiene de forma proactiva - una verificaciÃ³n OCSP de su certificado y transmite esa o la del cliente - durante el "Handshake".; mod_ssl Ahora se puede configurar para compartir los datos de - sesiÃ³n SSL entre servidores a travÃ©s de memcached.; Claves de cifrado de tipo EC (Curva ElÃptica en InglÃ©s) son ahora - soportadas junto con RSA y DSA.; Soporte de TLS-SRP (disponible en la versiÃ³n 2.4.4 y posteriores).
mod_proxy: La directiva ProxyPass - ahora estÃ¡ configurado de forma mÃ¡s Ã³ptima dentro de un bloque - Location o - LocationMatch, - y ofrece una ventaja de rendimiento significativa sobre la sintaxis tradicional - de dos parÃ¡metros cuando estÃ¡n presentes en gran nÃºmero.; La direcciÃ³n de origen utilizada para solicitudes de proxy es ahora configurable.; Soporte para sockets de dominio Unix en el backend (disponible en la versiÃ³n 2.4.7 - y posteriores).
mod_proxy_balancer: MÃ¡s cambios en la configuraciÃ³n en tiempo de ejecuciÃ³n para BalancerMembers - mediante el manager del balanceador.; Se pueden agregar miembros adicionales a BalancerMembers en tiempo de ejecuciÃ³n - mediante el manager del balanceador.; ConfiguraciÃ³n de ejecuciÃ³n de un subconjunto de parÃ¡metros Balancer; BalancerMembers se puede establecer en "fuga" de modo que sÃ³lo responden a las - sesiones problemÃ¡ticas existentes, lo que les permite ser puestos con gracia fuera de lÃnea.; ConfiguraciÃ³n del balanceador de carga pueden ser persistentes despuÃ©s de un reinicio.
mod_cache: En el mÃ³dulo mod_cache se puede aÃ±adir filtro de cache en determinado - punto en la cadena de filtro, para proveer mejor control de la cachÃ©; mod_cache Puede cachear ahora peticiones de tipo HEAD.; Siendo posible ahora las directivas mod_cache - ser configuradas por directorio en vez de por servidor.; La URL base de las URLs cacheadas se pueden personalizar, - de tal forma que un cluster de cachÃ©s puede compartir el mismo - prefijo URL de punto final.; mod_cache ahora es capaz de servir a los datos en cachÃ© - antigua cuando un motor no estÃ¡ disponible (error 5xx).; mod_cache ahora puede insertar HIT/MISS/REVALIDATE - en una cabecera de tipo X-Cache.
mod_include: Soporte al atributo 'onerror' dentro del elemento 'include', lo que permite - mostar un documento de error cuando hay un error en vez de la cadena de error por defecto. -
mod_cgi, mod_include, - mod_isapi, ...: La traducciÃ³n de cabeceras a variables de entorno es mÃ¡s estricta que antes para mitigar - algunos de los posibles ataques de cross-site scripting, a travÃ©s de la inyecciÃ³n de cabecera. - Las cabeceras que contienen carÃ¡cteres no vÃ¡lidos (incluyendo guiones bajos) - son descartadas de forma silenciosa. Las variables de entorno en - Apache tienen algunos consejos en como trabajar con clientes con sistemas heredados rotos que - requieren de este tipo de cabeceras. (Esto afecta a todos los mÃ³dulos que - usan Ã©stas variables de entorno.)
mod_authz_core AutorizaciÃ³n LÃ³gica de Contenedores: Ahora puede ser especificada una lÃ³gica avanzada de autorizaciÃ³n, usando la directiva - Require y - las directivas de los contenedores asociados, tales como - RequireAll.
mod_rewrite: mod_rewrite aÃ±ade los flags [QSD] - (Query String Discard) y [END] para las directivas - RewriteRule para - simplificar escenarios de reescritura comunes.; AÃ±ade la posibilidad de usar expresiones buleanas complejas en RewriteCond.; Permite el uso de queris SQL como funciones de RewriteMap.
mod_ldap, mod_authnz_ldap: mod_authnz_ldap agrega soporte a grupos anidados.; mod_ldap Incorpora - LDAPConnectionPoolTTL, - LDAPTimeout, y otras mejoras - en el manejo de los "timeouts" tiempo agotado de espera. - Esto es especialmente Ãºtil para escenarios en los que existe un firewall - en modo "Stateful" que desecha conexiones inactivas a un servidor LDAP.; mod_ldap Incorpora - LDAPLibraryDebug para registrar informaciÃ³n de - depuraciÃ³n proporcionada por el conjunto de herramientas usadas por LDAP.
mod_info: mod_info ahora puede volcar la configuraciÃ³n pre-procesada - a la salida estÃ¡ndar durante el inicio del servidor.
mod_auth_basic: Nuevo mecanismo genÃ©rico para la autenticaciÃ³n bÃ¡sica falsa (disponible en la versiÃ³n - 2.4.5 y posteriores).

- -

- Mejoras para el Programa -

fcgistarter: Nuevo demonio FastCGI como utilidad de arranque
htcacheclean: Ahora las URLs cacheadas actualmente, pueden ser listadas, con meta-datos adicionales incluidos.; Permite el borrado explicito y selectivo de URLs cacheadas.; Los tamaÃ±os de archivo ahora se pueden redondear hasta el tamaÃ±o de bloque determinado, - por lo que los lÃmites de tamaÃ±o se asemeja mÃ¡s estrechamente con el tamaÃ±o real en el disco.; El tamaÃ±o de la cachÃ© ahora puede ser limitado por el nÃºmero de i-nodos, - en vez de o como aÃ±adido, al limite del tamaÃ±o del archivo en el disco.
rotatelogs: Ahora puede crear un enlace al propio fichero de log.; Ahora puede invocar a un escript personalizado pos-rotate.
htpasswd, htdbm: Soporta el algoritmo bcrypt (disponible en la versiÃ³n 2.4.4 y posteriores). -

- -

- DocumentaciÃ³n -

mod_rewrite: La documentaciÃ³n de mod_rewrite ha sido reorganizada - y casi escrita por completo, poniendo Ã©nfasis en ejemplos y modos de empleo - mÃ¡s comunes, asÃ como enseÃ±arle que otras soluciones son mÃ¡s apropiadas. - - La guÃa del mÃ³dulo Rewrite es ahora ahora es una - secciÃ³n de nivel superior con mucho mÃ¡s detalle y una mejor organizaciÃ³n.
mod_ssl: La documentaciÃ³n del mÃ³dulo mod_ssl ha sido mejorada en gran medida, - con mÃ¡s ejemplos a nivel de la instalaciÃ³n inicial, ademÃ¡s del enfoque tÃ©cnico anterior.
GuÃa de CachÃ©s: La guÃa de cachÃ© ha sido reescrita para distinguir propiamente - entre la cachÃ© del RFC2616 HTTP/1.1 y sus caracterÃsticas - aportadas por mod_cache, y el caso general de cache de valor/clave - aportado por la interfaz socache, - asÃ como cubrir temas especÃficos como los mecanismos de cachÃ© aportados por el mÃ³dulo - mod_file_cache.

- -

- Cambios en los Desarrollos de MÃ³dulos -

AÃ±adido Hook de ComprobaciÃ³n de ConfiguraciÃ³n: El nuevo Hook, check_config, ha sido aÃ±adido el cuÃ¡l se ejecuta entre - los hooks pre_config y open_logs. - TambiÃ©n se ejecuta antes del hook test_config cuando la opciÃ³n - -t se le pasa al httpd. El hook check_config - permite a los mÃ³dulos revisar los valores en las directivas de - configuraciones de forma independiente y ajustarlos mientras - mensajes pueden seguir siendo logados a la consola. - - El usuario puede asÃ ser alertado de problemas de mala - configuraciÃ³n antes de que la funciÃ³n hook open_logs - redireccione la salida de error por la consola - al log de error.
AÃ±adido un Analizador de Expresiones: Ahora tenemos un analizador de expresiones de propÃ³sito general, y su API estÃ¡ - expuesta en ap_expr.h. Esto es una adaptaciÃ³n del que habÃa anteriormente - implementado en mod_ssl.
AutorizaciÃ³n LÃ³gica de Contenedores: Los mÃ³dulos de autorizaciÃ³n ahora se registran como un proveedor, mediante - ap_register_auth_provider(), para soportar lÃ³gicas de autorizaciÃ³n avanzadas, - como la directiva RequireAll.
Interfaz de Almacenamiento en CachÃ© de Objetos PequeÃ±os: La cabecera ap_socache.h expone una interfaz basada en proveedor - de objetos de datos para la captura de pequeÃ±os, basado en la - aplicaciÃ³n anterior de cachÃ© de sesiÃ³n del mÃ³dulo mod_ssl. - Los proveedores que utilizan una memoria compartida de bÃºfer cÃclico, - archivos dbf basados en disco, y una memoria cachÃ© distribuida - memcached estÃ¡n soportados actualmente.
AÃ±adido Hook de Estado de la CachÃ©: El mÃ³dulo mod_cache ahora incluye un nuevo hook - cache_status, que es llamado cuando las - decisiones de cachÃ© son conocidas. Se provee una implementaciÃ³n - por defecto que aÃ±ade a la cabecera de la respuesta de forma - opcional X-Cache y X-Cache-Detail.

- -

La documentaciÃ³n de desarrolladores contiene una - lista detallada de los cambios realizados - en la API.

- - + + + + + + + + + + + +InformaciÃ³n General sobre las Nuevas CaracterÃsticas en Apache HTTP Server 2.4 + +

Este documento describe algunos de los principales cambios entre las versiones + 2.2 y 2.4 del Servidor Apache HTTP. Para las nuevas caracterÃsticas desde + versiÃ³n 2.0, consulte el documento 2.2 nuevas caracterÃsticas.

+ +

+ Mejoras en el Core +

Cargas de MPM en Tiempo de EjecuciÃ³n: MÃºltiples MPMs ahora se pueden construir + como mÃ³dulos dinÃ¡micos de forma que pueden ser cargados en tiempo de compilaciÃ³n. + El MPM de elecciÃ³n se puede configurar en tiempo de ejecuciÃ³n a travÃ©s + de LoadModule .
Evento MPM: El Evento MPM ya no es experimental, lo cuÃ¡l ahora estÃ¡ totalmente soportado.
Soporte AsÃncrono (Asynchronous): Mejor soporte para lectura y escritura asÃncrona para soporte de MPM y + otras plataformas.
ConfiguraciÃ³n del Nivel de Log (LogLevel) por MÃ³dulo y Directorio: El LogLevel puede ser configurado ahora + por mÃ³dulo y por directorio. Nuevos niveles de trace1 + a trace8 se han aÃ±adido por encima de la etiqueta de nivel de + registro de log debug.
Secciones de ConfiguraciÃ³n por PeticiÃ³n: If, + ElseIf, + y Else se pueden usar + para establecer los criterios de configuraciÃ³n por cada peticiÃ³n.
Analizador de ExpresiÃ³n de Uso General: Un nuevo analizador de expresiones permite especificar + condiciones complejas utilizando una sintaxis comÃºn + en directivas como + SetEnvIfExpr, + RewriteCond, + Header, + If, + entre otras. +
KeepAliveTimeout en Milisegundos: Ahora es posible especificar KeepAliveTimeout en milisegundos. +
Directiva NameVirtualHost: Ya no es necesario y ahora estÃ¡ en desuso.
Anular ConfiguraciÃ³n: La nueva directiva AllowOverrideList + permite un control mÃ¡s exhaustivo de que directivas se permiten en los archivos .htaccess.
Variables de los Archivos de ConfiguraciÃ³n: Ahora es posible Definir + variables en la configuraciÃ³n, lo que permite una representaciÃ³n mÃ¡s clara + si el mismo valor se utiliza en muchos lugares en la configuraciÃ³n. +
ReducciÃ³n del Uso de Memoria: A pesar de muchas de las nuevas caracterÃsticas, 2.4.x tiende a usar menos + memoria que la versiÃ³n 2.2.x.

+ +

+ Nuevos MÃ³dulos +

mod_proxy_fcgi: Protocolo FastCGI backend paramod_proxy
mod_proxy_scgi: Protocolo SCGI backend para mod_proxy
mod_proxy_express: Proporciona una configuraciÃ³n masiva y dinÃ¡mica de proxys inversos para + mod_proxy
mod_remoteip: Reemplaza la direcciÃ³n IP remota cliente aparente y nombre de host para la solicitud + con la lista de direcciones IP presentada por un proxy o un balanceador de carga a travÃ©s de + las cabeceras de solicitud.
mod_heartmonitor, + mod_lbmethod_heartbeat: Permite a mod_proxy_balancer basar las decisiones del balanceo de + carga segÃºn el nÃºmero de conexiones activas en los servidores de back-end.
mod_proxy_html: antiguamente un mÃ³dulo de terceros, esto apoya la fijaciÃ³n de enlaces HTML en un proxy inverso, +situaciÃ³n en la que el servidor genera URLs que no son vÃ¡lidos para los clientes del proxy.
mod_sed: Un reemplazo avanzado de mod_substitute, permite editar el + cuerpo de la respuesta con el poder lleno de sed.
mod_auth_form: Habilitar la autenticaciÃ³n basada en formularios.
mod_session: Permite el uso de estado de sesiÃ³n para clientes, utilizando cookies o el + almacenamiento en una base de datos.
mod_allowmethods: Nuevo mÃ³dulo para restringir ciertos mÃ©todos HTTP sin interferir con + autenticaciÃ³n o autorizaciÃ³n.
mod_lua: Embebe el lenguajeLua en httpd, + para la configuraciÃ³n y las funciones lÃ³gicas de negocios pequeÃ±os. (Experimental)
mod_log_debug: Permite aÃ±adir mensajes de depuraciÃ³n personalizados en las diferentes fases del procesamiento de la solicitud.
mod_buffer: Proporciona almacenamiento en bÃºfer para los filtros de entrada y salida de las pilas
mod_data: Convierte la respuesta del cuerpo en una direcciÃ³n URL de datos RFC2397
mod_ratelimit: Proporciona limitaciÃ³n de velocidad en el ancho de banda para los clientes
mod_request: Proporciona filtros para manejar y hacer el cuerpo de la peticiÃ³n HTTP disponibles
mod_reflector: Proporciona ReflexiÃ³n del cuerpo de la peticiÃ³n como una respuesta a travÃ©s de la pila de filtro de salida.
mod_slotmem_shm: Proporciona un proveedor de memoria compartida basada en la ranura (ala the scoreboard).
mod_xml2enc: Anteriormente un mÃ³dulo de terceros, que apoya la internacionalizaciÃ³n en + mÃ³dulos de filtro (markup-aware) basada en libxml2.
mod_macro (disponible desde la versiÃ³n 2.4.5): Provee macros para los archivos de configuraciÃ³n
mod_proxy_wstunnel (disponible desde la versiÃ³n 2.4.5): Soporte a tÃºneles web-socket.
mod_authnz_fcgi (disponible desde la versiÃ³n 2.4.10): Habilitar aplicaciones autorizadas FastCGI para autenticar y/o autorizar a los clientes.
mod_http2 (disponible desde la versiÃ³n 2.4.17): Soporte para la capa HTTP/2

+ +

+ Mejoras de MÃ³dulos. +

mod_ssl: mod_ssl ahora puede ser configurado para utilizar un servidor + OCSP para comprobar el estado de validez de un certificado de cliente. La respuesta por + defecto es configurable, junto con la decisiÃ³n sobre si se debe preferir el "responder" + designado en el certificado de cliente en sÃ.; mod_ssl ahora tambiÃ©n es compatible con "OCSP stapling", + una respuesta de OCSP al inicial TLS "Handshake" con marca de tiempo + firmado por la CA , en el que el servidor obtiene de forma proactiva + una verificaciÃ³n OCSP de su certificado y transmite esa o la del cliente + durante el "Handshake".; mod_ssl Ahora se puede configurar para compartir los datos de + sesiÃ³n SSL entre servidores a travÃ©s de memcached.; Claves de cifrado de tipo EC (Curva ElÃptica en InglÃ©s) son ahora + soportadas junto con RSA y DSA.; Soporte de TLS-SRP (disponible en la versiÃ³n 2.4.4 y posteriores).
mod_proxy: La directiva ProxyPass + ahora estÃ¡ configurado de forma mÃ¡s Ã³ptima dentro de un bloque + Location o + LocationMatch, + y ofrece una ventaja de rendimiento significativa sobre la sintaxis tradicional + de dos parÃ¡metros cuando estÃ¡n presentes en gran nÃºmero.; La direcciÃ³n de origen utilizada para solicitudes de proxy es ahora configurable.; Soporte para sockets de dominio Unix en el backend (disponible en la versiÃ³n 2.4.7 + y posteriores).
mod_proxy_balancer: MÃ¡s cambios en la configuraciÃ³n en tiempo de ejecuciÃ³n para BalancerMembers + mediante el manager del balanceador.; Se pueden agregar miembros adicionales a BalancerMembers en tiempo de ejecuciÃ³n + mediante el manager del balanceador.; ConfiguraciÃ³n de ejecuciÃ³n de un subconjunto de parÃ¡metros Balancer; BalancerMembers se puede establecer en "fuga" de modo que sÃ³lo responden a las + sesiones problemÃ¡ticas existentes, lo que les permite ser puestos con gracia fuera de lÃnea.; ConfiguraciÃ³n del balanceador de carga pueden ser persistentes despuÃ©s de un reinicio.
mod_cache: En el mÃ³dulo mod_cache se puede aÃ±adir filtro de cache en determinado + punto en la cadena de filtro, para proveer mejor control de la cachÃ©; mod_cache Puede cachear ahora peticiones de tipo HEAD.; Siendo posible ahora las directivas mod_cache + ser configuradas por directorio en vez de por servidor.; La URL base de las URLs cacheadas se pueden personalizar, + de tal forma que un cluster de cachÃ©s puede compartir el mismo + prefijo URL de punto final.; mod_cache ahora es capaz de servir a los datos en cachÃ© + antigua cuando un motor no estÃ¡ disponible (error 5xx).; mod_cache ahora puede insertar HIT/MISS/REVALIDATE + en una cabecera de tipo X-Cache.
mod_include: Soporte al atributo 'onerror' dentro del elemento 'include', lo que permite + mostar un documento de error cuando hay un error en vez de la cadena de error por defecto. +
mod_cgi, mod_include, + mod_isapi, ...: La traducciÃ³n de cabeceras a variables de entorno es mÃ¡s estricta que antes para mitigar + algunos de los posibles ataques de cross-site scripting, a travÃ©s de la inyecciÃ³n de cabecera. + Las cabeceras que contienen carÃ¡cteres no vÃ¡lidos (incluyendo guiones bajos) + son descartadas de forma silenciosa. Las variables de entorno en + Apache tienen algunos consejos en como trabajar con clientes con sistemas heredados rotos que + requieren de este tipo de cabeceras. (Esto afecta a todos los mÃ³dulos que + usan Ã©stas variables de entorno.)
mod_authz_core AutorizaciÃ³n LÃ³gica de Contenedores: Ahora puede ser especificada una lÃ³gica avanzada de autorizaciÃ³n, usando la directiva + Require y + las directivas de los contenedores asociados, tales como + RequireAll.
mod_rewrite: mod_rewrite aÃ±ade los flags [QSD] + (Query String Discard) y [END] para las directivas + RewriteRule para + simplificar escenarios de reescritura comunes.; AÃ±ade la posibilidad de usar expresiones buleanas complejas en RewriteCond.; Permite el uso de queris SQL como funciones de RewriteMap.
mod_ldap, mod_authnz_ldap: mod_authnz_ldap agrega soporte a grupos anidados.; mod_ldap Incorpora + LDAPConnectionPoolTTL, + LDAPTimeout, y otras mejoras + en el manejo de los "timeouts" tiempo agotado de espera. + Esto es especialmente Ãºtil para escenarios en los que existe un firewall + en modo "Stateful" que desecha conexiones inactivas a un servidor LDAP.; mod_ldap Incorpora + LDAPLibraryDebug para registrar informaciÃ³n de + depuraciÃ³n proporcionada por el conjunto de herramientas usadas por LDAP.
mod_info: mod_info ahora puede volcar la configuraciÃ³n pre-procesada + a la salida estÃ¡ndar durante el inicio del servidor.
mod_auth_basic: Nuevo mecanismo genÃ©rico para la autenticaciÃ³n bÃ¡sica falsa (disponible en la versiÃ³n + 2.4.5 y posteriores).

+ +

+ Mejoras para el Programa +

fcgistarter: Nuevo demonio FastCGI como utilidad de arranque
htcacheclean: Ahora las URLs cacheadas actualmente, pueden ser listadas, con meta-datos adicionales incluidos.; Permite el borrado explicito y selectivo de URLs cacheadas.; Los tamaÃ±os de archivo ahora se pueden redondear hasta el tamaÃ±o de bloque determinado, + por lo que los lÃmites de tamaÃ±o se asemeja mÃ¡s estrechamente con el tamaÃ±o real en el disco.; El tamaÃ±o de la cachÃ© ahora puede ser limitado por el nÃºmero de i-nodos, + en vez de o como aÃ±adido, al limite del tamaÃ±o del archivo en el disco.
rotatelogs: Ahora puede crear un enlace al propio fichero de log.; Ahora puede invocar a un escript personalizado pos-rotate.
htpasswd, htdbm: Soporta el algoritmo bcrypt (disponible en la versiÃ³n 2.4.4 y posteriores). +

+ +

+ DocumentaciÃ³n +

mod_rewrite: La documentaciÃ³n de mod_rewrite ha sido reorganizada + y casi escrita por completo, poniendo Ã©nfasis en ejemplos y modos de empleo + mÃ¡s comunes, asÃ como enseÃ±arle que otras soluciones son mÃ¡s apropiadas. + + La guÃa del mÃ³dulo Rewrite es ahora ahora es una + secciÃ³n de nivel superior con mucho mÃ¡s detalle y una mejor organizaciÃ³n.
mod_ssl: La documentaciÃ³n del mÃ³dulo mod_ssl ha sido mejorada en gran medida, + con mÃ¡s ejemplos a nivel de la instalaciÃ³n inicial, ademÃ¡s del enfoque tÃ©cnico anterior.
GuÃa de CachÃ©s: La guÃa de cachÃ© ha sido reescrita para distinguir propiamente + entre la cachÃ© del RFC2616 HTTP/1.1 y sus caracterÃsticas + aportadas por mod_cache, y el caso general de cache de valor/clave + aportado por la interfaz socache, + asÃ como cubrir temas especÃficos como los mecanismos de cachÃ© aportados por el mÃ³dulo + mod_file_cache.

+ +

+ Cambios en los Desarrollos de MÃ³dulos +

AÃ±adido Hook de ComprobaciÃ³n de ConfiguraciÃ³n: El nuevo Hook, check_config, ha sido aÃ±adido el cuÃ¡l se ejecuta entre + los hooks pre_config y open_logs. + TambiÃ©n se ejecuta antes del hook test_config cuando la opciÃ³n + -t se le pasa al httpd. El hook check_config + permite a los mÃ³dulos revisar los valores en las directivas de + configuraciones de forma independiente y ajustarlos mientras + mensajes pueden seguir siendo logados a la consola. + + El usuario puede asÃ ser alertado de problemas de mala + configuraciÃ³n antes de que la funciÃ³n hook open_logs + redireccione la salida de error por la consola + al log de error.
AÃ±adido un Analizador de Expresiones: Ahora tenemos un analizador de expresiones de propÃ³sito general, y su API estÃ¡ + expuesta en ap_expr.h. Esto es una adaptaciÃ³n del que habÃa anteriormente + implementado en mod_ssl.
AutorizaciÃ³n LÃ³gica de Contenedores: Los mÃ³dulos de autorizaciÃ³n ahora se registran como un proveedor, mediante + ap_register_auth_provider(), para soportar lÃ³gicas de autorizaciÃ³n avanzadas, + como la directiva RequireAll.
Interfaz de Almacenamiento en CachÃ© de Objetos PequeÃ±os: La cabecera ap_socache.h expone una interfaz basada en proveedor + de objetos de datos para la captura de pequeÃ±os, basado en la + aplicaciÃ³n anterior de cachÃ© de sesiÃ³n del mÃ³dulo mod_ssl. + Los proveedores que utilizan una memoria compartida de bÃºfer cÃclico, + archivos dbf basados en disco, y una memoria cachÃ© distribuida + memcached estÃ¡n soportados actualmente.
AÃ±adido Hook de Estado de la CachÃ©: El mÃ³dulo mod_cache ahora incluye un nuevo hook + cache_status, que es llamado cuando las + decisiones de cachÃ© son conocidas. Se provee una implementaciÃ³n + por defecto que aÃ±ade a la cabecera de la respuesta de forma + opcional X-Cache y X-Cache-Detail.

+ +

La documentaciÃ³n de desarrolladores contiene una + lista detallada de los cambios realizados + en la API.

+ + diff --git a/docs/manual/stopping.html.es b/docs/manual/stopping.html.es index 7b0b2e6dd9..111f4e53e2 100644 --- a/docs/manual/stopping.html.es +++ b/docs/manual/stopping.html.es @@ -1,278 +1,278 @@ - - - - + + + + -Iniciar y Parar el servidor Apache - Servidor HTTP Apache Versión 2.5 - - - - - - - -

-Apache > Servidor HTTP > Documentación > Versión 2.5

Iniciar y Parar el servidor Apache

Idiomas disponibles: de | - en | - es | - fr | - ja | - ko | - tr

- -

Este documento explica como iniciar y parar el servidor Apache - en sistemas tipo Unix. Los usuarios de Windows NT, 2000 y XP - deben consultar la sección Ejecutar Apache como un - servicio y los usuario de Windows 9x y ME deben consultar Ejecutar Apache como una - Aplicación de Consola para obtener información - sobre como controlar Apache en esas plataformas.

Introducción
Parar Ahora Apache
Reinicio "Graceful" o elegante
Reiniciar Apache
Apándice: señales y race conditions

Consulte también

Introducción

- -

Para parar y reiniciar Apache, hay que enviar la señal - apropiada al proceso padre httpd que se está - ejecutando. Hay dos maneras de enviar estas señales. En - primer lugar, puede usar el comando de Unix kill que - envía señales directamente a los procesos. Puede que - tenga varios procesos httpd ejecutándose en su - sistema, pero las señales deben enviarse solamente al proceso - padre, cuyo PID está especificado en la directiva PidFile. Esto quiere decir que no - debe necesitar enviar señales a ningún proceso excepto - al proceso padre. Hay tres señales que puede enviar al - proceso padre: - TERM, - USR1 - HUP, y - WINCH, - que van a ser descritas a continuación.

- -

Para enviar una señal al proceso padre debe escribir un - comando como el que se muestra en el ejemplo:

- -

kill -TERM `cat /usr/local/apache2/logs/httpd.pid`

- -

La segunda manera de enviar señales a los procesos - httpd es usando las opciones de línea de - comandos -k: stop, restart, - y graceful y graceful-stop, como se - muestra más abajo. Estas opciones se le pueden pasar al binario - httpd, pero se recomienda que se pasen al - script de control apachectl, que a su vez los - pasará a httpd.

- -

Después de haber enviado las señales que desee a - httpd, puede ver como progresa el proceso - escribiendo:

- -

tail -f /usr/local/apache2/logs/error_log

- -

Modifique estos ejemplos para que coincidan con la - configuración que tenga especificada en las directivas - ServerRoot y PidFile en su fichero principal de - configuración.

Parar Ahora Apache

- -

Señal: TERM: apachectl -k stop

- -

Enviar las señales TERM o stop - al proceso padre hace que se intenten eliminar todos los procesos - hijos inmediatamente. Esto puede tardar algunos segundos. Una vez que hayan - terminado todos los procesos hijos, terminará el proceso padre. - Cualquier petición en proceso terminará inmediatamente, y - ninguna petición posterior será - atendida.

Reinicio "Graceful" o elegante

- -

Señal: USR1: apachectl -k graceful

- -

Las señales USR1 o graceful - hacen que el proceso padre indique a sus hijos que - terminen después de servir la petición que están - atendiendo en ese momento (o de inmediato si no están - sirviendo ninguna petición). El proceso padre lee de nuevo - sus ficheros de configuración y vuelve a abrir sus ficheros - log. Conforme cada hijo va terminando, el proceso padre lo va - sustituyendo con un hijo de una nueva generación con - la nueva configuración, que empiezan a servir peticiones - inmediatamente.

- -

En algunas plataformas que no permiten usar - USR1 para reinicios graceful, puede usarse una - señal alternativa (como WINCH). También puede - usar apachectl graceful y el script de control - enviará la señal adecuada para su plataforma.

- -

Apache está diseñado para respetar en todo momento la - directiva de control de procesos de los MPM, así como para - que el número de procesos e hilos disponibles para servir a - los clientes se mantenga en los valores adecuados durante el - proceso de reinicio. Aún más, está diseñado - para respetar la directiva StartServers de la siguiente - manera: si después de al menos un segundo el nuevo hijo de la - directiva StartServers - no ha sido creado, entonces crea los suficientes para que se atienda - el trabajo que queda por hacer. Así, se intenta mantener - tanto el número de hijos adecuado para el trabajo que el - servidor tenga en ese momento, como respetar la configuración - determinada por los parámetros de la directiva - StartServers.

- -

Los usuarios del módulo mod_status - notarán que las estadísticas del servidor - no se ponen a cero cuando se usa la señal - USR1. Apache fue escrito tanto para minimizar el - tiempo en el que el servidor no puede servir nuevas peticiones - (que se pondrán en cola por el sistema operativo, de modo que - se no se pierda ningún evento), como para respetar sus - parámetros de ajuste. Para hacer esto, tiene que guardar el - scoreboard usado para llevar el registro de los procesos - hijo a través de las distintas generaciones.

- -

El mod_status también usa una G para indicar - que esos hijos están todavía sirviendo peticiones - previas al reinicio graceful.

- -

Actualmente no existe ninguna manera de que un script con un - log de rotación usando USR1 sepa con seguridad - que todos los hijos que se registraron en el log con anterioridad - al reinicio han terminado. Se aconseja que se use un retardo - adecuado después de enviar la señal USR1 - antes de hacer nada con el log antiguo. Por ejemplo, si la mayor - parte las visitas que recibe de usuarios que tienen conexiones de - baja velocidad tardan menos de 10 minutos en completarse, entonces - espere 15 minutos antes de hacer nada con el log antiguo.

- -

Si su fichero de configuración tiene errores cuando - haga el reinicio, entonces el proceso padre no se reiniciará - y terminará con un error. En caso de un reinicio graceful, - también dejará a los procesos hijo ejecutándose mientras - existan. (Estos son los hijos de los que se está saliendo de - forma graceful y que están sirviendo sus últimas - peticiones.) Esto provocará problemas si intenta reiniciar el - servidor no será posible conectarse a la lista de puertos - de escucha. Antes de reiniciar, puede comprobar que la sintaxis de - sus ficheros de configuración es correcta con la opción de - línea de comandos -t (consulte httpd). - No obstante, esto no - garantiza que el servidor se reinicie correctamente. Para - comprobar que no hay errores en los ficheros de - configuración, puede intentar iniciar httpd con - un usuario diferente a root. Si no hay errores, intentará - abrir sus sockets y logs y fallará porque el usuario no es - root (o porque el httpd que se está ejecutando - en ese momento ya está conectado a esos puertos). Si falla - por cualquier otra razón, entonces casi seguro que hay - algún error en alguno de los ficheros de configuración y - debe corregir ese o esos errores antes de hacer un reinicio - graceful.

Reiniciar Apache

- -

Señal: HUP: apachectl -k restart

- -

El envío de las señales HUP o - restart al proceso padre hace que los procesos hijo - terminen como si le enviáramos la señal - TERM, para eliminar el proceso padre. La diferencia - está en que estas señales vuelven a leer los archivos de - configuración y vuelven a abrir los ficheros log. Se genera - un nuevo conjunto de hijos y se continúa sirviendo - peticiones.

- -

Los usuarios del módulo mod_status - notarán que las estadísticas del servidor se ponen a - cero cuando se envía la señal HUP.

- -

Si su fichero de configuración contiene errores, cuando -intente reiniciar, el proceso padre del servidor no se -reiniciará, sino que terminará con un error. Consulte -más arriba cómo puede solucionar este problema.

Apándice: señales y race conditions

- -

Con anterioridad a la versión de Apache 1.2b9 había - varias race conditions implicadas en las señales - para parar y reiniciar procesos (una descripción sencilla de - una race condition es: un problema relacionado con el momento en - que suceden las cosas, como si algo sucediera en momento en que no - debe, y entonces el resultado esperado no se corresponde con el - obtenido). Para aquellas arquitecturas que tienen el conjunto de - características "adecuadas", se han eliminado tantas race - conditions como ha sido posible. Pero hay que tener en cuenta que - todavía existen race conditions en algunas arquitecturas.

- -

En las arquitecturas que usan un ScoreBoardFile en disco, existe la - posibilidad de que se corrompan los scoreboards. Esto puede hacer - que se produzca el error "bind: Address already in use" - (despuás de usarHUP) o el error "long lost child - came home!" (despuás de usar USR1). En el - primer caso se trata de un error irrecuperable, mientras que en el - segundo, solo ocurre que el servidor pierde un slot del - scoreboard. Por lo tanto, sería aconsejable usar reinicios - graceful, y solo hacer reinicios normales de forma - ocasional. Estos problemas son bastante complicados de solucionar, - pero afortunadamente casi ninguna arquitectura necesita un fichero - scoreboard. Consulte la documentación de la directiva - ScoreBoardFile para ver - las arquitecturas que la usan.

- -

Todas las arquitecturas tienen una pequeña race condition - en cada proceso hijo implicada en la segunda y subsiguientes - peticiones en una conexión HTTP persistente - (KeepAlive). Puede ser que el servidor termine después de - leer la línea de petición pero antes de leer cualquiera - de las cabeceras de petición. Hay una solución que fue - descubierta demasiado tarde para la incluirla en versión - 1.2. En teoría esto no debe suponer ningún problema porque el - cliente KeepAlive ha de esperar que estas cosas pasen debido a los - retardos de red y a los timeouts que a veces dan los - servidores. En la practica, parece que no afecta a nada más - -- en una sesión de pruebas, un servidor se reinició - veinte veces por segundo y los clientes pudieron navegar sin - problemas por el sitio web sin encontrar problemas ni para - descargar una sola imagen ni encontrar un solo enlace roto.

Idiomas disponibles: de | - en | - es | - fr | - ja | - ko | - tr

Comentarios

+ --> +Iniciar y Parar el servidor Apache - Servidor HTTP Apache Versión 2.5 + + + + + + + +

+Apache > Servidor HTTP > Documentación > Versión 2.5

Iniciar y Parar el servidor Apache

Idiomas disponibles: de | + en | + es | + fr | + ja | + ko | + tr

+ +

Este documento explica como iniciar y parar el servidor Apache + en sistemas tipo Unix. Los usuarios de Windows NT, 2000 y XP + deben consultar la sección Ejecutar Apache como un + servicio y los usuario de Windows 9x y ME deben consultar Ejecutar Apache como una + Aplicación de Consola para obtener información + sobre como controlar Apache en esas plataformas.

Introducción
Parar Ahora Apache
Reinicio "Graceful" o elegante
Reiniciar Apache
Apándice: señales y race conditions

Consulte también

Introducción

+ +

Para parar y reiniciar Apache, hay que enviar la señal + apropiada al proceso padre httpd que se está + ejecutando. Hay dos maneras de enviar estas señales. En + primer lugar, puede usar el comando de Unix kill que + envía señales directamente a los procesos. Puede que + tenga varios procesos httpd ejecutándose en su + sistema, pero las señales deben enviarse solamente al proceso + padre, cuyo PID está especificado en la directiva PidFile. Esto quiere decir que no + debe necesitar enviar señales a ningún proceso excepto + al proceso padre. Hay tres señales que puede enviar al + proceso padre: + TERM, + USR1 + HUP, y + WINCH, + que van a ser descritas a continuación.

+ +

Para enviar una señal al proceso padre debe escribir un + comando como el que se muestra en el ejemplo:

+ +

kill -TERM `cat /usr/local/apache2/logs/httpd.pid`

+ +

La segunda manera de enviar señales a los procesos + httpd es usando las opciones de línea de + comandos -k: stop, restart, + y graceful y graceful-stop, como se + muestra más abajo. Estas opciones se le pueden pasar al binario + httpd, pero se recomienda que se pasen al + script de control apachectl, que a su vez los + pasará a httpd.

+ +

Después de haber enviado las señales que desee a + httpd, puede ver como progresa el proceso + escribiendo:

+ +

tail -f /usr/local/apache2/logs/error_log

+ +

Modifique estos ejemplos para que coincidan con la + configuración que tenga especificada en las directivas + ServerRoot y PidFile en su fichero principal de + configuración.

Parar Ahora Apache

+ +

Señal: TERM: apachectl -k stop

+ +

Enviar las señales TERM o stop + al proceso padre hace que se intenten eliminar todos los procesos + hijos inmediatamente. Esto puede tardar algunos segundos. Una vez que hayan + terminado todos los procesos hijos, terminará el proceso padre. + Cualquier petición en proceso terminará inmediatamente, y + ninguna petición posterior será + atendida.

Reinicio "Graceful" o elegante

+ +

Señal: USR1: apachectl -k graceful

+ +

Las señales USR1 o graceful + hacen que el proceso padre indique a sus hijos que + terminen después de servir la petición que están + atendiendo en ese momento (o de inmediato si no están + sirviendo ninguna petición). El proceso padre lee de nuevo + sus ficheros de configuración y vuelve a abrir sus ficheros + log. Conforme cada hijo va terminando, el proceso padre lo va + sustituyendo con un hijo de una nueva generación con + la nueva configuración, que empiezan a servir peticiones + inmediatamente.

+ +

En algunas plataformas que no permiten usar + USR1 para reinicios graceful, puede usarse una + señal alternativa (como WINCH). También puede + usar apachectl graceful y el script de control + enviará la señal adecuada para su plataforma.

+ +

Apache está diseñado para respetar en todo momento la + directiva de control de procesos de los MPM, así como para + que el número de procesos e hilos disponibles para servir a + los clientes se mantenga en los valores adecuados durante el + proceso de reinicio. Aún más, está diseñado + para respetar la directiva StartServers de la siguiente + manera: si después de al menos un segundo el nuevo hijo de la + directiva StartServers + no ha sido creado, entonces crea los suficientes para que se atienda + el trabajo que queda por hacer. Así, se intenta mantener + tanto el número de hijos adecuado para el trabajo que el + servidor tenga en ese momento, como respetar la configuración + determinada por los parámetros de la directiva + StartServers.

+ +

Los usuarios del módulo mod_status + notarán que las estadísticas del servidor + no se ponen a cero cuando se usa la señal + USR1. Apache fue escrito tanto para minimizar el + tiempo en el que el servidor no puede servir nuevas peticiones + (que se pondrán en cola por el sistema operativo, de modo que + se no se pierda ningún evento), como para respetar sus + parámetros de ajuste. Para hacer esto, tiene que guardar el + scoreboard usado para llevar el registro de los procesos + hijo a través de las distintas generaciones.

+ +

El mod_status también usa una G para indicar + que esos hijos están todavía sirviendo peticiones + previas al reinicio graceful.

+ +

Actualmente no existe ninguna manera de que un script con un + log de rotación usando USR1 sepa con seguridad + que todos los hijos que se registraron en el log con anterioridad + al reinicio han terminado. Se aconseja que se use un retardo + adecuado después de enviar la señal USR1 + antes de hacer nada con el log antiguo. Por ejemplo, si la mayor + parte las visitas que recibe de usuarios que tienen conexiones de + baja velocidad tardan menos de 10 minutos en completarse, entonces + espere 15 minutos antes de hacer nada con el log antiguo.

+ +

Si su fichero de configuración tiene errores cuando + haga el reinicio, entonces el proceso padre no se reiniciará + y terminará con un error. En caso de un reinicio graceful, + también dejará a los procesos hijo ejecutándose mientras + existan. (Estos son los hijos de los que se está saliendo de + forma graceful y que están sirviendo sus últimas + peticiones.) Esto provocará problemas si intenta reiniciar el + servidor no será posible conectarse a la lista de puertos + de escucha. Antes de reiniciar, puede comprobar que la sintaxis de + sus ficheros de configuración es correcta con la opción de + línea de comandos -t (consulte httpd). + No obstante, esto no + garantiza que el servidor se reinicie correctamente. Para + comprobar que no hay errores en los ficheros de + configuración, puede intentar iniciar httpd con + un usuario diferente a root. Si no hay errores, intentará + abrir sus sockets y logs y fallará porque el usuario no es + root (o porque el httpd que se está ejecutando + en ese momento ya está conectado a esos puertos). Si falla + por cualquier otra razón, entonces casi seguro que hay + algún error en alguno de los ficheros de configuración y + debe corregir ese o esos errores antes de hacer un reinicio + graceful.

Reiniciar Apache

+ +

Señal: HUP: apachectl -k restart

+ +

El envío de las señales HUP o + restart al proceso padre hace que los procesos hijo + terminen como si le enviáramos la señal + TERM, para eliminar el proceso padre. La diferencia + está en que estas señales vuelven a leer los archivos de + configuración y vuelven a abrir los ficheros log. Se genera + un nuevo conjunto de hijos y se continúa sirviendo + peticiones.

+ +

Los usuarios del módulo mod_status + notarán que las estadísticas del servidor se ponen a + cero cuando se envía la señal HUP.

+ +

Si su fichero de configuración contiene errores, cuando +intente reiniciar, el proceso padre del servidor no se +reiniciará, sino que terminará con un error. Consulte +más arriba cómo puede solucionar este problema.

Apándice: señales y race conditions

+ +

Con anterioridad a la versión de Apache 1.2b9 había + varias race conditions implicadas en las señales + para parar y reiniciar procesos (una descripción sencilla de + una race condition es: un problema relacionado con el momento en + que suceden las cosas, como si algo sucediera en momento en que no + debe, y entonces el resultado esperado no se corresponde con el + obtenido). Para aquellas arquitecturas que tienen el conjunto de + características "adecuadas", se han eliminado tantas race + conditions como ha sido posible. Pero hay que tener en cuenta que + todavía existen race conditions en algunas arquitecturas.

+ +

En las arquitecturas que usan un ScoreBoardFile en disco, existe la + posibilidad de que se corrompan los scoreboards. Esto puede hacer + que se produzca el error "bind: Address already in use" + (despuás de usarHUP) o el error "long lost child + came home!" (despuás de usar USR1). En el + primer caso se trata de un error irrecuperable, mientras que en el + segundo, solo ocurre que el servidor pierde un slot del + scoreboard. Por lo tanto, sería aconsejable usar reinicios + graceful, y solo hacer reinicios normales de forma + ocasional. Estos problemas son bastante complicados de solucionar, + pero afortunadamente casi ninguna arquitectura necesita un fichero + scoreboard. Consulte la documentación de la directiva + ScoreBoardFile para ver + las arquitecturas que la usan.

+ +

Todas las arquitecturas tienen una pequeña race condition + en cada proceso hijo implicada en la segunda y subsiguientes + peticiones en una conexión HTTP persistente + (KeepAlive). Puede ser que el servidor termine después de + leer la línea de petición pero antes de leer cualquiera + de las cabeceras de petición. Hay una solución que fue + descubierta demasiado tarde para la incluirla en versión + 1.2. En teoría esto no debe suponer ningún problema porque el + cliente KeepAlive ha de esperar que estas cosas pasen debido a los + retardos de red y a los timeouts que a veces dan los + servidores. En la practica, parece que no afecta a nada más + -- en una sesión de pruebas, un servidor se reinició + veinte veces por segundo y los clientes pudieron navegar sin + problemas por el sitio web sin encontrar problemas ni para + descargar una sola imagen ni encontrar un solo enlace roto.

Idiomas disponibles: de | + en | + es | + fr | + ja | + ko | + tr

Comentarios

- \ No newline at end of file +//--> + -- 2.40.0

Uso de los Handlers en Apache

Consulte también

Uso de los Handlers en Apache

Consulte también

Iniciar Apache

Consulte también

Iniciar Apache

Consulte también

Funcionalidad Básica de Apache

Directivas

Bugfix checklist

Consulte también

Consulte también

Consulte también

Consulte también

Note

Consulte también

Only available in <Directory> sections

Consulte también

Consulte también

Consulte también

Consulte también

Compatability

Trailing Slash

Consulte también

Consulte también

Consulte también

Consulte también

Example

Consulte también

Example

Example

Example

Note

Consulte también

Simple example

Example (somewhat similar to default format)

Example (similar to the 2.2.x format)

Advanced example with request/connection log IDs

Consulte también

Warning

Server Side Includes

Consulte también

Consulte también

Consulte también

Consulte también

Consulte también

Consulte también

Example

Warning

Warning

Warning

When to use <Location>

Note about / (slash)

Consulte también

Consulte también

Note

Consulte también

Supported modules

Warning

Warning

Security

Warning

Warning

Security

Argument to <VirtualHost> - directive

Consulte también

Note

When to use `<Location>`

Argument to `<VirtualHost>` - directive