You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by lg...@apache.org on 2016/06/08 11:37:09 UTC
svn commit: r1747381 [2/3] - in /httpd/httpd/trunk/docs/manual/mod:
core.html.es core.xml.es
Modified: httpd/httpd/trunk/docs/manual/mod/core.html.es
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/core.html.es?rev=1747381&r1=1747380&r2=1747381&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/core.html.es (original)
+++ httpd/httpd/trunk/docs/manual/mod/core.html.es Wed Jun 8 11:37:09 2016
@@ -1,4459 +1,4452 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" lang="es" xml:lang="es"><head>
-<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" />
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="es" xml:lang="es"><head>
+<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" />
<!--
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
This file is generated from xml source: DO NOT EDIT
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
- -->
-<title>core - Servidor HTTP Apache Versi�n 2.5</title>
-<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
-<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
-<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
-<script src="../style/scripts/prettify.min.js" type="text/javascript">
-</script>
-
-<link href="../images/favicon.ico" rel="shortcut icon" /></head>
-<body>
-<div id="page-header">
-<p class="menu"><a href="../mod/">M�dulos</a> | <a href="../mod/quickreference.html">Directivas</a> | <a href="http://wiki.apache.org/httpd/FAQ">Preguntas Frecuentes</a> | <a href="../glossary.html">Glosario</a> | <a href="../sitemap.html">Mapa del sitio web</a></p>
-<p class="apache">Versi�n 2.5 del Servidor HTTP Apache</p>
-<img alt="" src="../images/feather.png" /></div>
-<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div>
-<div id="path">
-<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">Servidor HTTP</a> > <a href="http://httpd.apache.org/docs/">Documentaci�n</a> > <a href="../">Versi�n 2.5</a> > <a href="./">M�dulos</a></div>
-<div id="page-content">
-<div id="preamble"><h1>Funcionalidad B�sica de Apache</h1>
-<div class="toplang">
-<p><span>Idiomas disponibles: </span><a href="../de/mod/core.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> |
-<a href="../en/mod/core.html" hreflang="en" rel="alternate" title="English"> en </a> |
-<a href="../es/mod/core.html" title="Espa�ol"> es </a> |
-<a href="../fr/mod/core.html" hreflang="fr" rel="alternate" title="Fran�ais"> fr </a> |
-<a href="../ja/mod/core.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
-<a href="../tr/mod/core.html" hreflang="tr" rel="alternate" title="T�rk�e"> tr </a></p>
-</div>
-<div class="outofdate">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.</div>
-<table class="module"><tr><th><a href="module-dict.html#Description">Descripci�n:</a></th><td>Funcionalides b�sicas del Servidor HTTP Apache que siempre est�n presentes.</td></tr>
-<tr><th><a href="module-dict.html#Status">Estado:</a></th><td>Core</td></tr></table>
-</div>
-<div id="quickview"><h3 class="directives">Directivas</h3>
-<ul id="toc">
-<li><img alt="" src="../images/down.gif" /> <a href="#acceptfilter">AcceptFilter</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#acceptpathinfo">AcceptPathInfo</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#accessfilename">AccessFileName</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#adddefaultcharset">AddDefaultCharset</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#allowencodedslashes">AllowEncodedSlashes</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#allowoverride">AllowOverride</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#allowoverridelist">AllowOverrideList</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#asyncfilter">AsyncFilter</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#cgimapextension">CGIMapExtension</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#cgipassauth">CGIPassAuth</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#cgivar">CGIVar</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#contentdigest">ContentDigest</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#defaultruntimedir">DefaultRuntimeDir</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#defaulttype">DefaultType</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#define">Define</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#directory"><Directory></a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#directorymatch"><DirectoryMatch></a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#documentroot">DocumentRoot</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#else"><Else></a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#elseif"><ElseIf></a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#enablemmap">EnableMMAP</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#enablesendfile">EnableSendfile</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#error">Error</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#errordocument">ErrorDocument</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#errorlog">ErrorLog</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#errorlogformat">ErrorLogFormat</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#extendedstatus">ExtendedStatus</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#fileetag">FileETag</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#files"><Files></a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#filesmatch"><FilesMatch></a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#forcetype">ForceType</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#gprofdir">GprofDir</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#hostnamelookups">HostnameLookups</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#if"><If></a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#ifdefine"><IfDefine></a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#ifmodule"><IfModule></a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#include">Include</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#includeoptional">IncludeOptional</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#keepalive">KeepAlive</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#keepalivetimeout">KeepAliveTimeout</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#limit"><Limit></a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#limitexcept"><LimitExcept></a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#limitinternalrecursion">LimitInternalRecursion</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#limitrequestbody">LimitRequestBody</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#limitrequestfields">LimitRequestFields</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#limitrequestfieldsize">LimitRequestFieldSize</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#limitrequestline">LimitRequestLine</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#limitxmlrequestbody">LimitXMLRequestBody</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#location"><Location></a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#locationmatch"><LocationMatch></a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#loglevel">LogLevel</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#logleveloverride">LogLevelOverride</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#maxkeepaliverequests">MaxKeepAliveRequests</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#maxrangeoverlaps">MaxRangeOverlaps</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#maxrangereversals">MaxRangeReversals</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#maxranges">MaxRanges</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#mergetrailers">MergeTrailers</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#mutex">Mutex</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#namevirtualhost">NameVirtualHost</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#options">Options</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#protocol">Protocol</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#protocols">Protocols</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#protocolshonororder">ProtocolsHonorOrder</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#qualifyredirecturl">QualifyRedirectURL</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#registerhttpmethod">RegisterHttpMethod</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#rlimitcpu">RLimitCPU</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#rlimitmem">RLimitMEM</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#rlimitnproc">RLimitNPROC</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#scriptinterpretersource">ScriptInterpreterSource</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#seerequesttail">SeeRequestTail</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#serveradmin">ServerAdmin</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#serveralias">ServerAlias</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#servername">ServerName</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#serverpath">ServerPath</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#serverroot">ServerRoot</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#serversignature">ServerSignature</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#servertokens">ServerTokens</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#sethandler">SetHandler</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#setinputfilter">SetInputFilter</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#setoutputfilter">SetOutputFilter</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#timeout">TimeOut</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#traceenable">TraceEnable</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#undefine">UnDefine</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#usecanonicalname">UseCanonicalName</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#virtualhost"><VirtualHost></a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#warning">Warning</a></li>
-</ul>
-<h3>Bugfix checklist</h3><ul class="seealso"><li><a href="https://www.apache.org/dist/httpd/CHANGES_2.4">httpd changelog</a></li><li><a href="https://bz.apache.org/bugzilla/buglist.cgi?bug_status=__open__&list_id=144532&product=Apache%20httpd-2&query_format=specific&order=changeddate%20DESC%2Cpriority%2Cbug_severity&component=core">Known issues</a></li><li><a href="https://bz.apache.org/bugzilla/enter_bug.cgi?product=Apache%20httpd-2&component=core">Report a bug</a></li></ul><h3>Consulte tambi�n</h3>
-<ul class="seealso">
-<li><a href="#comments_section">Comentarios</a></li></ul></div>
-
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="AcceptFilter" id="AcceptFilter">AcceptFilter</a> <a name="acceptfilter" id="acceptfilter">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Configura mejoras para un Protocolo de Escucha de Sockets</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AcceptFilter <var>protocol</var> <var>accept_filter</var></code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Disponible en Apache httpd 2.1.5 y posteriores.
-En Windows desde Apache httpd 2.3.3 y posteriores.</td></tr>
-</table>
- <p>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
- <a href="http://www.freebsd.org/cgi/man.cgi?query=accept_filter&sektion=9">
- Accept Filters</a> sobre FreeBSD, <code>TCP_DEFER_ACCEPT</code> sobre Linux,
- y AcceptEx() sobre Windows.</p>
-
- <p>El uso de <code>none</code> 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 <code>ftp:</code> o <code>nntp</code>:</p>
- <div class="example"><p><code>AcceptFilter nntp none</code></p></div>
-
- <p>Los nombres de protocolo por defecto son <code>https</code> para el puerto 443
- y <code>http</code> para todos los dem�s puertos. Para especificar que se est�
- utilizando otro protocolo con un puerto escuchando, a�ade el argumento <var>protocol</var>
- a la directiva <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>.</p>
-
- <p>Sobre FreeBDS los valores por defecto:</p>
- <div class="example"><p><code>
- AcceptFilter http httpready <br />
- AcceptFilter https dataready
- </code></p></div>
-
- <p>El filtro <code>httpready</code> 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
- <a href="http://www.freebsd.org/cgi/man.cgi?query=accf_http&sektion=9">
- accf_http(9)</a> para m�s detalles. Puesto que las peticiones HTTPS
- est�n encriptadas, s�lo se utiliza el filtro
- <a href="http://www.freebsd.org/cgi/man.cgi?query=accf_data&sektion=9">accf_data(9)</a>.</p>
-
- <p>Sobre Linux los valores por defecto son:</p>
- <div class="example"><p><code>
- AcceptFilter http data <br />
- AcceptFilter https data
- </code></p></div>
-
- <p>En Linux, <code>TCP_DEFER_ACCEPT</code> no soporta el buffering en peticiones http.
- Cualquier valor adem�s de <code>none</code> habilitar�
- <code>TCP_DEFER_ACCEPT</code> en ese socket. Para m�s detalles
- ver la p�gina man de Linux
- <a href="http://homepages.cwi.nl/~aeb/linux/man2html/man7/tcp.7.html">
- tcp(7)</a>.</p>
-
- <p>Sobre Windows los valores por defecto son:</p>
- <div class="example"><p><code>
- AcceptFilter http data <br />
- AcceptFilter https data
- </code></p></div>
-
- <p>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 conexciones. <code>data</code> 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().
- <code>connect</code> utiliza la API AcceptEx() API, y recupera tambi�n
- las direcciones de red, pero a diferencia de <code>none</code>
- la opci�n <code>connect</code> no espera a la transmisi�n inicial de los datos.</p>
-
- <p>Sobre Windows, <code>none</code> prefiere 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.</p>
-
-
-<h3>Consulte tambi�n</h3>
-<ul>
-<li><code class="directive">Protocol</code></li>
-</ul>
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="AcceptPathInfo" id="AcceptPathInfo">AcceptPathInfo</a> <a name="acceptpathinfo" id="acceptpathinfo">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Los recursos aceptan informaci�n sobre su ruta</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AcceptPathInfo On|Off|Default</code></td></tr>
-<tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AcceptPathInfo Default</code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
-<tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Disponible en Apache httpd 2.0.30 y posteriores</td></tr>
-</table>
-
- <p>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 <code>PATH_INFO</code>.</p>
-
- <p>Por ejemplo, asumamos que la ubicaci�n <code>/test/</code> apunta a
- un directorio que contiene �nicamente el fichero
- <code>here.html</code>. Entonces, las peticiones tanto para
- <code>/test/here.html/more</code> como para
- <code>/test/nothere.html/more</code> recogen
- <code>/more</code> como <code>PATH_INFO</code>.</p>
-
- <p>Los tres posibles argumentos para la directiva
- <code class="directive">AcceptPathInfo</code> son los siguientes:</p>
- <dl>
- <dt><code>Off</code></dt><dd>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
- <code>/test/here.html/more</code> en el ejemplo anterior devolver�
- un error 404 NOT FOUND.</dd>
-
- <dt><code>On</code></dt><dd>Una petici�n ser� aceptada si una
- ruta principal de acceso se corresponde con un fichero que existe. El ejemplo
- anterior <code>/test/here.html/more</code> ser� aceptado si
- <code>/test/here.html</code> corresponde a un fichero v�lido.</dd>
-
- <dt><code>Default</code></dt><dd>La gesti�n de las peticiones
- con informaci�n de ruta est� determinada por el <a href="../handler.html">controlador</a> responsable de la petici�n.
- El controlador principal para para ficheros normales rechaza por defecto
- peticiones <code>PATH_INFO</code>. Los controladores que sirven scripts, tales como <a href="mod_cgi.html">cgi-script</a> e <a href="mod_isapi.html">isapi-handler</a>, normalmente aceptan
- <code>PATH_INFO</code> por defecto.</dd>
- </dl>
-
- <p>El objetivo principal de la directiva <code>AcceptPathInfo</code>
- es permitirte sobreescribir la opci�n del controlador
- de aceptar or rechazar <code>PATH_INFO</code>. Este tipo de sobreescritura se necesita,
- por ejemplo, cuando utilizas un <a href="../filter.html">filtro</a>, tal como
- <a href="mod_include.html">INCLUDES</a>, para generar contenido
- basado en <code>PATH_INFO</code>. El controlador principal normalmente rechazar�a
- la petici�n, de modo que puedes utilizar la siguiente configuraci�n para habilitarla
- como script:</p>
-
- <div class="example"><p><code>
- <Files "mypaths.shtml"><br />
- <span class="indent">
- Options +Includes<br />
- SetOutputFilter INCLUDES<br />
- AcceptPathInfo On<br />
- </span>
- </Files>
- </code></p></div>
-
-
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="AccessFileName" id="AccessFileName">AccessFileName</a> <a name="accessfilename" id="accessfilename">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Nombre del fichero distribuido de configuraci�n</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AccessFileName <var>filename</var> [<var>filename</var>] ...</code></td></tr>
-<tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AccessFileName .htaccess</code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-</table>
- <p>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 <a href="#allowoverride">habilitados para ese
- directorio</a>. Por ejemplo:</p>
-
- <div class="example"><p><code>
- AccessFileName .acl
- </code></p></div>
-
- <p>antes de servir el documento
- <code>/usr/local/web/index.html</code>, el servidor leer�
- <code>/.acl</code>, <code>/usr/.acl</code>,
- <code>/usr/local/.acl</code> and <code>/usr/local/web/.acl</code>
- para las directivas, salvo que est�n deshabilitadas with</p>
-
- <div class="example"><p><code>
- <Directory /><br />
- <span class="indent">
- AllowOverride None<br />
- </span>
- </Directory>
- </code></p></div>
-
-<h3>Consulte tambi�n</h3>
-<ul>
-<li><code class="directive"><a href="#allowoverride">AllowOverride</a></code></li>
-<li><a href="../configuring.html">Configuration Files</a></li>
-<li><a href="../howto/htaccess.html">.htaccess Files</a></li>
-</ul>
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="AddDefaultCharset" id="AddDefaultCharset">AddDefaultCharset</a> <a name="adddefaultcharset" id="adddefaultcharset">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Default charset parameter to be added when a response
-content-type is <code>text/plain</code> or <code>text/html</code></td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AddDefaultCharset On|Off|<var>charset</var></code></td></tr>
-<tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AddDefaultCharset Off</code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
-<tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-</table>
- <p>This directive specifies a default value for the media type
- charset parameter (the name of a character encoding) to be added
- to a response if and only if the response's content-type is either
- <code>text/plain</code> or <code>text/html</code>. This should override
- any charset specified in the body of the response via a <code>META</code>
- element, though the exact behavior is often dependent on the user's client
- configuration. A setting of <code>AddDefaultCharset Off</code>
- disables this functionality. <code>AddDefaultCharset On</code> enables
- a default charset of <code>iso-8859-1</code>. Any other value is assumed
- to be the <var>charset</var> to be used, which should be one of the
- <a href="http://www.iana.org/assignments/character-sets">IANA registered
- charset values</a> for use in Internet media types (MIME types).
- For example:</p>
-
- <div class="example"><p><code>
- AddDefaultCharset utf-8
- </code></p></div>
-
- <p><code class="directive">AddDefaultCharset</code> should only be used when all
- of the text resources to which it applies are known to be in that
- character encoding and it is too inconvenient to label their charset
- individually. One such example is to add the charset parameter
- to resources containing generated content, such as legacy CGI
- scripts, that might be vulnerable to cross-site scripting attacks
- due to user-provided data being included in the output. Note, however,
- that a better solution is to just fix (or delete) those scripts, since
- setting a default charset does not protect users that have enabled
- the "auto-detect character encoding" feature on their browser.</p>
-
-<h3>Consulte tambi�n</h3>
-<ul>
-<li><code class="directive"><a href="../mod/mod_mime.html#addcharset">AddCharset</a></code></li>
-</ul>
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="AllowEncodedSlashes" id="AllowEncodedSlashes">AllowEncodedSlashes</a> <a name="allowencodedslashes" id="allowencodedslashes">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Determines whether encoded path separators in URLs are allowed to
-be passed through</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AllowEncodedSlashes On|Off</code></td></tr>
-<tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AllowEncodedSlashes Off</code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache httpd 2.0.46 and later</td></tr>
-</table>
- <p>The <code class="directive">AllowEncodedSlashes</code> directive allows URLs
- which contain encoded path separators (<code>%2F</code> for <code>/</code>
- and additionally <code>%5C</code> for <code>\</code> on according systems)
- to be used. Normally such URLs are refused with a 404 (Not found) error.</p>
-
- <p>Turning <code class="directive">AllowEncodedSlashes</code> <code>On</code> is
- mostly useful when used in conjunction with <code>PATH_INFO</code>.</p>
-
- <div class="note"><h3>Note</h3>
- <p>Allowing encoded slashes does <em>not</em> imply <em>decoding</em>.
- Occurrences of <code>%2F</code> or <code>%5C</code> (<em>only</em> on
- according systems) will be left as such in the otherwise decoded URL
- string.</p>
- </div>
-
-<h3>Consulte tambi�n</h3>
-<ul>
-<li><code class="directive"><a href="#acceptpathinfo">AcceptPathInfo</a></code></li>
-</ul>
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="AllowOverride" id="AllowOverride">AllowOverride</a> <a name="allowoverride" id="allowoverride">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Types of directives that are allowed in
-<code>.htaccess</code> files</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AllowOverride All|None|<var>directive-type</var>
-[<var>directive-type</var>] ...</code></td></tr>
-<tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AllowOverride None (2.3.9 and later), AllowOverride All (2.3.8 and earlier)</code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-</table>
- <p>When the server finds an <code>.htaccess</code> file (as
- specified by <code class="directive"><a href="#accessfilename">AccessFileName</a></code>)
- it needs to know which directives declared in that file can override
- earlier configuration directives.</p>
-
- <div class="note"><h3>Only available in <Directory> sections</h3>
- <code class="directive">AllowOverride</code> is valid only in
- <code class="directive"><a href="#directory"><Directory></a></code>
- sections specified without regular expressions, not in <code class="directive"><a href="#location"><Location></a></code>, <code class="directive"><a href="#directorymatch"><DirectoryMatch></a></code> or
- <code class="directive"><a href="#files"><Files></a></code> sections.
- </div>
-
- <p>When this directive is set to <code>None</code>, then
- <a href="#accessfilename">.htaccess</a> files are completely ignored.
- In this case, the server will not even attempt to read
- <code>.htaccess</code> files in the filesystem.</p>
-
- <p>When this directive is set to <code>All</code>, then any
- directive which has the .htaccess <a href="directive-dict.html#Context">Context</a> is allowed in
- <code>.htaccess</code> files.</p>
-
- <p>The <var>directive-type</var> can be one of the following
- groupings of directives.</p>
-
- <dl>
- <dt>AuthConfig</dt>
-
- <dd>
-
- Allow use of the authorization directives (<code class="directive"><a href="../mod/mod_authn_dbm.html#authdbmgroupfile">AuthDBMGroupFile</a></code>,
- <code class="directive"><a href="../mod/mod_authn_dbm.html#authdbmuserfile">AuthDBMUserFile</a></code>,
- <code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code>,
- <code class="directive"><a href="../mod/mod_authn_core.html#authname">AuthName</a></code>,
- <code class="directive"><a href="../mod/mod_authn_core.html#authtype">AuthType</a></code>, <code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code>, <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>, <em>etc.</em>).</dd>
-
- <dt>FileInfo</dt>
-
- <dd>
- Allow use of the directives controlling document types
- (<code class="directive"><a href="#errordocument">ErrorDocument</a></code>,
- <code class="directive"><a href="#forcetype">ForceType</a></code>,
- <code class="directive"><a href="../mod/mod_negotiation.html#languagepriority">LanguagePriority</a></code>,
- <code class="directive"><a href="#sethandler">SetHandler</a></code>,
- <code class="directive"><a href="#setinputfilter">SetInputFilter</a></code>,
- <code class="directive"><a href="#setoutputfilter">SetOutputFilter</a></code>, and
- <code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code> Add* and Remove* directives),
- document meta data (<code class="directive"><a href="../mod/mod_headers.html#header">Header</a></code>, <code class="directive"><a href="../mod/mod_headers.html#requestheader">RequestHeader</a></code>, <code class="directive"><a href="../mod/mod_setenvif.html#setenvif">SetEnvIf</a></code>, <code class="directive"><a href="../mod/mod_setenvif.html#setenvifnocase">SetEnvIfNoCase</a></code>, <code class="directive"><a href="../mod/mod_setenvif.html#browsermatch">BrowserMatch</a></code>, <code class="directive"><a href="../mod/mod_usertrack.html#cookieexpires">CookieExpires</a></code>, <code class="directive"><a href="../mod/mod_usertrack.html#cookiedomain">CookieDomain</a></code>, <code class="directive"><a href="../mod/mod_usertrack.html#cookiestyle">CookieStyle</a></code>, <code class="directive"><a href="../mod/mod_usertrack.html#cookietracking">CookieTracking</a></code>, <code class="directive"><a href="../mod/mod_usertrack.html#cookiename">CookieName</a></code>),
- <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> directives <code class="directive"><a href="../mod/mod_rewrite.html#rewriteengine">RewriteEngine</a></code>, <code class="directive"><a href="../mod/mod_rewrite.html#rewriteoptions">RewriteOptions</a></code>, <code class="directive"><a href="../mod/mod_rewrite.html#rewritebase">RewriteBase</a></code>, <code class="directive"><a href="../mod/mod_rewrite.html#rewritecond">RewriteCond</a></code>, <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code>) and
- <code class="directive"><a href="../mod/mod_actions.html#action">Action</a></code> from
- <code class="module"><a href="../mod/mod_actions.html">mod_actions</a></code>.
- </dd>
-
- <dt>Indexes</dt>
-
- <dd>
- Allow use of the directives controlling directory indexing
- (<code class="directive"><a href="../mod/mod_autoindex.html#adddescription">AddDescription</a></code>,
- <code class="directive"><a href="../mod/mod_autoindex.html#addicon">AddIcon</a></code>, <code class="directive"><a href="../mod/mod_autoindex.html#addiconbyencoding">AddIconByEncoding</a></code>,
- <code class="directive"><a href="../mod/mod_autoindex.html#addiconbytype">AddIconByType</a></code>,
- <code class="directive"><a href="../mod/mod_autoindex.html#defaulticon">DefaultIcon</a></code>, <code class="directive"><a href="../mod/mod_dir.html#directoryindex">DirectoryIndex</a></code>, <code class="directive"><a href="../mod/mod_autoindex.html#fancyindexing">FancyIndexing</a></code>, <code class="directive"><a href="../mod/mod_autoindex.html#headername">HeaderName</a></code>, <code class="directive"><a href="../mod/mod_autoindex.html#indexignore">IndexIgnore</a></code>, <code class="directive"><a href="../mod/mod_autoindex.html#indexoptions">IndexOptions</a></code>, <code class="directive"><a href="../mod/mod_autoindex.html#readmename">ReadmeName</a></code>,
- <em>etc.</em>).</dd>
-
- <dt>Limit</dt>
-
- <dd>
- Allow use of the directives controlling host access (<code class="directive"><a href="../mod/mod_authz_host.html#allow">Allow</a></code>, <code class="directive"><a href="../mod/mod_authz_host.html#deny">Deny</a></code> and <code class="directive"><a href="../mod/mod_authz_host.html#order">Order</a></code>).</dd>
-
- <dt>Options[=<var>Option</var>,...]</dt>
-
- <dd>
- Allow use of the directives controlling specific directory
- features (<code class="directive"><a href="#options">Options</a></code> and
- <code class="directive"><a href="../mod/mod_include.html#xbithack">XBitHack</a></code>).
- An equal sign may be given followed by a comma (but no spaces)
- separated lists of options that may be set using the <code class="directive"><a href="#options">Options</a></code> command.</dd>
- </dl>
-
- <p>Example:</p>
-
- <div class="example"><p><code>
- AllowOverride AuthConfig Indexes
- </code></p></div>
-
- <p>In the example above all directives that are neither in the group
- <code>AuthConfig</code> nor <code>Indexes</code> cause an internal
- server error.</p>
-
- <div class="note"><p>For security and performance reasons, do not set
- <code>AllowOverride</code> to anything other than <code>None</code>
- in your <code><Directory /></code> block. Instead, find (or
- create) the <code><Directory></code> block that refers to the
- directory where you're actually planning to place a
- <code>.htaccess</code> file.</p>
- </div>
-
-<h3>Consulte tambi�n</h3>
-<ul>
-<li><code class="directive"><a href="#accessfilename">AccessFileName</a></code></li>
-<li><a href="../configuring.html">Configuration Files</a></li>
-<li><a href="../howto/htaccess.html">.htaccess Files</a></li>
-</ul>
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="AllowOverrideList" id="AllowOverrideList">AllowOverrideList</a> <a name="allowoverridelist" id="allowoverridelist">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Individual directives that are allowed in
-<code>.htaccess</code> files</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AllowOverrideList None|<var>directive</var>
-[<var>directive-type</var>] ...</code></td></tr>
-<tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AllowOverrideList None</code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-</table><p>The documentation for this directive has
- not been translated yet. Please have a look at the English
- version.</p><h3>Consulte tambi�n</h3>
-<ul>
-<li><code class="directive"><a href="#accessfilename">AccessFileName</a></code></li>
-<li><code class="directive"><a href="#allowoverride">AllowOverride</a></code></li>
-<li><a href="../configuring.html">Configuration Files</a></li>
-<li><a href="../howto/htaccess.html">.htaccess Files</a></li>
-</ul>
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="AsyncFilter" id="AsyncFilter">AsyncFilter</a> <a name="asyncfilter" id="asyncfilter">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Set the minimum filter type eligible for asynchronous handling</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AsyncFilter request|connection|network</code></td></tr>
-<tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AsyncFilter request</code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Only available from Apache 2.5.0 and later.</td></tr>
-</table><p>The documentation for this directive has
- not been translated yet. Please have a look at the English
- version.</p></div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="CGIMapExtension" id="CGIMapExtension">CGIMapExtension</a> <a name="cgimapextension" id="cgimapextension">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Technique for locating the interpreter for CGI
-scripts</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>CGIMapExtension <var>cgi-path</var> <var>.extension</var></code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
-<tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>NetWare only</td></tr>
-</table>
- <p>This directive is used to control how Apache httpd finds the
- interpreter used to run CGI scripts. For example, setting
- <code>CGIMapExtension sys:\foo.nlm .foo</code> will
- cause all CGI script files with a <code>.foo</code> extension to
- be passed to the FOO interpreter.</p>
-
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="CGIPassAuth" id="CGIPassAuth">CGIPassAuth</a> <a name="cgipassauth" id="cgipassauth">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Enables passing HTTP authorization headers to scripts as CGI
-variables</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>CGIPassAuth On|Off</code></td></tr>
-<tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>CGIPassAuth Off</code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
-<tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>AuthConfig</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.4.13 and later</td></tr>
-</table><p>The documentation for this directive has
- not been translated yet. Please have a look at the English
- version.</p></div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="CGIVar" id="CGIVar">CGIVar</a> <a name="cgivar" id="cgivar">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Controls how some CGI variables are set</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>CGIVar <var>variable</var> <var>rule</var></code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
-<tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.4.21 and later</td></tr>
-</table><p>The documentation for this directive has
- not been translated yet. Please have a look at the English
- version.</p></div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="ContentDigest" id="ContentDigest">ContentDigest</a> <a name="contentdigest" id="contentdigest">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Enables the generation of <code>Content-MD5</code> HTTP Response
-headers</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ContentDigest On|Off</code></td></tr>
-<tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ContentDigest Off</code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
-<tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>Options</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-</table>
- <p>This directive enables the generation of
- <code>Content-MD5</code> headers as defined in RFC1864
- respectively RFC2616.</p>
-
- <p>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.</p>
-
- <p>The <code>Content-MD5</code> 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:</p>
-
- <div class="example"><p><code>
- Content-MD5: AuLb7Dp1rqtRtxz2m9kRpA==
- </code></p></div>
-
- <p>Note that this can cause performance problems on your server
- since the message digest is computed on every request (the
- values are not cached).</p>
-
- <p><code>Content-MD5</code> is only sent for documents served
- by the <code class="module"><a href="../mod/core.html">core</a></code>, and not by any module. For example,
- SSI documents, output from CGI scripts, and byte range responses
- do not have this header.</p>
-
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="DefaultRuntimeDir" id="DefaultRuntimeDir">DefaultRuntimeDir</a> <a name="defaultruntimedir" id="defaultruntimedir">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Base directory for the server run-time files</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>DefaultRuntimeDir <var>directory-path</var></code></td></tr>
-<tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>DefaultRuntimeDir DEFAULT_REL_RUNTIMEDIR (logs/)</code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache 2.4.2 and later</td></tr>
-</table><p>The documentation for this directive has
- not been translated yet. Please have a look at the English
- version.</p><h3>Consulte tambi�n</h3>
-<ul>
-<li><a href="../misc/security_tips.html#serverroot">the
- security tips</a> for information on how to properly set
- permissions on the <code class="directive">ServerRoot</code></li>
-</ul>
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="DefaultType" id="DefaultType">DefaultType</a> <a name="defaulttype" id="defaulttype">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>This directive has no effect other than to emit warnings
-if the value is not <code>none</code>. 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.
-</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>DefaultType <var>media-type|none</var></code></td></tr>
-<tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>DefaultType none</code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
-<tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>The argument <code>none</code> is available in Apache httpd 2.2.7 and later. All other choices are DISABLED for 2.3.x and later.</td></tr>
-</table>
- <p>This directive has been disabled. For backwards compatibility
- of configuration files, it may be specified with the value
- <code>none</code>, meaning no default media type. For example:</p>
-
- <div class="example"><p><code>
- DefaultType None
- </code></p></div>
-
- <p><code>DefaultType None</code> is only available in
- httpd-2.2.7 and later.</p>
-
- <p>Use the mime.types configuration file and the
- <code class="directive"><a href="../mod/mod_mime.html#addtype">AddType</a></code> to configure media
- type assignments via file extensions, or the
- <code class="directive"><a href="#forcetype">ForceType</a></code> 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.</p>
-
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="Define" id="Define">Define</a> <a name="define" id="define">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Define the existence of a variable</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Define <var>parameter-name</var></code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-</table>
- <p>Equivalent to passing the <code>-D</code> argument to <code class="program"><a href="../programs/httpd.html">httpd</a></code>.</p>
- <p>This directive can be used to toggle the use of <code class="directive"><a href="#ifdefine"><IfDefine></a></code> sections without needing to alter
- <code>-D</code> arguments in any startup scripts.</p>
-
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="Directory" id="Directory"><Directory></a> <a name="directory" id="directory">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Enclose a group of directives that apply only to the
-named file-system directory, sub-directories, and their contents.</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><Directory <var>directory-path</var>>
-... </Directory></code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-</table>
- <p><code class="directive"><Directory></code> and
- <code></Directory></code> 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. <var>Directory-path</var> is
- either the full path to a directory, or a wild-card string using
- Unix shell-style matching. In a wild-card string, <code>?</code> matches
- any single character, and <code>*</code> matches any sequences of
- characters. You may also use <code>[]</code> character ranges. None
- of the wildcards match a `/' character, so <code><Directory
- /*/public_html></code> will not match
- <code>/home/user/public_html</code>, but <code><Directory
- /home/*/public_html></code> will match. Example:</p>
-
- <div class="example"><p><code>
- <Directory /usr/local/httpd/htdocs><br />
- <span class="indent">
- Options Indexes FollowSymLinks<br />
- </span>
- </Directory>
- </code></p></div>
-
- <div class="note">
- <p>Be careful with the <var>directory-path</var> arguments:
- They have to literally match the filesystem path which Apache httpd uses
- to access the files. Directives applied to a particular
- <code><Directory></code> will not apply to files accessed from
- that same directory via a different path, such as via different symbolic
- links.</p>
- </div>
-
- <p><a class="glossarylink" href="../glossary.html#regex" title="ver glosario">Regular
- expressions</a> can also be used, with the addition of the
- <code>~</code> character. For example:</p>
-
- <div class="example"><p><code>
- <Directory ~ "^/www/.*/[0-9]{3}">
- </code></p></div>
-
- <p>would match directories in <code>/www/</code> that consisted of
- three numbers.</p>
-
- <p>If multiple (non-regular expression) <code class="directive"><Directory></code> 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 <a href="#accessfilename">.htaccess</a> files. For example,
- with</p>
-
- <div class="example"><p><code>
- <Directory /><br />
- <span class="indent">
- AllowOverride None<br />
- </span>
- </Directory><br />
- <br />
- <Directory /home/><br />
- <span class="indent">
- AllowOverride FileInfo<br />
- </span>
- </Directory>
- </code></p></div>
-
- <p>for access to the document <code>/home/web/dir/doc.html</code>
- the steps are:</p>
-
- <ul>
- <li>Apply directive <code>AllowOverride None</code>
- (disabling <code>.htaccess</code> files).</li>
-
- <li>Apply directive <code>AllowOverride FileInfo</code> (for
- directory <code>/home</code>).</li>
-
- <li>Apply any <code>FileInfo</code> directives in
- <code>/home/.htaccess</code>, <code>/home/web/.htaccess</code> and
- <code>/home/web/dir/.htaccess</code> in that order.</li>
- </ul>
-
- <p>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</p>
-
- <div class="example"><p><code>
- <Directory ~ abc$><br />
- <span class="indent">
- # ... directives here ...<br />
- </span>
- </Directory>
- </code></p></div>
-
- <p>the regular expression section won't be considered until after
- all normal <code class="directive"><Directory></code>s and
- <code>.htaccess</code> files have been applied. Then the regular
- expression will match on <code>/home/abc/public_html/abc</code> and
- the corresponding <code class="directive"><Directory></code> will
- be applied.</p>
-
- <p><strong>Note that the default access for
- <code><Directory /></code> is <code>Allow from All</code>.
- 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</strong></p>
-
- <div class="example"><p><code>
- <Directory /><br />
- <span class="indent">
- Order Deny,Allow<br />
- Deny from All<br />
- </span>
- </Directory>
- </code></p></div>
-
- <p><strong>and then override this for directories you
- <em>want</em> accessible. See the <a href="../misc/security_tips.html">Security Tips</a> page for more
- details.</strong></p>
-
- <p>The directory sections occur in the <code>httpd.conf</code> file.
- <code class="directive"><Directory></code> directives
- cannot nest, and cannot appear in a <code class="directive"><a href="#limit"><Limit></a></code> or <code class="directive"><a href="#limitexcept"><LimitExcept></a></code> section.</p>
-
-<h3>Consulte tambi�n</h3>
-<ul>
-<li><a href="../sections.html">How <Directory>,
- <Location> and <Files> sections work</a> for an
- explanation of how these different sections are combined when a
- request is received</li>
-</ul>
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="DirectoryMatch" id="DirectoryMatch"><DirectoryMatch></a> <a name="directorymatch" id="directorymatch">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Enclose directives that apply to
-the contents of file-system directories matching a regular expression.</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><DirectoryMatch <var>regex</var>>
-... </DirectoryMatch></code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-</table>
- <p><code class="directive"><DirectoryMatch></code> and
- <code></DirectoryMatch></code> are used to enclose a group
- of directives which will apply only to the named directory (and the files within),
- the same as <code class="directive"><a href="#directory"><Directory></a></code>.
- However, it takes as an argument a
- <a class="glossarylink" href="../glossary.html#regex" title="ver glosario">regular expression</a>. For example:</p>
-
- <div class="example"><p><code>
- <DirectoryMatch "^/www/(.+/)?[0-9]{3}">
- </code></p></div>
-
- <p>would match directories in <code>/www/</code> that consisted of three
- numbers.</p>
-
- <div class="note"><h3>Compatability</h3>
- Prior to 2.3.9, this directive implicitly applied to sub-directories
- (like <code class="directive"><a href="#directory"><Directory></a></code>) 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.
- </div>
-
- <div class="note"><h3>Trailing Slash</h3>
- 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.
- </div>
-
-<h3>Consulte tambi�n</h3>
-<ul>
-<li><code class="directive"><a href="#directory"><Directory></a></code> for
-a description of how regular expressions are mixed in with normal
-<code class="directive"><Directory></code>s</li>
-<li><a href="../sections.html">How <Directory>, <Location> and
-<Files> sections work</a> for an explanation of how these different
-sections are combined when a request is received</li>
-</ul>
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="DocumentRoot" id="DocumentRoot">DocumentRoot</a> <a name="documentroot" id="documentroot">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Directory that forms the main document tree visible
-from the web</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>DocumentRoot <var>directory-path</var></code></td></tr>
-<tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>DocumentRoot /usr/local/apache/htdocs</code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-</table>
- <p>This directive sets the directory from which <code class="program"><a href="../programs/httpd.html">httpd</a></code>
- will serve files. Unless matched by a directive like <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>, the server appends the
- path from the requested URL to the document root to make the
- path to the document. Example:</p>
-
- <div class="example"><p><code>
- DocumentRoot /usr/web
- </code></p></div>
-
- <p>then an access to
- <code>http://www.my.host.com/index.html</code> refers to
- <code>/usr/web/index.html</code>. If the <var>directory-path</var> is
- not absolute then it is assumed to be relative to the <code class="directive"><a href="#serverroot">ServerRoot</a></code>.</p>
-
- <p>The <code class="directive">DocumentRoot</code> should be specified without
- a trailing slash.</p>
-
-<h3>Consulte tambi�n</h3>
-<ul>
-<li><a href="../urlmapping.html#documentroot">Mapping URLs to Filesystem
-Locations</a></li>
-</ul>
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="Else" id="Else"><Else></a> <a name="else" id="else">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Contains directives that apply only if the condition of a
-previous <code class="directive"><a href="#if"><If></a></code> or
-<code class="directive"><a href="#elseif"><ElseIf></a></code> section is not
-satisfied by a request at runtime</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><Else> ... </Else></code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
-<tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-</table><p>The documentation for this directive has
- not been translated yet. Please have a look at the English
- version.</p><h3>Consulte tambi�n</h3>
-<ul>
-<li><code class="directive"><a href="#if"><If></a></code></li>
-<li><code class="directive"><a href="#elseif"><ElseIf></a></code></li>
-<li><a href="../sections.html">How <Directory>, <Location>,
- <Files> sections work</a> for an explanation of how these
- different sections are combined when a request is received.
- <code class="directive"><If></code>,
- <code class="directive"><ElseIf></code>, and
- <code class="directive"><Else></code> are applied last.</li>
-</ul>
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="ElseIf" id="ElseIf"><ElseIf></a> <a name="elseif" id="elseif">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Contains directives that apply only if a condition is satisfied
-by a request at runtime while the condition of a previous
-<code class="directive"><a href="#if"><If></a></code> or
-<code class="directive"><ElseIf></code> section is not
-satisfied</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><ElseIf <var>expression</var>> ... </ElseIf></code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
-<tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-</table><p>The documentation for this directive has
- not been translated yet. Please have a look at the English
- version.</p><h3>Consulte tambi�n</h3>
-<ul>
-<li><a href="../expr.html">Expressions in Apache HTTP Server</a>,
-for a complete reference and more examples.</li>
-<li><code class="directive"><a href="#if"><If></a></code></li>
-<li><code class="directive"><a href="#else"><Else></a></code></li>
-<li><a href="../sections.html">How <Directory>, <Location>,
- <Files> sections work</a> for an explanation of how these
- different sections are combined when a request is received.
- <code class="directive"><If></code>,
- <code class="directive"><ElseIf></code>, and
- <code class="directive"><Else></code> are applied last.</li>
-</ul>
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="EnableMMAP" id="EnableMMAP">EnableMMAP</a> <a name="enablemmap" id="enablemmap">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Use memory-mapping to read files during delivery</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>EnableMMAP On|Off</code></td></tr>
-<tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>EnableMMAP On</code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
-<tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-</table>
- <p>This directive controls whether the <code class="program"><a href="../programs/httpd.html">httpd</a></code> 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 <code class="module"><a href="../mod/mod_include.html">mod_include</a></code> -- Apache httpd
- memory-maps the file if the OS supports it.</p>
-
- <p>This memory-mapping sometimes yields a performance improvement.
- But in some environments, it is better to disable the memory-mapping
- to prevent operational problems:</p>
-
- <ul>
- <li>On some multiprocessor systems, memory-mapping can reduce the
- performance of the <code class="program"><a href="../programs/httpd.html">httpd</a></code>.</li>
- <li>Deleting or truncating a file while <code class="program"><a href="../programs/httpd.html">httpd</a></code>
- has it memory-mapped can cause <code class="program"><a href="../programs/httpd.html">httpd</a></code> to
- crash with a segmentation fault.
- </li>
- </ul>
-
- <p>For server configurations that are vulnerable to these problems,
- you should disable memory-mapping of delivered files by specifying:</p>
-
- <div class="example"><p><code>
- EnableMMAP Off
- </code></p></div>
-
- <p>For NFS mounted files, this feature may be disabled explicitly for
- the offending files by specifying:</p>
-
- <div class="example"><p><code>
- <Directory "/path-to-nfs-files">
- <span class="indent">
- EnableMMAP Off
- </span>
- </Directory>
- </code></p></div>
-
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="EnableSendfile" id="EnableSendfile">EnableSendfile</a> <a name="enablesendfile" id="enablesendfile">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Use the kernel sendfile support to deliver files to the client</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>EnableSendfile On|Off</code></td></tr>
-<tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>EnableSendfile Off</code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
-<tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in version 2.0.44 and later. Default changed to Off in
-version 2.3.9.</td></tr>
-</table>
- <p>This directive controls whether <code class="program"><a href="../programs/httpd.html">httpd</a></code> 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.</p>
-
- <p>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:</p>
-
- <ul>
- <li>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.</li>
- <li>On Linux the use of sendfile triggers TCP-checksum
- offloading bugs on certain networking cards when using IPv6.</li>
- <li>On Linux on Itanium, sendfile may be unable to handle files
- over 2GB in size.</li>
- <li>With a network-mounted <code class="directive"><a href="#documentroot">DocumentRoot</a></code> (e.g., NFS, SMB, CIFS, FUSE),
- the kernel may be unable to serve the network file through
- its own cache.</li>
- </ul>
-
- <p>For server configurations that are not vulnerable to these problems,
- you may enable this feature by specifying:</p>
-
- <div class="example"><p><code>
- EnableSendfile On
- </code></p></div>
-
- <p>For network mounted files, this feature may be disabled explicitly
- for the offending files by specifying:</p>
-
- <div class="example"><p><code>
- <Directory "/path-to-nfs-files">
- <span class="indent">
- EnableSendfile Off
- </span>
- </Directory>
- </code></p></div>
- <p>Please note that the per-directory and .htaccess configuration
- of <code class="directive">EnableSendfile</code> is not supported by
- <code class="module"><a href="../mod/mod_cache_disk.html">mod_cache_disk</a></code>.
- Only global definition of <code class="directive">EnableSendfile</code>
- is taken into account by the module.
- </p>
-
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="Error" id="Error">Error</a> <a name="error" id="error">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Abort configuration parsing with a custom error message</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Error <var>message</var></code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>2.3.9 and later</td></tr>
-</table>
- <p>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.</p>
-
- <div class="example"><h3>Example</h3><p><code>
- # ensure that mod_include is loaded<br />
- <IfModule !include_module><br />
- Error mod_include is required by mod_foo. Load it with LoadModule.<br />
- </IfModule><br />
- <br />
- # ensure that exactly one of SSL,NOSSL is defined<br />
- <IfDefine SSL><br />
- <IfDefine NOSSL><br />
- Error Both SSL and NOSSL are defined. Define only one of them.<br />
- </IfDefine><br />
- </IfDefine><br />
- <IfDefine !SSL><br />
- <IfDefine !NOSSL><br />
- Error Either SSL or NOSSL must be defined.<br />
- </IfDefine><br />
- </IfDefine><br />
- </code></p></div>
-
-
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="ErrorDocument" id="ErrorDocument">ErrorDocument</a> <a name="errordocument" id="errordocument">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>What the server will return to the client
-in case of an error</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ErrorDocument <var>error-code</var> <var>document</var></code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
-<tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-</table>
- <p>In the event of a problem or error, Apache httpd can be configured
- to do one of four things,</p>
-
- <ol>
- <li>output a simple hardcoded error message</li>
-
- <li>output a customized message</li>
-
- <li>redirect to a local <var>URL-path</var> to handle the
- problem/error</li>
-
- <li>redirect to an external <var>URL</var> to handle the
- problem/error</li>
- </ol>
-
- <p>The first option is the default, while options 2-4 are
- configured using the <code class="directive">ErrorDocument</code>
- 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.</p>
-
- <p>URLs can begin with a slash (/) for local web-paths (relative
- to the <code class="directive"><a href="#documentroot">DocumentRoot</a></code>), or be a
- full URL which the client can resolve. Alternatively, a message
- can be provided to be displayed by the browser. Examples:</p>
-
- <div class="example"><p><code>
- ErrorDocument 500 http://foo.example.com/cgi-bin/tester<br />
- ErrorDocument 404 /cgi-bin/bad_urls.pl<br />
- ErrorDocument 401 /subscription_info.html<br />
- ErrorDocument 403 "Sorry can't allow you access today"
- </code></p></div>
-
- <p>Additionally, the special value <code>default</code> can be used
- to specify Apache httpd's simple hardcoded message. While not required
- under normal circumstances, <code>default</code> will restore
- Apache httpd's simple hardcoded message for configurations that would
- otherwise inherit an existing <code class="directive">ErrorDocument</code>.</p>
-
- <div class="example"><p><code>
- ErrorDocument 404 /cgi-bin/bad_urls.pl<br /><br />
- <Directory /web/docs><br />
- <span class="indent">
- ErrorDocument 404 default<br />
- </span>
- </Directory>
- </code></p></div>
-
- <p>Note that when you specify an <code class="directive">ErrorDocument</code>
- that points to a remote URL (ie. anything with a method such as
- <code>http</code> 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 <code>ErrorDocument 401</code>, the client will not
- know to prompt the user for a password since it will not
- receive the 401 status code. Therefore, <strong>if you use an
- <code>ErrorDocument 401</code> directive then it must refer to a local
- document.</strong></p>
-
- <p>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 <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294807">Q294807</a>.</p>
-
- <p>Although most error messages can be overriden, there are certain
- circumstances where the internal messages are used regardless of the
- setting of <code class="directive"><a href="#errordocument">ErrorDocument</a></code>. 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.</p>
-
- <p>If you are using mod_proxy, you may wish to enable
- <code class="directive"><a href="../mod/mod_proxy.html#proxyerroroverride">ProxyErrorOverride</a></code> 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.</p>
-
-<h3>Consulte tambi�n</h3>
-<ul>
-<li><a href="../custom-error.html">documentation of
- customizable responses</a></li>
-</ul>
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="ErrorLog" id="ErrorLog">ErrorLog</a> <a name="errorlog" id="errorlog">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Location where the server will log errors</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code> ErrorLog <var>file-path</var>|syslog[:<var>facility</var>]</code></td></tr>
-<tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ErrorLog logs/error_log (Unix) ErrorLog logs/error.log (Windows and OS/2)</code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-</table>
- <p>The <code class="directive">ErrorLog</code> directive sets the name of
- the file to which the server will log any errors it encounters. If
- the <var>file-path</var> is not absolute then it is assumed to be
- relative to the <code class="directive"><a href="#serverroot">ServerRoot</a></code>.</p>
-
- <div class="example"><h3>Example</h3><p><code>
- ErrorLog /var/log/httpd/error_log
- </code></p></div>
-
- <p>If the <var>file-path</var>
- begins with a pipe character "<code>|</code>" then it is assumed to be a
- command to spawn to handle the error log.</p>
-
- <div class="example"><h3>Example</h3><p><code>
- ErrorLog "|/usr/local/bin/httpd_errors"
- </code></p></div>
-
- <p>See the notes on <a href="../logs.html#piped">piped logs</a> for
- more information.</p>
-
- <p>Using <code>syslog</code> instead of a filename enables logging
- via syslogd(8) if the system supports it. The default is to use
- syslog facility <code>local7</code>, but you can override this by
- using the <code>syslog:<var>facility</var></code> syntax where
- <var>facility</var> 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.</p>
-
- <div class="example"><h3>Example</h3><p><code>
- ErrorLog syslog:user
- </code></p></div>
-
- <p>SECURITY: See the <a href="../misc/security_tips.html#serverroot">security tips</a>
- 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.</p>
- <div class="warning"><h3>Note</h3>
- <p>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.</p>
- </div>
-
-<h3>Consulte tambi�n</h3>
-<ul>
-<li><code class="directive"><a href="#loglevel">LogLevel</a></code></li>
-<li><a href="../logs.html">Apache HTTP Server Log Files</a></li>
-</ul>
-</div>
-<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="directive-section"><h2><a name="ErrorLogFormat" id="ErrorLogFormat">ErrorLogFormat</a> <a name="errorlogformat" id="errorlogformat">Directiva</a></h2>
-<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Descripci�n:</a></th><td>Format specification for error log entries</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code> ErrorLog [connection|request] <var>format</var></code></td></tr>
-<tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
-<tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
-<tr><th><a href="directive-dict.html#Module">M�dulo:</a></th><td>core</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache httpd 2.3.9 and later</td></tr>
-</table>
- <p><code class="directive">ErrorLogFormat</code> allows to specify what
- supplementary information is logged in the error log in addition to the
- actual log message.</p>
-
- <div class="example"><h3>Simple example</h3><p><code>
- ErrorLogFormat "[%t] [%l] [pid %P] %F: %E: [client %a] %M"
- </code></p></div>
-
- <p>Specifying <code>connection</code> or <code>request</code> 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.</p>
-
- <p>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 <code>%a</code> in the log
- format <code>[%t] [%l] [%a] %M </code> 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.</p>
-
- <p>The above behaviour can be changed by adding modifiers to the format
- string item. A <code>-</code> (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 <code>+</code> (plus) modifier. If an
- item with the plus modifier does not produce any output, the whole line is
- ommitted.</p>
-
- <p>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).</p>
-
- <p>Some format string items accept additional parameters in braces.</p>
-
- <table class="bordered"><tr class="header"><th>Format String</th> <th>Description</th></tr>
-<tr><td><code>%%</code></td>
- <td>The percent sign</td></tr>
-<tr class="odd"><td><code>%...a</code></td>
- <td>Remote IP-address and port</td></tr>
-<tr><td><code>%...A</code></td>
- <td>Local IP-address and port</td></tr>
-<tr class="odd"><td><code>%...{name}e</code></td>
- <td>Request environment variable <code>name</code></td></tr>
-<tr><td><code>%...E</code></td>
- <td>APR/OS error status code and string</td></tr>
-<tr class="odd"><td><code>%...F</code></td>
- <td>Source file name and line number of the log call</td></tr>
-<tr><td><code>%...{name}i</code></td>
- <td>Request header <code>name</code></td></tr>
-<tr class="odd"><td><code>%...k</code></td>
- <td>Number of keep-alive requests on this connection</td></tr>
-<tr><td><code>%...l</code></td>
- <td>Loglevel of the message</td></tr>
-<tr class="odd"><td><code>%...L</code></td>
- <td>Log ID of the request</td></tr>
-<tr><td><code>%...{c}L</code></td>
- <td>Log ID of the connection</td></tr>
-<tr class="odd"><td><code>%...{C}L</code></td>
- <td>Log ID of the connection if used in connection scope, empty otherwise</td></tr>
-<tr><td><code>%...m</code></td>
- <td>Name of the module logging the message</td></tr>
-<tr class="odd"><td><code>%M</code></td>
- <td>The actual log message</td></tr>
-<tr><td><code>%...{name}n</code></td>
- <td>Request note <code>name</code></td></tr>
-<tr class="odd"><td><code>%...P</code></td>
- <td>Process ID of current process</td></tr>
-<tr><td><code>%...T</code></td>
- <td>Thread ID of current thread</td></tr>
-<tr class="odd"><td><code>%...t</code></td>
- <td>The current time</td></tr>
-<tr><td><code>%...{u}t</code></td>
- <td>The current time including micro-seconds</td></tr>
-<tr class="odd"><td><code>%...{cu}t</code></td>
- <td>The current time in compact ISO 8601 format, including
- micro-seconds</td></tr>
-<tr><td><code>%...v</code></td>
- <td>The canonical <code class="directive"><a href="#servername">ServerName</a></code>
- of the current server.</td></tr>
-<tr class="odd"><td><code>%...V</code></td>
- <td>The server name of the server serving the request according to the
- <code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code>
- setting.</td></tr>
-<tr><td><code>\ </code> (backslash space)</td>
- <td>Non-field delimiting space</td></tr>
-<tr class="odd"><td><code>% </code> (percent space)</td>
- <td>Field delimiter (no output)</td></tr>
-</table>
-
[... 7506 lines stripped ...]