1 <?xml version="1.0" encoding="ISO-8859-1"?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" lang="es" xml:lang="es"><head>
4 <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" />
6 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
7 This file is generated from xml source: DO NOT EDIT
8 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
10 <title>core - Servidor HTTP Apache Versión 2.5</title>
11 <link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
12 <link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
13 <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" />
14 <script src="../style/scripts/prettify.min.js" type="text/javascript">
17 <link href="../images/favicon.ico" rel="shortcut icon" /></head>
19 <div id="page-header">
20 <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>
21 <p class="apache">Versión 2.5 del Servidor HTTP Apache</p>
22 <img alt="" src="../images/feather.png" /></div>
23 <div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div>
25 <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>
26 <div id="page-content">
27 <div id="preamble"><h1>Funcionalidad Básica de Apache</h1>
29 <p><span>Idiomas disponibles: </span><a href="../de/mod/core.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> |
30 <a href="../en/mod/core.html" hreflang="en" rel="alternate" title="English"> en </a> |
31 <a href="../es/mod/core.html" title="Español"> es </a> |
32 <a href="../fr/mod/core.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
33 <a href="../ja/mod/core.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
34 <a href="../tr/mod/core.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p>
36 <div class="outofdate">Esta traducción podría estar
37 obsoleta. Consulte la versión en inglés de la
38 documentación para comprobar si se han producido cambios
40 <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>
41 <tr><th><a href="module-dict.html#Status">Estado:</a></th><td>Core</td></tr></table>
43 <div id="quickview"><h3 class="directives">Directivas</h3>
45 <li><img alt="" src="../images/down.gif" /> <a href="#acceptfilter">AcceptFilter</a></li>
46 <li><img alt="" src="../images/down.gif" /> <a href="#acceptpathinfo">AcceptPathInfo</a></li>
47 <li><img alt="" src="../images/down.gif" /> <a href="#accessfilename">AccessFileName</a></li>
48 <li><img alt="" src="../images/down.gif" /> <a href="#adddefaultcharset">AddDefaultCharset</a></li>
49 <li><img alt="" src="../images/down.gif" /> <a href="#allowencodedslashes">AllowEncodedSlashes</a></li>
50 <li><img alt="" src="../images/down.gif" /> <a href="#allowoverride">AllowOverride</a></li>
51 <li><img alt="" src="../images/down.gif" /> <a href="#allowoverridelist">AllowOverrideList</a></li>
52 <li><img alt="" src="../images/down.gif" /> <a href="#asyncfilter">AsyncFilter</a></li>
53 <li><img alt="" src="../images/down.gif" /> <a href="#cgimapextension">CGIMapExtension</a></li>
54 <li><img alt="" src="../images/down.gif" /> <a href="#cgipassauth">CGIPassAuth</a></li>
55 <li><img alt="" src="../images/down.gif" /> <a href="#cgivar">CGIVar</a></li>
56 <li><img alt="" src="../images/down.gif" /> <a href="#contentdigest">ContentDigest</a></li>
57 <li><img alt="" src="../images/down.gif" /> <a href="#defaultruntimedir">DefaultRuntimeDir</a></li>
58 <li><img alt="" src="../images/down.gif" /> <a href="#defaulttype">DefaultType</a></li>
59 <li><img alt="" src="../images/down.gif" /> <a href="#define">Define</a></li>
60 <li><img alt="" src="../images/down.gif" /> <a href="#directory"><Directory></a></li>
61 <li><img alt="" src="../images/down.gif" /> <a href="#directorymatch"><DirectoryMatch></a></li>
62 <li><img alt="" src="../images/down.gif" /> <a href="#documentroot">DocumentRoot</a></li>
63 <li><img alt="" src="../images/down.gif" /> <a href="#else"><Else></a></li>
64 <li><img alt="" src="../images/down.gif" /> <a href="#elseif"><ElseIf></a></li>
65 <li><img alt="" src="../images/down.gif" /> <a href="#enablemmap">EnableMMAP</a></li>
66 <li><img alt="" src="../images/down.gif" /> <a href="#enablesendfile">EnableSendfile</a></li>
67 <li><img alt="" src="../images/down.gif" /> <a href="#error">Error</a></li>
68 <li><img alt="" src="../images/down.gif" /> <a href="#errordocument">ErrorDocument</a></li>
69 <li><img alt="" src="../images/down.gif" /> <a href="#errorlog">ErrorLog</a></li>
70 <li><img alt="" src="../images/down.gif" /> <a href="#errorlogformat">ErrorLogFormat</a></li>
71 <li><img alt="" src="../images/down.gif" /> <a href="#extendedstatus">ExtendedStatus</a></li>
72 <li><img alt="" src="../images/down.gif" /> <a href="#fileetag">FileETag</a></li>
73 <li><img alt="" src="../images/down.gif" /> <a href="#files"><Files></a></li>
74 <li><img alt="" src="../images/down.gif" /> <a href="#filesmatch"><FilesMatch></a></li>
75 <li><img alt="" src="../images/down.gif" /> <a href="#forcetype">ForceType</a></li>
76 <li><img alt="" src="../images/down.gif" /> <a href="#gprofdir">GprofDir</a></li>
77 <li><img alt="" src="../images/down.gif" /> <a href="#hostnamelookups">HostnameLookups</a></li>
78 <li><img alt="" src="../images/down.gif" /> <a href="#httpprotocoloptions">HTTPProtocolOptions</a></li>
79 <li><img alt="" src="../images/down.gif" /> <a href="#if"><If></a></li>
80 <li><img alt="" src="../images/down.gif" /> <a href="#ifdefine"><IfDefine></a></li>
81 <li><img alt="" src="../images/down.gif" /> <a href="#ifmodule"><IfModule></a></li>
82 <li><img alt="" src="../images/down.gif" /> <a href="#include">Include</a></li>
83 <li><img alt="" src="../images/down.gif" /> <a href="#includeoptional">IncludeOptional</a></li>
84 <li><img alt="" src="../images/down.gif" /> <a href="#keepalive">KeepAlive</a></li>
85 <li><img alt="" src="../images/down.gif" /> <a href="#keepalivetimeout">KeepAliveTimeout</a></li>
86 <li><img alt="" src="../images/down.gif" /> <a href="#limit"><Limit></a></li>
87 <li><img alt="" src="../images/down.gif" /> <a href="#limitexcept"><LimitExcept></a></li>
88 <li><img alt="" src="../images/down.gif" /> <a href="#limitinternalrecursion">LimitInternalRecursion</a></li>
89 <li><img alt="" src="../images/down.gif" /> <a href="#limitrequestbody">LimitRequestBody</a></li>
90 <li><img alt="" src="../images/down.gif" /> <a href="#limitrequestfields">LimitRequestFields</a></li>
91 <li><img alt="" src="../images/down.gif" /> <a href="#limitrequestfieldsize">LimitRequestFieldSize</a></li>
92 <li><img alt="" src="../images/down.gif" /> <a href="#limitrequestline">LimitRequestLine</a></li>
93 <li><img alt="" src="../images/down.gif" /> <a href="#limitxmlrequestbody">LimitXMLRequestBody</a></li>
94 <li><img alt="" src="../images/down.gif" /> <a href="#location"><Location></a></li>
95 <li><img alt="" src="../images/down.gif" /> <a href="#locationmatch"><LocationMatch></a></li>
96 <li><img alt="" src="../images/down.gif" /> <a href="#loglevel">LogLevel</a></li>
97 <li><img alt="" src="../images/down.gif" /> <a href="#logleveloverride">LogLevelOverride</a></li>
98 <li><img alt="" src="../images/down.gif" /> <a href="#maxkeepaliverequests">MaxKeepAliveRequests</a></li>
99 <li><img alt="" src="../images/down.gif" /> <a href="#maxrangeoverlaps">MaxRangeOverlaps</a></li>
100 <li><img alt="" src="../images/down.gif" /> <a href="#maxrangereversals">MaxRangeReversals</a></li>
101 <li><img alt="" src="../images/down.gif" /> <a href="#maxranges">MaxRanges</a></li>
102 <li><img alt="" src="../images/down.gif" /> <a href="#mergetrailers">MergeTrailers</a></li>
103 <li><img alt="" src="../images/down.gif" /> <a href="#mutex">Mutex</a></li>
104 <li><img alt="" src="../images/down.gif" /> <a href="#namevirtualhost">NameVirtualHost</a></li>
105 <li><img alt="" src="../images/down.gif" /> <a href="#options">Options</a></li>
106 <li><img alt="" src="../images/down.gif" /> <a href="#protocol">Protocol</a></li>
107 <li><img alt="" src="../images/down.gif" /> <a href="#protocols">Protocols</a></li>
108 <li><img alt="" src="../images/down.gif" /> <a href="#protocolshonororder">ProtocolsHonorOrder</a></li>
109 <li><img alt="" src="../images/down.gif" /> <a href="#qualifyredirecturl">QualifyRedirectURL</a></li>
110 <li><img alt="" src="../images/down.gif" /> <a href="#registerhttpmethod">RegisterHttpMethod</a></li>
111 <li><img alt="" src="../images/down.gif" /> <a href="#rlimitcpu">RLimitCPU</a></li>
112 <li><img alt="" src="../images/down.gif" /> <a href="#rlimitmem">RLimitMEM</a></li>
113 <li><img alt="" src="../images/down.gif" /> <a href="#rlimitnproc">RLimitNPROC</a></li>
114 <li><img alt="" src="../images/down.gif" /> <a href="#scriptinterpretersource">ScriptInterpreterSource</a></li>
115 <li><img alt="" src="../images/down.gif" /> <a href="#seerequesttail">SeeRequestTail</a></li>
116 <li><img alt="" src="../images/down.gif" /> <a href="#serveradmin">ServerAdmin</a></li>
117 <li><img alt="" src="../images/down.gif" /> <a href="#serveralias">ServerAlias</a></li>
118 <li><img alt="" src="../images/down.gif" /> <a href="#servername">ServerName</a></li>
119 <li><img alt="" src="../images/down.gif" /> <a href="#serverpath">ServerPath</a></li>
120 <li><img alt="" src="../images/down.gif" /> <a href="#serverroot">ServerRoot</a></li>
121 <li><img alt="" src="../images/down.gif" /> <a href="#serversignature">ServerSignature</a></li>
122 <li><img alt="" src="../images/down.gif" /> <a href="#servertokens">ServerTokens</a></li>
123 <li><img alt="" src="../images/down.gif" /> <a href="#sethandler">SetHandler</a></li>
124 <li><img alt="" src="../images/down.gif" /> <a href="#setinputfilter">SetInputFilter</a></li>
125 <li><img alt="" src="../images/down.gif" /> <a href="#setoutputfilter">SetOutputFilter</a></li>
126 <li><img alt="" src="../images/down.gif" /> <a href="#timeout">TimeOut</a></li>
127 <li><img alt="" src="../images/down.gif" /> <a href="#traceenable">TraceEnable</a></li>
128 <li><img alt="" src="../images/down.gif" /> <a href="#undefine">UnDefine</a></li>
129 <li><img alt="" src="../images/down.gif" /> <a href="#usecanonicalname">UseCanonicalName</a></li>
130 <li><img alt="" src="../images/down.gif" /> <a href="#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></li>
131 <li><img alt="" src="../images/down.gif" /> <a href="#virtualhost"><VirtualHost></a></li>
132 <li><img alt="" src="../images/down.gif" /> <a href="#warning">Warning</a></li>
134 <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>
136 <li><a href="#comments_section">Comentarios</a></li></ul></div>
138 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
139 <div class="directive-section"><h2><a name="AcceptFilter" id="AcceptFilter">AcceptFilter</a> <a name="acceptfilter" id="acceptfilter">Directiva</a></h2>
140 <table class="directive">
141 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configura mejoras para un Protocolo de Escucha de Sockets</td></tr>
142 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AcceptFilter <var>protocol</var> <var>accept_filter</var></code></td></tr>
143 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
144 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
145 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
147 <p>Esta directiva hace posible mejoras específicas a nivel de sistema operativo
148 y a través del tipo de Protocolo para un socket que escucha.
149 La premisa básica es que el kernel no envíe un socket al servidor
150 hasta que o bien los datos se hayan recibido o bien se haya almacenado
151 en el buffer una Respuesta HTTP completa.
152 Actualmente sólo están soportados
153 <a href="http://www.freebsd.org/cgi/man.cgi?query=accept_filter&sektion=9">
154 Accept Filters</a> sobre FreeBSD, <code>TCP_DEFER_ACCEPT</code> sobre Linux,
155 y AcceptEx() sobre Windows.</p>
157 <p>El uso de <code>none</code> para un argumento desactiva cualquier filtro
158 aceptado para ese protocolo. Esto es útil para protocolos que requieren que un
159 servidor envíe datos primeros, tales como <code>ftp:</code> o <code>nntp</code>:</p>
160 <pre class="prettyprint lang-config">AcceptFilter nntp none</pre>
163 <p>Los nombres de protocolo por defecto son <code>https</code> para el puerto 443
164 y <code>http</code> para todos los demás puertos. Para especificar que se está
165 utilizando otro protocolo con un puerto a la escucha, añade el argumento <var>protocol</var>
166 a la directiva <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>.</p>
168 <p>Los valores por defecto de FreeBDS son:</p>
169 <pre class="prettyprint lang-config">AcceptFilter http httpready
170 AcceptFilter https dataready</pre>
173 <p>El filtro <code>httpready</code> almacena en el buffer peticiones HTTP completas
174 a nivel de kernel. Una vez que la petición es recibida, el kernel la envía al servidor.
175 Consulta la página man de
176 <a href="http://www.freebsd.org/cgi/man.cgi?query=accf_http&sektion=9">
177 accf_http(9)</a> para más detalles. Puesto que las peticiones HTTPS
178 están encriptadas, sólo se utiliza el filtro
179 <a href="http://www.freebsd.org/cgi/man.cgi?query=accf_data&sektion=9">accf_data(9)</a>.</p>
181 <p>Los valores por defecto en Linux son:</p>
182 <pre class="prettyprint lang-config">AcceptFilter http data
183 AcceptFilter https data</pre>
186 <p>En Linux, <code>TCP_DEFER_ACCEPT</code> no soporta el buffering en peticiones http.
187 Cualquier valor además de <code>none</code> habilitará
188 <code>TCP_DEFER_ACCEPT</code> en ese socket. Para más detalles
189 ver la página man de Linux
190 <a href="http://linux.die.net/man/7/tcp">
193 <p>Los valores por defecto en Windows son:</p>
194 <pre class="prettyprint lang-config">AcceptFilter http data
195 AcceptFilter https data</pre>
198 <p>Sobre Windows mpm_winnt interpreta el argumento AcceptFilter para conmutar la API
199 AcceptEx(), y no soporta el buffering sobre el protocolo http. Hay dos valores
200 que utilizan la API Windows AcceptEx() y que recuperan sockets de red
201 entre conexiones. <code>data</code> espera hasta que los datos han sido
202 transmitidos como se comentaba anteriormente, y el buffer inicial de datos y las
203 direcciones de red son recuperadas a partir de una única llamada AcceptEx().
204 <code>connect</code> utiliza la API AcceptEx() API, y recupera también
205 las direcciones de red, pero a diferencia de <code>none</code>
206 la opción <code>connect</code> no espera a la transmisión inicial de los datos.</p>
208 <p>Sobre Windows, <code>none</code> usa accept() antes que AcceptEx()
209 y no recuperará sockets entre las conexiones. Lo que es útil para los adaptadores de
210 red con un soporte precario de drivers, así como para algunos proveedores de red
211 tales como drivers vpn, o filtros de spam, de virus o de spyware.</p>
214 <h3>Consulte también</h3>
216 <li><code class="directive"><a href="#protocol">Protocol</a></code></li>
219 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
220 <div class="directive-section"><h2><a name="AcceptPathInfo" id="AcceptPathInfo">AcceptPathInfo</a> <a name="acceptpathinfo" id="acceptpathinfo">Directiva</a></h2>
221 <table class="directive">
222 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Los recursos aceptan información sobre su ruta</td></tr>
223 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AcceptPathInfo On|Off|Default</code></td></tr>
224 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AcceptPathInfo Default</code></td></tr>
225 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
226 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
227 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
228 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
231 <p>Esta directiva controla si las peticiones que contienen información sobre la ruta
232 que sigue un fichero que existe (o un fichero que no existe pero en un directorio que
233 sí existe) serán aceptadas o denegadas. La información de ruta puede estar disponible
234 para los scripts en la variable de entorno <code>PATH_INFO</code>.</p>
236 <p>Por ejemplo, asumamos que la ubicación <code>/test/</code> apunta a
237 un directorio que contiene únicamente el fichero
238 <code>here.html</code>. Entonces, las peticiones tanto para
239 <code>/test/here.html/more</code> como para
240 <code>/test/nothere.html/more</code> recogen
241 <code>/more</code> como <code>PATH_INFO</code>.</p>
243 <p>Los tres posibles argumentos para la directiva
244 <code class="directive">AcceptPathInfo</code> son los siguientes:</p>
246 <dt><code>Off</code></dt><dd>Una petición sólo será aceptada si
247 se corresponde con una ruta literal que existe. Por lo tanto, una petición
248 con una información de ruta después del nombre de fichero tal como
249 <code>/test/here.html/more</code> en el ejemplo anterior devolverá
250 un error 404 NOT FOUND.</dd>
252 <dt><code>On</code></dt><dd>Una petición será aceptada si una
253 ruta principal de acceso se corresponde con un fichero que existe. El ejemplo
254 anterior <code>/test/here.html/more</code> será aceptado si
255 <code>/test/here.html</code> corresponde a un fichero válido.</dd>
257 <dt><code>Default</code></dt><dd>La gestión de las peticiones
258 con información de ruta está determinada por el <a href="../handler.html">controlador</a> responsable de la petición.
259 El controlador principal para para ficheros normales rechaza por defecto
260 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
261 <code>PATH_INFO</code> por defecto.</dd>
264 <p>El objetivo principal de la directiva <code>AcceptPathInfo</code>
265 es permitirnos sobrescribir la opción del controlador
266 de aceptar o rechazar <code>PATH_INFO</code>. Este tipo de reescritura se necesita,
267 por ejemplo, cuando utilizas un <a href="../filter.html">filtro</a>, tal como
268 <a href="mod_include.html">INCLUDES</a>, para generar contenido
269 basado en <code>PATH_INFO</code>. El controlador principal normalmente rechazaría
270 la petición, de modo que puedes utilizar la siguiente configuración para habilitarla
273 <pre class="prettyprint lang-config"><Files "mypaths.shtml">
275 SetOutputFilter INCLUDES
282 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
283 <div class="directive-section"><h2><a name="AccessFileName" id="AccessFileName">AccessFileName</a> <a name="accessfilename" id="accessfilename">Directiva</a></h2>
284 <table class="directive">
285 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Nombre del fichero distribuido de configuración</td></tr>
286 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AccessFileName <var>filename</var> [<var>filename</var>] ...</code></td></tr>
287 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AccessFileName .htaccess</code></td></tr>
288 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
289 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
290 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
292 <p>Mientras que procesa una petición el servidor busca
293 el primer fichero de configuración existente dentro de un listado de nombres en
294 cada directorio de la ruta del documento, si los ficheros distribuidos
295 de configuración están <a href="#allowoverride">habilitados para ese
296 directorio</a>. Por ejemplo:</p>
298 <pre class="prettyprint lang-config">AccessFileName .acl</pre>
301 <p>Antes de servir el documento
302 <code>/usr/local/web/index.html</code>, el servidor leerá
303 <code>/.acl</code>, <code>/usr/.acl</code>,
304 <code>/usr/local/.acl</code> y <code>/usr/local/web/.acl</code>
305 para las directivas, salvo que estén deshabilitadas con:</p>
307 <pre class="prettyprint lang-config"><Directory "/">
309 </Directory></pre>
314 <h3>Consulte también</h3>
316 <li><code class="directive"><a href="#allowoverride">AllowOverride</a></code></li>
317 <li><a href="../configuring.html">Ficheros de configuración</a></li>
318 <li><a href="../howto/htaccess.html">Fichero .htaccess</a></li>
321 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
322 <div class="directive-section"><h2><a name="AddDefaultCharset" id="AddDefaultCharset">AddDefaultCharset</a> <a name="adddefaultcharset" id="adddefaultcharset">Directiva</a></h2>
323 <table class="directive">
324 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Juego de casrácteres que se le añade por defecto a una respuesta del tipo
325 contenido "content-type" es <code>text/plain</code> o <code>text/html</code></td></tr>
326 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AddDefaultCharset On|Off|<var>charset</var></code></td></tr>
327 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AddDefaultCharset Off</code></td></tr>
328 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
329 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
330 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
331 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
333 <p>Esta directiva especifica un valor por defecto para el tipo de soporte que
334 se usa como parámetro del juego de carácteres (el nombre de una
335 codificación de carácteres) para ser añadido a una respuesta si y solo si
336 el contenido de "content-type" es o <code>text/plain</code> o
337 <code>text/html</code>. Esto debería sobreescribir cualquier juego de
338 caracteres que se le especifique en el cuerpo de la respuesta mediante un
339 elemento <code>META</code>, aunque el comportamiento exacto depende a menudo
340 de la confuguracion del usuario cliente. Una configuración de
341 <code>AddDefaultCharset Off</code> deshabilita esta funcionalidad.
342 <code>AddDefaultCharset On</code> habilita un conjunto de caracteres por defecto
343 de <code>iso-8859-1</code>. Cualquier otro valor se asume que sea el <var>charset</var>
344 que va a ser usado, que debe ser uno de los juegos de carácteres
345 <a href="http://www.iana.org/assignments/character-sets">registradas por el IANA
346 </a> para su uso en los tipos de medios de Internet (MIME types).
349 <pre class="prettyprint lang-config">AddDefaultCharset utf-8</pre>
352 <p><code class="directive">AddDefaultCharset</code> debería ser utilizada sólo cuando
353 se sepa que todo el texto del recurso al que se le aplica se sabe que va a
354 estar en ese juego de caracteres y es inconveniente etiquetar los
355 documentos individualmente. Un ejemplo de ello es añadir el juego de caracteres
356 a recursos con contenido autogenerado, tales como scripts legados de CGI,
357 que pueden ser vulnerables a ataques de tipo XSS (Cross-Site Scripting),
358 debido a datos que incluye el usuario en la salida. Notese, sin embargo
359 una mejor solución es arreglar (o eliminar) dichos scripts, ya que
360 dejar por defecto un juego de carácteres no protege a los usuarios
361 que han habilitado la funcionalidad "auto-detect character encoding" en sus
365 <h3>Consulte también</h3>
367 <li><code class="directive"><a href="../mod/mod_mime.html#addcharset">AddCharset</a></code></li>
370 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
371 <div class="directive-section"><h2><a name="AllowEncodedSlashes" id="AllowEncodedSlashes">AllowEncodedSlashes</a> <a name="allowencodedslashes" id="allowencodedslashes">Directiva</a></h2>
372 <table class="directive">
373 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determina si Determines whether encoded path separators in URLs are allowed to
374 be passed through</td></tr>
375 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AllowEncodedSlashes On|Off</code></td></tr>
376 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AllowEncodedSlashes Off</code></td></tr>
377 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
378 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
379 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
380 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache httpd 2.0.46 and later</td></tr>
382 <p>The <code class="directive">AllowEncodedSlashes</code> directive allows URLs
383 which contain encoded path separators (<code>%2F</code> for <code>/</code>
384 and additionally <code>%5C</code> for <code>\</code> on according systems)
385 to be used. Normally such URLs are refused with a 404 (Not found) error.</p>
387 <p>Turning <code class="directive">AllowEncodedSlashes</code> <code>On</code> is
388 mostly useful when used in conjunction with <code>PATH_INFO</code>.</p>
390 <div class="note"><h3>Note</h3>
391 <p>Allowing encoded slashes does <em>not</em> imply <em>decoding</em>.
392 Occurrences of <code>%2F</code> or <code>%5C</code> (<em>only</em> on
393 according systems) will be left as such in the otherwise decoded URL
397 <h3>Consulte también</h3>
399 <li><code class="directive"><a href="#acceptpathinfo">AcceptPathInfo</a></code></li>
402 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
403 <div class="directive-section"><h2><a name="AllowOverride" id="AllowOverride">AllowOverride</a> <a name="allowoverride" id="allowoverride">Directiva</a></h2>
404 <table class="directive">
405 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Types of directives that are allowed in
406 <code>.htaccess</code> files</td></tr>
407 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AllowOverride All|None|<var>directive-type</var>
408 [<var>directive-type</var>] ...</code></td></tr>
409 <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>
410 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory</td></tr>
411 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
412 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
414 <p>When the server finds an <code>.htaccess</code> file (as
415 specified by <code class="directive"><a href="#accessfilename">AccessFileName</a></code>)
416 it needs to know which directives declared in that file can override
417 earlier configuration directives.</p>
419 <div class="note"><h3>Only available in <Directory> sections</h3>
420 <code class="directive">AllowOverride</code> is valid only in
421 <code class="directive"><a href="#directory"><Directory></a></code>
422 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
423 <code class="directive"><a href="#files"><Files></a></code> sections.
426 <p>When this directive is set to <code>None</code>, then
427 <a href="#accessfilename">.htaccess</a> files are completely ignored.
428 In this case, the server will not even attempt to read
429 <code>.htaccess</code> files in the filesystem.</p>
431 <p>When this directive is set to <code>All</code>, then any
432 directive which has the .htaccess <a href="directive-dict.html#Context">Context</a> is allowed in
433 <code>.htaccess</code> files.</p>
435 <p>The <var>directive-type</var> can be one of the following
436 groupings of directives.</p>
443 Allow use of the authorization directives (<code class="directive"><a href="../mod/mod_authn_dbm.html#authdbmgroupfile">AuthDBMGroupFile</a></code>,
444 <code class="directive"><a href="../mod/mod_authn_dbm.html#authdbmuserfile">AuthDBMUserFile</a></code>,
445 <code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code>,
446 <code class="directive"><a href="../mod/mod_authn_core.html#authname">AuthName</a></code>,
447 <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>
452 Allow use of the directives controlling document types
453 (<code class="directive"><a href="#errordocument">ErrorDocument</a></code>,
454 <code class="directive"><a href="#forcetype">ForceType</a></code>,
455 <code class="directive"><a href="../mod/mod_negotiation.html#languagepriority">LanguagePriority</a></code>,
456 <code class="directive"><a href="#sethandler">SetHandler</a></code>,
457 <code class="directive"><a href="#setinputfilter">SetInputFilter</a></code>,
458 <code class="directive"><a href="#setoutputfilter">SetOutputFilter</a></code>, and
459 <code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code> Add* and Remove* directives),
460 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>),
461 <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
462 <code class="directive"><a href="../mod/mod_actions.html#action">Action</a></code> from
463 <code class="module"><a href="../mod/mod_actions.html">mod_actions</a></code>.
469 Allow use of the directives controlling directory indexing
470 (<code class="directive"><a href="../mod/mod_autoindex.html#adddescription">AddDescription</a></code>,
471 <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>,
472 <code class="directive"><a href="../mod/mod_autoindex.html#addiconbytype">AddIconByType</a></code>,
473 <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>,
479 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>
481 <dt>Options[=<var>Option</var>,...]</dt>
484 Allow use of the directives controlling specific directory
485 features (<code class="directive"><a href="#options">Options</a></code> and
486 <code class="directive"><a href="../mod/mod_include.html#xbithack">XBitHack</a></code>).
487 An equal sign may be given followed by a comma (but no spaces)
488 separated lists of options that may be set using the <code class="directive"><a href="#options">Options</a></code> command.</dd>
493 <div class="example"><p><code>
494 AllowOverride AuthConfig Indexes
497 <p>In the example above all directives that are neither in the group
498 <code>AuthConfig</code> nor <code>Indexes</code> cause an internal
501 <div class="note"><p>For security and performance reasons, do not set
502 <code>AllowOverride</code> to anything other than <code>None</code>
503 in your <code><Directory /></code> block. Instead, find (or
504 create) the <code><Directory></code> block that refers to the
505 directory where you're actually planning to place a
506 <code>.htaccess</code> file.</p>
509 <h3>Consulte también</h3>
511 <li><code class="directive"><a href="#accessfilename">AccessFileName</a></code></li>
512 <li><a href="../configuring.html">Configuration Files</a></li>
513 <li><a href="../howto/htaccess.html">.htaccess Files</a></li>
516 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
517 <div class="directive-section"><h2><a name="AllowOverrideList" id="AllowOverrideList">AllowOverrideList</a> <a name="allowoverridelist" id="allowoverridelist">Directiva</a></h2>
518 <table class="directive">
519 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Individual directives that are allowed in
520 <code>.htaccess</code> files</td></tr>
521 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AllowOverrideList None|<var>directive</var>
522 [<var>directive-type</var>] ...</code></td></tr>
523 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AllowOverrideList None</code></td></tr>
524 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory</td></tr>
525 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
526 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
527 </table><p>The documentation for this directive has
528 not been translated yet. Please have a look at the English
529 version.</p><h3>Consulte también</h3>
531 <li><code class="directive"><a href="#accessfilename">AccessFileName</a></code></li>
532 <li><code class="directive"><a href="#allowoverride">AllowOverride</a></code></li>
533 <li><a href="../configuring.html">Configuration Files</a></li>
534 <li><a href="../howto/htaccess.html">.htaccess Files</a></li>
537 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
538 <div class="directive-section"><h2><a name="AsyncFilter" id="AsyncFilter">AsyncFilter</a> <a name="asyncfilter" id="asyncfilter">Directiva</a></h2>
539 <table class="directive">
540 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Set the minimum filter type eligible for asynchronous handling</td></tr>
541 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AsyncFilter request|connection|network</code></td></tr>
542 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AsyncFilter request</code></td></tr>
543 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
544 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
545 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
546 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Only available from Apache 2.5.0 and later.</td></tr>
547 </table><p>The documentation for this directive has
548 not been translated yet. Please have a look at the English
550 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
551 <div class="directive-section"><h2><a name="CGIMapExtension" id="CGIMapExtension">CGIMapExtension</a> <a name="cgimapextension" id="cgimapextension">Directiva</a></h2>
552 <table class="directive">
553 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Technique for locating the interpreter for CGI
555 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>CGIMapExtension <var>cgi-path</var> <var>.extension</var></code></td></tr>
556 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
557 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
558 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
559 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
560 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>NetWare only</td></tr>
562 <p>This directive is used to control how Apache httpd finds the
563 interpreter used to run CGI scripts. For example, setting
564 <code>CGIMapExtension sys:\foo.nlm .foo</code> will
565 cause all CGI script files with a <code>.foo</code> extension to
566 be passed to the FOO interpreter.</p>
569 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
570 <div class="directive-section"><h2><a name="CGIPassAuth" id="CGIPassAuth">CGIPassAuth</a> <a name="cgipassauth" id="cgipassauth">Directiva</a></h2>
571 <table class="directive">
572 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enables passing HTTP authorization headers to scripts as CGI
574 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>CGIPassAuth On|Off</code></td></tr>
575 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>CGIPassAuth Off</code></td></tr>
576 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
577 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>AuthConfig</td></tr>
578 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
579 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
580 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.4.13 and later</td></tr>
581 </table><p>The documentation for this directive has
582 not been translated yet. Please have a look at the English
584 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
585 <div class="directive-section"><h2><a name="CGIVar" id="CGIVar">CGIVar</a> <a name="cgivar" id="cgivar">Directiva</a></h2>
586 <table class="directive">
587 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Controls how some CGI variables are set</td></tr>
588 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>CGIVar <var>variable</var> <var>rule</var></code></td></tr>
589 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
590 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
591 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
592 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
593 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.4.21 and later</td></tr>
594 </table><p>The documentation for this directive has
595 not been translated yet. Please have a look at the English
597 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
598 <div class="directive-section"><h2><a name="ContentDigest" id="ContentDigest">ContentDigest</a> <a name="contentdigest" id="contentdigest">Directiva</a></h2>
599 <table class="directive">
600 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enables the generation of <code>Content-MD5</code> HTTP Response
602 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ContentDigest On|Off</code></td></tr>
603 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ContentDigest Off</code></td></tr>
604 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
605 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>Options</td></tr>
606 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
607 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
609 <p>This directive enables the generation of
610 <code>Content-MD5</code> headers as defined in RFC1864
611 respectively RFC2616.</p>
613 <p>MD5 is an algorithm for computing a "message digest"
614 (sometimes called "fingerprint") of arbitrary-length data, with
615 a high degree of confidence that any alterations in the data
616 will be reflected in alterations in the message digest.</p>
618 <p>The <code>Content-MD5</code> header provides an end-to-end
619 message integrity check (MIC) of the entity-body. A proxy or
620 client may check this header for detecting accidental
621 modification of the entity-body in transit. Example header:</p>
623 <div class="example"><p><code>
624 Content-MD5: AuLb7Dp1rqtRtxz2m9kRpA==
627 <p>Note that this can cause performance problems on your server
628 since the message digest is computed on every request (the
629 values are not cached).</p>
631 <p><code>Content-MD5</code> is only sent for documents served
632 by the <code class="module"><a href="../mod/core.html">core</a></code>, and not by any module. For example,
633 SSI documents, output from CGI scripts, and byte range responses
634 do not have this header.</p>
637 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
638 <div class="directive-section"><h2><a name="DefaultRuntimeDir" id="DefaultRuntimeDir">DefaultRuntimeDir</a> <a name="defaultruntimedir" id="defaultruntimedir">Directiva</a></h2>
639 <table class="directive">
640 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Base directory for the server run-time files</td></tr>
641 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>DefaultRuntimeDir <var>directory-path</var></code></td></tr>
642 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>DefaultRuntimeDir DEFAULT_REL_RUNTIMEDIR (logs/)</code></td></tr>
643 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
644 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
645 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
646 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache 2.4.2 and later</td></tr>
647 </table><p>The documentation for this directive has
648 not been translated yet. Please have a look at the English
649 version.</p><h3>Consulte también</h3>
651 <li><a href="../misc/security_tips.html#serverroot">the
652 security tips</a> for information on how to properly set
653 permissions on the <code class="directive">ServerRoot</code></li>
656 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
657 <div class="directive-section"><h2><a name="DefaultType" id="DefaultType">DefaultType</a> <a name="defaulttype" id="defaulttype">Directiva</a></h2>
658 <table class="directive">
659 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>This directive has no effect other than to emit warnings
660 if the value is not <code>none</code>. In prior versions, DefaultType
661 would specify a default media type to assign to response content for
662 which no other media type configuration could be found.
664 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>DefaultType <var>media-type|none</var></code></td></tr>
665 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>DefaultType none</code></td></tr>
666 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
667 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
668 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
669 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
670 <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>
672 <p>This directive has been disabled. For backwards compatibility
673 of configuration files, it may be specified with the value
674 <code>none</code>, meaning no default media type. For example:</p>
676 <div class="example"><p><code>
680 <p><code>DefaultType None</code> is only available in
681 httpd-2.2.7 and later.</p>
683 <p>Use the mime.types configuration file and the
684 <code class="directive"><a href="../mod/mod_mime.html#addtype">AddType</a></code> to configure media
685 type assignments via file extensions, or the
686 <code class="directive"><a href="#forcetype">ForceType</a></code> directive to configure
687 the media type for specific resources. Otherwise, the server will
688 send the response without a Content-Type header field and the
689 recipient may attempt to guess the media type.</p>
692 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
693 <div class="directive-section"><h2><a name="Define" id="Define">Define</a> <a name="define" id="define">Directiva</a></h2>
694 <table class="directive">
695 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Define the existence of a variable</td></tr>
696 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Define <var>parameter-name</var></code></td></tr>
697 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
698 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
699 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
701 <p>Equivalent to passing the <code>-D</code> argument to <code class="program"><a href="../programs/httpd.html">httpd</a></code>.</p>
702 <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
703 <code>-D</code> arguments in any startup scripts.</p>
706 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
707 <div class="directive-section"><h2><a name="Directory" id="Directory"><Directory></a> <a name="directory" id="directory">Directiva</a></h2>
708 <table class="directive">
709 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enclose a group of directives that apply only to the
710 named file-system directory, sub-directories, and their contents.</td></tr>
711 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><Directory <var>directory-path</var>>
712 ... </Directory></code></td></tr>
713 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
714 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
715 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
717 <p><code class="directive"><Directory></code> and
718 <code></Directory></code> are used to enclose a group of
719 directives that will apply only to the named directory,
720 sub-directories of that directory, and the files within the respective
721 directories. Any directive that is allowed
722 in a directory context may be used. <var>Directory-path</var> is
723 either the full path to a directory, or a wild-card string using
724 Unix shell-style matching. In a wild-card string, <code>?</code> matches
725 any single character, and <code>*</code> matches any sequences of
726 characters. You may also use <code>[]</code> character ranges. None
727 of the wildcards match a `/' character, so <code><Directory
728 /*/public_html></code> will not match
729 <code>/home/user/public_html</code>, but <code><Directory
730 /home/*/public_html></code> will match. Example:</p>
732 <div class="example"><p><code>
733 <Directory /usr/local/httpd/htdocs><br />
734 <span class="indent">
735 Options Indexes FollowSymLinks<br />
741 <p>Be careful with the <var>directory-path</var> arguments:
742 They have to literally match the filesystem path which Apache httpd uses
743 to access the files. Directives applied to a particular
744 <code><Directory></code> will not apply to files accessed from
745 that same directory via a different path, such as via different symbolic
749 <p><a class="glossarylink" href="../glossary.html#regex" title="ver glosario">Regular
750 expressions</a> can also be used, with the addition of the
751 <code>~</code> character. For example:</p>
753 <div class="example"><p><code>
754 <Directory ~ "^/www/.*/[0-9]{3}">
757 <p>would match directories in <code>/www/</code> that consisted of
760 <p>If multiple (non-regular expression) <code class="directive"><Directory></code> sections
761 match the directory (or one of its parents) containing a document,
762 then the directives are applied in the order of shortest match
763 first, interspersed with the directives from the <a href="#accessfilename">.htaccess</a> files. For example,
766 <div class="example"><p><code>
767 <Directory /><br />
768 <span class="indent">
769 AllowOverride None<br />
771 </Directory><br />
773 <Directory /home/><br />
774 <span class="indent">
775 AllowOverride FileInfo<br />
780 <p>for access to the document <code>/home/web/dir/doc.html</code>
784 <li>Apply directive <code>AllowOverride None</code>
785 (disabling <code>.htaccess</code> files).</li>
787 <li>Apply directive <code>AllowOverride FileInfo</code> (for
788 directory <code>/home</code>).</li>
790 <li>Apply any <code>FileInfo</code> directives in
791 <code>/home/.htaccess</code>, <code>/home/web/.htaccess</code> and
792 <code>/home/web/dir/.htaccess</code> in that order.</li>
795 <p>Regular expressions are not considered until after all of the
796 normal sections have been applied. Then all of the regular
797 expressions are tested in the order they appeared in the
798 configuration file. For example, with</p>
800 <div class="example"><p><code>
801 <Directory ~ abc$><br />
802 <span class="indent">
803 # ... directives here ...<br />
808 <p>the regular expression section won't be considered until after
809 all normal <code class="directive"><Directory></code>s and
810 <code>.htaccess</code> files have been applied. Then the regular
811 expression will match on <code>/home/abc/public_html/abc</code> and
812 the corresponding <code class="directive"><Directory></code> will
815 <p><strong>Note that the default access for
816 <code><Directory /></code> is <code>Allow from All</code>.
817 This means that Apache httpd will serve any file mapped from an URL. It is
818 recommended that you change this with a block such
821 <div class="example"><p><code>
822 <Directory /><br />
823 <span class="indent">
824 Order Deny,Allow<br />
830 <p><strong>and then override this for directories you
831 <em>want</em> accessible. See the <a href="../misc/security_tips.html">Security Tips</a> page for more
832 details.</strong></p>
834 <p>The directory sections occur in the <code>httpd.conf</code> file.
835 <code class="directive"><Directory></code> directives
836 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>
838 <h3>Consulte también</h3>
840 <li><a href="../sections.html">How <Directory>,
841 <Location> and <Files> sections work</a> for an
842 explanation of how these different sections are combined when a
843 request is received</li>
846 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
847 <div class="directive-section"><h2><a name="DirectoryMatch" id="DirectoryMatch"><DirectoryMatch></a> <a name="directorymatch" id="directorymatch">Directiva</a></h2>
848 <table class="directive">
849 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enclose directives that apply to
850 the contents of file-system directories matching a regular expression.</td></tr>
851 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><DirectoryMatch <var>regex</var>>
852 ... </DirectoryMatch></code></td></tr>
853 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
854 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
855 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
857 <p><code class="directive"><DirectoryMatch></code> and
858 <code></DirectoryMatch></code> are used to enclose a group
859 of directives which will apply only to the named directory (and the files within),
860 the same as <code class="directive"><a href="#directory"><Directory></a></code>.
861 However, it takes as an argument a
862 <a class="glossarylink" href="../glossary.html#regex" title="ver glosario">regular expression</a>. For example:</p>
864 <div class="example"><p><code>
865 <DirectoryMatch "^/www/(.+/)?[0-9]{3}">
868 <p>would match directories in <code>/www/</code> that consisted of three
871 <div class="note"><h3>Compatability</h3>
872 Prior to 2.3.9, this directive implicitly applied to sub-directories
873 (like <code class="directive"><a href="#directory"><Directory></a></code>) and
874 could not match the end of line symbol ($). In 2.3.9 and later,
875 only directories that match the expression are affected by the enclosed
879 <div class="note"><h3>Trailing Slash</h3>
880 This directive applies to requests for directories that may or may
881 not end in a trailing slash, so expressions that are anchored to the
882 end of line ($) must be written with care.
885 <h3>Consulte también</h3>
887 <li><code class="directive"><a href="#directory"><Directory></a></code> for
888 a description of how regular expressions are mixed in with normal
889 <code class="directive"><Directory></code>s</li>
890 <li><a href="../sections.html">How <Directory>, <Location> and
891 <Files> sections work</a> for an explanation of how these different
892 sections are combined when a request is received</li>
895 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
896 <div class="directive-section"><h2><a name="DocumentRoot" id="DocumentRoot">DocumentRoot</a> <a name="documentroot" id="documentroot">Directiva</a></h2>
897 <table class="directive">
898 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Directory that forms the main document tree visible
899 from the web</td></tr>
900 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>DocumentRoot <var>directory-path</var></code></td></tr>
901 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>DocumentRoot /usr/local/apache/htdocs</code></td></tr>
902 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
903 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
904 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
906 <p>This directive sets the directory from which <code class="program"><a href="../programs/httpd.html">httpd</a></code>
907 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
908 path from the requested URL to the document root to make the
909 path to the document. Example:</p>
911 <div class="example"><p><code>
912 DocumentRoot /usr/web
916 <code>http://www.my.host.com/index.html</code> refers to
917 <code>/usr/web/index.html</code>. If the <var>directory-path</var> is
918 not absolute then it is assumed to be relative to the <code class="directive"><a href="#serverroot">ServerRoot</a></code>.</p>
920 <p>The <code class="directive">DocumentRoot</code> should be specified without
921 a trailing slash.</p>
923 <h3>Consulte también</h3>
925 <li><a href="../urlmapping.html#documentroot">Mapping URLs to Filesystem
929 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
930 <div class="directive-section"><h2><a name="Else" id="Else"><Else></a> <a name="else" id="else">Directiva</a></h2>
931 <table class="directive">
932 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply only if the condition of a
933 previous <code class="directive"><a href="#if"><If></a></code> or
934 <code class="directive"><a href="#elseif"><ElseIf></a></code> section is not
935 satisfied by a request at runtime</td></tr>
936 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><Else> ... </Else></code></td></tr>
937 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
938 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
939 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
940 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
941 </table><p>The documentation for this directive has
942 not been translated yet. Please have a look at the English
943 version.</p><h3>Consulte también</h3>
945 <li><code class="directive"><a href="#if"><If></a></code></li>
946 <li><code class="directive"><a href="#elseif"><ElseIf></a></code></li>
947 <li><a href="../sections.html">How <Directory>, <Location>,
948 <Files> sections work</a> for an explanation of how these
949 different sections are combined when a request is received.
950 <code class="directive"><If></code>,
951 <code class="directive"><ElseIf></code>, and
952 <code class="directive"><Else></code> are applied last.</li>
955 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
956 <div class="directive-section"><h2><a name="ElseIf" id="ElseIf"><ElseIf></a> <a name="elseif" id="elseif">Directiva</a></h2>
957 <table class="directive">
958 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply only if a condition is satisfied
959 by a request at runtime while the condition of a previous
960 <code class="directive"><a href="#if"><If></a></code> or
961 <code class="directive"><ElseIf></code> section is not
963 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><ElseIf <var>expression</var>> ... </ElseIf></code></td></tr>
964 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
965 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
966 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
967 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
968 </table><p>The documentation for this directive has
969 not been translated yet. Please have a look at the English
970 version.</p><h3>Consulte también</h3>
972 <li><a href="../expr.html">Expressions in Apache HTTP Server</a>,
973 for a complete reference and more examples.</li>
974 <li><code class="directive"><a href="#if"><If></a></code></li>
975 <li><code class="directive"><a href="#else"><Else></a></code></li>
976 <li><a href="../sections.html">How <Directory>, <Location>,
977 <Files> sections work</a> for an explanation of how these
978 different sections are combined when a request is received.
979 <code class="directive"><If></code>,
980 <code class="directive"><ElseIf></code>, and
981 <code class="directive"><Else></code> are applied last.</li>
984 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
985 <div class="directive-section"><h2><a name="EnableMMAP" id="EnableMMAP">EnableMMAP</a> <a name="enablemmap" id="enablemmap">Directiva</a></h2>
986 <table class="directive">
987 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Use memory-mapping to read files during delivery</td></tr>
988 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>EnableMMAP On|Off</code></td></tr>
989 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>EnableMMAP On</code></td></tr>
990 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
991 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
992 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
993 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
995 <p>This directive controls whether the <code class="program"><a href="../programs/httpd.html">httpd</a></code> may use
996 memory-mapping if it needs to read the contents of a file during
997 delivery. By default, when the handling of a request requires
998 access to the data within a file -- for example, when delivering a
999 server-parsed file using <code class="module"><a href="../mod/mod_include.html">mod_include</a></code> -- Apache httpd
1000 memory-maps the file if the OS supports it.</p>
1002 <p>This memory-mapping sometimes yields a performance improvement.
1003 But in some environments, it is better to disable the memory-mapping
1004 to prevent operational problems:</p>
1007 <li>On some multiprocessor systems, memory-mapping can reduce the
1008 performance of the <code class="program"><a href="../programs/httpd.html">httpd</a></code>.</li>
1009 <li>Deleting or truncating a file while <code class="program"><a href="../programs/httpd.html">httpd</a></code>
1010 has it memory-mapped can cause <code class="program"><a href="../programs/httpd.html">httpd</a></code> to
1011 crash with a segmentation fault.
1015 <p>For server configurations that are vulnerable to these problems,
1016 you should disable memory-mapping of delivered files by specifying:</p>
1018 <div class="example"><p><code>
1022 <p>For NFS mounted files, this feature may be disabled explicitly for
1023 the offending files by specifying:</p>
1025 <div class="example"><p><code>
1026 <Directory "/path-to-nfs-files">
1027 <span class="indent">
1034 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1035 <div class="directive-section"><h2><a name="EnableSendfile" id="EnableSendfile">EnableSendfile</a> <a name="enablesendfile" id="enablesendfile">Directiva</a></h2>
1036 <table class="directive">
1037 <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>
1038 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>EnableSendfile On|Off</code></td></tr>
1039 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>EnableSendfile Off</code></td></tr>
1040 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1041 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
1042 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1043 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1044 <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
1045 version 2.3.9.</td></tr>
1047 <p>This directive controls whether <code class="program"><a href="../programs/httpd.html">httpd</a></code> may use the
1048 sendfile support from the kernel to transmit file contents to the client.
1049 By default, when the handling of a request requires no access
1050 to the data within a file -- for example, when delivering a
1051 static file -- Apache httpd uses sendfile to deliver the file contents
1052 without ever reading the file if the OS supports it.</p>
1054 <p>This sendfile mechanism avoids separate read and send operations,
1055 and buffer allocations. But on some platforms or within some
1056 filesystems, it is better to disable this feature to avoid
1057 operational problems:</p>
1060 <li>Some platforms may have broken sendfile support that the build
1061 system did not detect, especially if the binaries were built on
1062 another box and moved to such a machine with broken sendfile
1064 <li>On Linux the use of sendfile triggers TCP-checksum
1065 offloading bugs on certain networking cards when using IPv6.</li>
1066 <li>On Linux on Itanium, sendfile may be unable to handle files
1067 over 2GB in size.</li>
1068 <li>With a network-mounted <code class="directive"><a href="#documentroot">DocumentRoot</a></code> (e.g., NFS, SMB, CIFS, FUSE),
1069 the kernel may be unable to serve the network file through
1073 <p>For server configurations that are not vulnerable to these problems,
1074 you may enable this feature by specifying:</p>
1076 <div class="example"><p><code>
1080 <p>For network mounted files, this feature may be disabled explicitly
1081 for the offending files by specifying:</p>
1083 <div class="example"><p><code>
1084 <Directory "/path-to-nfs-files">
1085 <span class="indent">
1090 <p>Please note that the per-directory and .htaccess configuration
1091 of <code class="directive">EnableSendfile</code> is not supported by
1092 <code class="module"><a href="../mod/mod_cache_disk.html">mod_cache_disk</a></code>.
1093 Only global definition of <code class="directive">EnableSendfile</code>
1094 is taken into account by the module.
1098 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1099 <div class="directive-section"><h2><a name="Error" id="Error">Error</a> <a name="error" id="error">Directiva</a></h2>
1100 <table class="directive">
1101 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Abort configuration parsing with a custom error message</td></tr>
1102 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Error <var>message</var></code></td></tr>
1103 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1104 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1105 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1106 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>2.3.9 and later</td></tr>
1108 <p>If an error can be detected within the configuration, this
1109 directive can be used to generate a custom error message, and halt
1110 configuration parsing. The typical use is for reporting required
1111 modules which are missing from the configuration.</p>
1113 <div class="example"><h3>Example</h3><p><code>
1114 # ensure that mod_include is loaded<br />
1115 <IfModule !include_module><br />
1116 Error mod_include is required by mod_foo. Load it with LoadModule.<br />
1117 </IfModule><br />
1119 # ensure that exactly one of SSL,NOSSL is defined<br />
1120 <IfDefine SSL><br />
1121 <IfDefine NOSSL><br />
1122 Error Both SSL and NOSSL are defined. Define only one of them.<br />
1123 </IfDefine><br />
1124 </IfDefine><br />
1125 <IfDefine !SSL><br />
1126 <IfDefine !NOSSL><br />
1127 Error Either SSL or NOSSL must be defined.<br />
1128 </IfDefine><br />
1129 </IfDefine><br />
1134 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1135 <div class="directive-section"><h2><a name="ErrorDocument" id="ErrorDocument">ErrorDocument</a> <a name="errordocument" id="errordocument">Directiva</a></h2>
1136 <table class="directive">
1137 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>What the server will return to the client
1138 in case of an error</td></tr>
1139 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ErrorDocument <var>error-code</var> <var>document</var></code></td></tr>
1140 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1141 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
1142 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1143 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1145 <p>In the event of a problem or error, Apache httpd can be configured
1146 to do one of four things,</p>
1149 <li>output a simple hardcoded error message</li>
1151 <li>output a customized message</li>
1153 <li>redirect to a local <var>URL-path</var> to handle the
1156 <li>redirect to an external <var>URL</var> to handle the
1160 <p>The first option is the default, while options 2-4 are
1161 configured using the <code class="directive">ErrorDocument</code>
1162 directive, which is followed by the HTTP response code and a URL
1163 or a message. Apache httpd will sometimes offer additional information
1164 regarding the problem/error.</p>
1166 <p>URLs can begin with a slash (/) for local web-paths (relative
1167 to the <code class="directive"><a href="#documentroot">DocumentRoot</a></code>), or be a
1168 full URL which the client can resolve. Alternatively, a message
1169 can be provided to be displayed by the browser. Examples:</p>
1171 <div class="example"><p><code>
1172 ErrorDocument 500 http://foo.example.com/cgi-bin/tester<br />
1173 ErrorDocument 404 /cgi-bin/bad_urls.pl<br />
1174 ErrorDocument 401 /subscription_info.html<br />
1175 ErrorDocument 403 "Sorry can't allow you access today"
1178 <p>Additionally, the special value <code>default</code> can be used
1179 to specify Apache httpd's simple hardcoded message. While not required
1180 under normal circumstances, <code>default</code> will restore
1181 Apache httpd's simple hardcoded message for configurations that would
1182 otherwise inherit an existing <code class="directive">ErrorDocument</code>.</p>
1184 <div class="example"><p><code>
1185 ErrorDocument 404 /cgi-bin/bad_urls.pl<br /><br />
1186 <Directory /web/docs><br />
1187 <span class="indent">
1188 ErrorDocument 404 default<br />
1193 <p>Note that when you specify an <code class="directive">ErrorDocument</code>
1194 that points to a remote URL (ie. anything with a method such as
1195 <code>http</code> in front of it), Apache HTTP Server will send a redirect to the
1196 client to tell it where to find the document, even if the
1197 document ends up being on the same server. This has several
1198 implications, the most important being that the client will not
1199 receive the original error status code, but instead will
1200 receive a redirect status code. This in turn can confuse web
1201 robots and other clients which try to determine if a URL is
1202 valid using the status code. In addition, if you use a remote
1203 URL in an <code>ErrorDocument 401</code>, the client will not
1204 know to prompt the user for a password since it will not
1205 receive the 401 status code. Therefore, <strong>if you use an
1206 <code>ErrorDocument 401</code> directive then it must refer to a local
1207 document.</strong></p>
1209 <p>Microsoft Internet Explorer (MSIE) will by default ignore
1210 server-generated error messages when they are "too small" and substitute
1211 its own "friendly" error messages. The size threshold varies depending on
1212 the type of error, but in general, if you make your error document
1213 greater than 512 bytes, then MSIE will show the server-generated
1214 error rather than masking it. More information is available in
1215 Microsoft Knowledge Base article <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294807">Q294807</a>.</p>
1217 <p>Although most error messages can be overriden, there are certain
1218 circumstances where the internal messages are used regardless of the
1219 setting of <code class="directive"><a href="#errordocument">ErrorDocument</a></code>. In
1220 particular, if a malformed request is detected, normal request processing
1221 will be immediately halted and the internal error message returned.
1222 This is necessary to guard against security problems caused by
1225 <p>If you are using mod_proxy, you may wish to enable
1226 <code class="directive"><a href="../mod/mod_proxy.html#proxyerroroverride">ProxyErrorOverride</a></code> so that you can provide
1227 custom error messages on behalf of your Origin servers. If you don't enable ProxyErrorOverride,
1228 Apache httpd will not generate custom error documents for proxied content.</p>
1230 <h3>Consulte también</h3>
1232 <li><a href="../custom-error.html">documentation of
1233 customizable responses</a></li>
1236 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1237 <div class="directive-section"><h2><a name="ErrorLog" id="ErrorLog">ErrorLog</a> <a name="errorlog" id="errorlog">Directiva</a></h2>
1238 <table class="directive">
1239 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Location where the server will log errors</td></tr>
1240 <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>
1241 <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>
1242 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
1243 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1244 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1246 <p>The <code class="directive">ErrorLog</code> directive sets the name of
1247 the file to which the server will log any errors it encounters. If
1248 the <var>file-path</var> is not absolute then it is assumed to be
1249 relative to the <code class="directive"><a href="#serverroot">ServerRoot</a></code>.</p>
1251 <div class="example"><h3>Example</h3><p><code>
1252 ErrorLog /var/log/httpd/error_log
1255 <p>If the <var>file-path</var>
1256 begins with a pipe character "<code>|</code>" then it is assumed to be a
1257 command to spawn to handle the error log.</p>
1259 <div class="example"><h3>Example</h3><p><code>
1260 ErrorLog "|/usr/local/bin/httpd_errors"
1263 <p>See the notes on <a href="../logs.html#piped">piped logs</a> for
1264 more information.</p>
1266 <p>Using <code>syslog</code> instead of a filename enables logging
1267 via syslogd(8) if the system supports it. The default is to use
1268 syslog facility <code>local7</code>, but you can override this by
1269 using the <code>syslog:<var>facility</var></code> syntax where
1270 <var>facility</var> can be one of the names usually documented in
1271 syslog(1). The facility is effectively global, and if it is changed
1272 in individual virtual hosts, the final facility specified affects the
1275 <div class="example"><h3>Example</h3><p><code>
1276 ErrorLog syslog:user
1279 <p>SECURITY: See the <a href="../misc/security_tips.html#serverroot">security tips</a>
1280 document for details on why your security could be compromised
1281 if the directory where log files are stored is writable by
1282 anyone other than the user that starts the server.</p>
1283 <div class="warning"><h3>Note</h3>
1284 <p>When entering a file path on non-Unix platforms, care should be taken
1285 to make sure that only forward slashed are used even though the platform
1286 may allow the use of back slashes. In general it is a good idea to always
1287 use forward slashes throughout the configuration files.</p>
1290 <h3>Consulte también</h3>
1292 <li><code class="directive"><a href="#loglevel">LogLevel</a></code></li>
1293 <li><a href="../logs.html">Apache HTTP Server Log Files</a></li>
1296 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1297 <div class="directive-section"><h2><a name="ErrorLogFormat" id="ErrorLogFormat">ErrorLogFormat</a> <a name="errorlogformat" id="errorlogformat">Directiva</a></h2>
1298 <table class="directive">
1299 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Format specification for error log entries</td></tr>
1300 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code> ErrorLog [connection|request] <var>format</var></code></td></tr>
1301 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
1302 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1303 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1304 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache httpd 2.3.9 and later</td></tr>
1306 <p><code class="directive">ErrorLogFormat</code> allows to specify what
1307 supplementary information is logged in the error log in addition to the
1308 actual log message.</p>
1310 <div class="example"><h3>Simple example</h3><p><code>
1311 ErrorLogFormat "[%t] [%l] [pid %P] %F: %E: [client %a] %M"
1314 <p>Specifying <code>connection</code> or <code>request</code> as first
1315 paramter allows to specify additional formats, causing additional
1316 information to be logged when the first message is logged for a specific
1317 connection or request, respectivly. This additional information is only
1318 logged once per connection/request. If a connection or request is processed
1319 without causing any log message, the additional information is not logged
1322 <p>It can happen that some format string items do not produce output. For
1323 example, the Referer header is only present if the log message is
1324 associated to a request and the log message happens at a time when the
1325 Referer header has already been read from the client. If no output is
1326 produced, the default behaviour is to delete everything from the preceeding
1327 space character to the next space character. This means the log line is
1328 implicitly divided into fields on non-whitespace to whitespace transitions.
1329 If a format string item does not produce output, the whole field is
1330 ommitted. For example, if the remote address <code>%a</code> in the log
1331 format <code>[%t] [%l] [%a] %M </code> is not available, the surrounding
1332 brackets are not logged either. Space characters can be escaped with a
1333 backslash to prevent them from delimiting a field. The combination '% '
1334 (percent space) is a zero-witdh field delimiter that does not produce any
1337 <p>The above behaviour can be changed by adding modifiers to the format
1338 string item. A <code>-</code> (minus) modifier causes a minus to be logged if the
1339 respective item does not produce any output. In once-per-connection/request
1340 formats, it is also possible to use the <code>+</code> (plus) modifier. If an
1341 item with the plus modifier does not produce any output, the whole line is
1344 <p>A number as modifier can be used to assign a log severity level to a
1345 format item. The item will only be logged if the severity of the log
1346 message is not higher than the specified log severity level. The number can
1347 range from 1 (alert) over 4 (warn) and 7 (debug) to 15 (trace8).</p>
1349 <p>Some format string items accept additional parameters in braces.</p>
1351 <table class="bordered"><tr class="header"><th>Format String</th> <th>Description</th></tr>
1352 <tr><td><code>%%</code></td>
1353 <td>The percent sign</td></tr>
1354 <tr class="odd"><td><code>%...a</code></td>
1355 <td>Remote IP-address and port</td></tr>
1356 <tr><td><code>%...A</code></td>
1357 <td>Local IP-address and port</td></tr>
1358 <tr class="odd"><td><code>%...{name}e</code></td>
1359 <td>Request environment variable <code>name</code></td></tr>
1360 <tr><td><code>%...E</code></td>
1361 <td>APR/OS error status code and string</td></tr>
1362 <tr class="odd"><td><code>%...F</code></td>
1363 <td>Source file name and line number of the log call</td></tr>
1364 <tr><td><code>%...{name}i</code></td>
1365 <td>Request header <code>name</code></td></tr>
1366 <tr class="odd"><td><code>%...k</code></td>
1367 <td>Number of keep-alive requests on this connection</td></tr>
1368 <tr><td><code>%...l</code></td>
1369 <td>Loglevel of the message</td></tr>
1370 <tr class="odd"><td><code>%...L</code></td>
1371 <td>Log ID of the request</td></tr>
1372 <tr><td><code>%...{c}L</code></td>
1373 <td>Log ID of the connection</td></tr>
1374 <tr class="odd"><td><code>%...{C}L</code></td>
1375 <td>Log ID of the connection if used in connection scope, empty otherwise</td></tr>
1376 <tr><td><code>%...m</code></td>
1377 <td>Name of the module logging the message</td></tr>
1378 <tr class="odd"><td><code>%M</code></td>
1379 <td>The actual log message</td></tr>
1380 <tr><td><code>%...{name}n</code></td>
1381 <td>Request note <code>name</code></td></tr>
1382 <tr class="odd"><td><code>%...P</code></td>
1383 <td>Process ID of current process</td></tr>
1384 <tr><td><code>%...T</code></td>
1385 <td>Thread ID of current thread</td></tr>
1386 <tr class="odd"><td><code>%...t</code></td>
1387 <td>The current time</td></tr>
1388 <tr><td><code>%...{u}t</code></td>
1389 <td>The current time including micro-seconds</td></tr>
1390 <tr class="odd"><td><code>%...{cu}t</code></td>
1391 <td>The current time in compact ISO 8601 format, including
1392 micro-seconds</td></tr>
1393 <tr><td><code>%...v</code></td>
1394 <td>The canonical <code class="directive"><a href="#servername">ServerName</a></code>
1395 of the current server.</td></tr>
1396 <tr class="odd"><td><code>%...V</code></td>
1397 <td>The server name of the server serving the request according to the
1398 <code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code>
1400 <tr><td><code>\ </code> (backslash space)</td>
1401 <td>Non-field delimiting space</td></tr>
1402 <tr class="odd"><td><code>% </code> (percent space)</td>
1403 <td>Field delimiter (no output)</td></tr>
1406 <p>The log ID format <code>%L</code> produces a unique id for a connection
1407 or request. This can be used to correlate which log lines belong to the
1408 same connection or request, which request happens on which connection.
1409 A <code>%L</code> format string is also available in
1410 <code class="module"><a href="../mod/mod_log_config.html">mod_log_config</a></code>, to allow to correlate access log entries
1411 with error log lines. If <code class="module"><a href="../mod/mod_unique_id.html">mod_unique_id</a></code> is loaded, its
1412 unique id will be used as log ID for requests.</p>
1414 <div class="example"><h3>Example (somewhat similar to default format)</h3><p><code>
1415 ErrorLogFormat "[%{u}t] [%-m:%l] [pid %P] %7F: %E: [client\ %a]
1416 %M% ,\ referer\ %{Referer}i"
1419 <div class="example"><h3>Example (similar to the 2.2.x format)</h3><p><code>
1420 ErrorLogFormat "[%t] [%l] %7F: %E: [client\ %a]
1421 %M% ,\ referer\ %{Referer}i"
1424 <div class="example"><h3>Advanced example with request/connection log IDs</h3><p><code>
1425 ErrorLogFormat "[%{uc}t] [%-m:%-l] [R:%L] [C:%{C}L] %7F: %E: %M"<br />
1426 ErrorLogFormat request "[%{uc}t] [R:%L] Request %k on C:%{c}L pid:%P tid:%T"<br />
1427 ErrorLogFormat request "[%{uc}t] [R:%L] UA:'%+{User-Agent}i'"<br />
1428 ErrorLogFormat request "[%{uc}t] [R:%L] Referer:'%+{Referer}i'"<br />
1429 ErrorLogFormat connection "[%{uc}t] [C:%{c}L] local\ %a remote\ %A"<br />
1433 <h3>Consulte también</h3>
1435 <li><code class="directive"><a href="#errorlog">ErrorLog</a></code></li>
1436 <li><code class="directive"><a href="#loglevel">LogLevel</a></code></li>
1437 <li><a href="../logs.html">Apache HTTP Server Log Files</a></li>
1440 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1441 <div class="directive-section"><h2><a name="ExtendedStatus" id="ExtendedStatus">ExtendedStatus</a> <a name="extendedstatus" id="extendedstatus">Directiva</a></h2>
1442 <table class="directive">
1443 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Keep track of extended status information for each
1445 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ExtendedStatus On|Off</code></td></tr>
1446 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ExtendedStatus Off[*]</code></td></tr>
1447 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
1448 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1449 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1451 <p>This option tracks additional data per worker about the
1452 currently executing request, and a utilization summary; you
1453 can see these variables during runtime by configuring
1454 <code class="module"><a href="../mod/mod_status.html">mod_status</a></code>. Note that other modules may
1455 rely on this scoreboard.</p>
1457 <p>This setting applies to the entire server, and cannot be
1458 enabled or disabled on a virtualhost-by-virtualhost basis.
1459 The collection of extended status information can slow down
1460 the server. Also note that this setting cannot be changed
1461 during a graceful restart.</p>
1464 <p>Note that loading <code class="module"><a href="../mod/mod_status.html">mod_status</a></code> will change
1465 the default behavior to ExtendedStatus On, while other
1466 third party modules may do the same. Such modules rely on
1467 collecting detailed information about the state of all workers.
1468 The default is changed by <code class="module"><a href="../mod/mod_status.html">mod_status</a></code> beginning
1469 with version 2.3.6; the previous default was always Off.</p>
1474 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1475 <div class="directive-section"><h2><a name="FileETag" id="FileETag">FileETag</a> <a name="fileetag" id="fileetag">Directiva</a></h2>
1476 <table class="directive">
1477 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>File attributes used to create the ETag
1478 HTTP response header for static files</td></tr>
1479 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>FileETag <var>component</var> ...</code></td></tr>
1480 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>FileETag INode MTime Size</code></td></tr>
1481 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1482 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
1483 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1484 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1487 The <code class="directive">FileETag</code> directive configures the file
1488 attributes that are used to create the <code>ETag</code> (entity
1489 tag) response header field when the document is based on a static file.
1490 (The <code>ETag</code> value is used in cache management to save
1491 network bandwidth.) The
1492 <code class="directive">FileETag</code> directive allows you to choose
1493 which of these -- if any -- should be used. The recognized keywords are:
1497 <dt><strong>INode</strong></dt>
1498 <dd>The file's i-node number will be included in the calculation</dd>
1499 <dt><strong>MTime</strong></dt>
1500 <dd>The date and time the file was last modified will be included</dd>
1501 <dt><strong>Size</strong></dt>
1502 <dd>The number of bytes in the file will be included</dd>
1503 <dt><strong>All</strong></dt>
1504 <dd>All available fields will be used. This is equivalent to:
1505 <div class="example"><p><code>FileETag INode MTime Size</code></p></div></dd>
1506 <dt><strong>None</strong></dt>
1507 <dd>If a document is file-based, no <code>ETag</code> field will be
1508 included in the response</dd>
1511 <p>The <code>INode</code>, <code>MTime</code>, and <code>Size</code>
1512 keywords may be prefixed with either <code>+</code> or <code>-</code>,
1513 which allow changes to be made to the default setting inherited
1514 from a broader scope. Any keyword appearing without such a prefix
1515 immediately and completely cancels the inherited setting.</p>
1517 <p>If a directory's configuration includes
1518 <code>FileETag INode MTime Size</code>, and a
1519 subdirectory's includes <code>FileETag -INode</code>,
1520 the setting for that subdirectory (which will be inherited by
1521 any sub-subdirectories that don't override it) will be equivalent to
1522 <code>FileETag MTime Size</code>.</p>
1523 <div class="warning"><h3>Warning</h3>
1524 Do not change the default for directories or locations that have WebDAV
1525 enabled and use <code class="module"><a href="../mod/mod_dav_fs.html">mod_dav_fs</a></code> as a storage provider.
1526 <code class="module"><a href="../mod/mod_dav_fs.html">mod_dav_fs</a></code> uses <code>INode MTime Size</code>
1527 as a fixed format for <code>ETag</code> comparisons on conditional requests.
1528 These conditional requests will break if the <code>ETag</code> format is
1529 changed via <code class="directive">FileETag</code>.
1531 <div class="note"><h3>Server Side Includes</h3>
1532 An ETag is not generated for responses parsed by <code class="module"><a href="../mod/mod_include.html">mod_include</a></code>,
1533 since the response entity can change without a change of the INode, MTime, or Size
1534 of the static file with embedded SSI directives.
1539 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1540 <div class="directive-section"><h2><a name="Files" id="Files"><Files></a> <a name="files" id="files">Directiva</a></h2>
1541 <table class="directive">
1542 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply to matched
1544 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><Files <var>filename</var>> ... </Files></code></td></tr>
1545 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1546 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
1547 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1548 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1550 <p>The <code class="directive"><Files></code> directive
1551 limits the scope of the enclosed directives by filename. It is comparable
1552 to the <code class="directive"><a href="#directory"><Directory></a></code>
1553 and <code class="directive"><a href="#location"><Location></a></code>
1554 directives. It should be matched with a <code></Files></code>
1555 directive. The directives given within this section will be applied to
1556 any object with a basename (last component of filename) matching the
1557 specified filename. <code class="directive"><Files></code>
1558 sections are processed in the order they appear in the
1559 configuration file, after the <code class="directive"><a href="#directory"><Directory></a></code> sections and
1560 <code>.htaccess</code> files are read, but before <code class="directive"><a href="#location"><Location></a></code> sections. Note
1561 that <code class="directive"><Files></code> can be nested
1562 inside <code class="directive"><a href="#directory"><Directory></a></code> sections to restrict the
1563 portion of the filesystem they apply to.</p>
1565 <p>The <var>filename</var> argument should include a filename, or
1566 a wild-card string, where <code>?</code> matches any single character,
1567 and <code>*</code> matches any sequences of characters.
1568 <a class="glossarylink" href="../glossary.html#regex" title="ver glosario">Regular expressions</a>
1569 can also be used, with the addition of the
1570 <code>~</code> character. For example:</p>
1572 <div class="example"><p><code>
1573 <Files ~ "\.(gif|jpe?g|png)$">
1576 <p>would match most common Internet graphics formats. <code class="directive"><a href="#filesmatch"><FilesMatch></a></code> is preferred,
1579 <p>Note that unlike <code class="directive"><a href="#directory"><Directory></a></code> and <code class="directive"><a href="#location"><Location></a></code> sections, <code class="directive"><Files></code> sections can be used inside
1580 <code>.htaccess</code> files. This allows users to control access to
1581 their own files, at a file-by-file level.</p>
1584 <h3>Consulte también</h3>
1586 <li><a href="../sections.html">How <Directory>, <Location>
1587 and <Files> sections work</a> for an explanation of how these
1588 different sections are combined when a request is received</li>
1591 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1592 <div class="directive-section"><h2><a name="FilesMatch" id="FilesMatch"><FilesMatch></a> <a name="filesmatch" id="filesmatch">Directiva</a></h2>
1593 <table class="directive">
1594 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply to regular-expression matched
1596 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><FilesMatch <var>regex</var>> ... </FilesMatch></code></td></tr>
1597 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1598 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
1599 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1600 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1602 <p>The <code class="directive"><FilesMatch></code> directive
1603 limits the scope of the enclosed directives by filename, just as the
1604 <code class="directive"><a href="#files"><Files></a></code> directive
1605 does. However, it accepts a <a class="glossarylink" href="../glossary.html#regex" title="ver glosario">regular
1606 expression</a>. For example:</p>
1608 <div class="example"><p><code>
1609 <FilesMatch "\.(gif|jpe?g|png)$">
1612 <p>would match most common Internet graphics formats.</p>
1614 <h3>Consulte también</h3>
1616 <li><a href="../sections.html">How <Directory>, <Location>
1617 and <Files> sections work</a> for an explanation of how these
1618 different sections are combined when a request is received</li>
1621 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1622 <div class="directive-section"><h2><a name="ForceType" id="ForceType">ForceType</a> <a name="forcetype" id="forcetype">Directiva</a></h2>
1623 <table class="directive">
1624 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Forces all matching files to be served with the specified
1625 media type in the HTTP Content-Type header field</td></tr>
1626 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ForceType <var>media-type</var>|None</code></td></tr>
1627 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
1628 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
1629 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1630 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1631 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Moved to the core in Apache httpd 2.0</td></tr>
1633 <p>When placed into an <code>.htaccess</code> file or a
1634 <code class="directive"><a href="#directory"><Directory></a></code>, or
1635 <code class="directive"><a href="#location"><Location></a></code> or
1636 <code class="directive"><a href="#files"><Files></a></code>
1637 section, this directive forces all matching files to be served
1638 with the content type identification given by
1639 <var>media-type</var>. For example, if you had a directory full of
1640 GIF files, but did not want to label them all with <code>.gif</code>,
1641 you might want to use:</p>
1643 <div class="example"><p><code>
1647 <p>Note that this directive overrides other indirect media type
1648 associations defined in mime.types or via the
1649 <code class="directive"><a href="../mod/mod_mime.html#addtype">AddType</a></code>.</p>
1651 <p>You can also override more general
1652 <code class="directive">ForceType</code> settings
1653 by using the value of <code>None</code>:</p>
1655 <div class="example"><p><code>
1656 # force all files to be image/gif:<br />
1657 <Location /images><br />
1658 <span class="indent">
1659 ForceType image/gif<br />
1661 </Location><br />
1663 # but normal mime-type associations here:<br />
1664 <Location /images/mixed><br />
1665 <span class="indent">
1666 ForceType None<br />
1671 <p>This directive primarily overrides the content types generated for
1672 static files served out of the filesystem. For resources other than
1673 static files, where the generator of the response typically specifies
1674 a Content-Type, this directive has no effect.</p>
1678 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1679 <div class="directive-section"><h2><a name="GprofDir" id="GprofDir">GprofDir</a> <a name="gprofdir" id="gprofdir">Directiva</a></h2>
1680 <table class="directive">
1681 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Directory to write gmon.out profiling data to. </td></tr>
1682 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>GprofDir <var>/tmp/gprof/</var>|<var>/tmp/gprof/</var>%</code></td></tr>
1683 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
1684 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1685 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1687 <p>When the server has been compiled with gprof profiling support,
1688 <code class="directive">GprofDir</code> causes <code>gmon.out</code> files to
1689 be written to the specified directory when the process exits. If the
1690 argument ends with a percent symbol ('%'), subdirectories are created
1691 for each process id.</p>
1693 <p>This directive currently only works with the <code class="module"><a href="../mod/prefork.html">prefork</a></code>
1697 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1698 <div class="directive-section"><h2><a name="HostnameLookups" id="HostnameLookups">HostnameLookups</a> <a name="hostnamelookups" id="hostnamelookups">Directiva</a></h2>
1699 <table class="directive">
1700 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enables DNS lookups on client IP addresses</td></tr>
1701 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>HostnameLookups On|Off|Double</code></td></tr>
1702 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>HostnameLookups Off</code></td></tr>
1703 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
1704 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1705 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1707 <p>This directive enables DNS lookups so that host names can be
1708 logged (and passed to CGIs/SSIs in <code>REMOTE_HOST</code>).
1709 The value <code>Double</code> refers to doing double-reverse
1710 DNS lookup. That is, after a reverse lookup is performed, a forward
1711 lookup is then performed on that result. At least one of the IP
1712 addresses in the forward lookup must match the original
1713 address. (In "tcpwrappers" terminology this is called
1714 <code>PARANOID</code>.)</p>
1716 <p>Regardless of the setting, when <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code> is
1717 used for controlling access by hostname, a double reverse lookup
1718 will be performed. This is necessary for security. Note that the
1719 result of this double-reverse isn't generally available unless you
1720 set <code>HostnameLookups Double</code>. For example, if only
1721 <code>HostnameLookups On</code> and a request is made to an object
1722 that is protected by hostname restrictions, regardless of whether
1723 the double-reverse fails or not, CGIs will still be passed the
1724 single-reverse result in <code>REMOTE_HOST</code>.</p>
1726 <p>The default is <code>Off</code> in order to save the network
1727 traffic for those sites that don't truly need the reverse
1728 lookups done. It is also better for the end users because they
1729 don't have to suffer the extra latency that a lookup entails.
1730 Heavily loaded sites should leave this directive
1731 <code>Off</code>, since DNS lookups can take considerable
1732 amounts of time. The utility <code class="program"><a href="../programs/logresolve.html">logresolve</a></code>, compiled by
1733 default to the <code>bin</code> subdirectory of your installation
1734 directory, can be used to look up host names from logged IP addresses
1738 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1739 <div class="directive-section"><h2><a name="HTTPProtocolOptions" id="HTTPProtocolOptions">HTTPProtocolOptions</a> <a name="httpprotocoloptions" id="httpprotocoloptions">Directiva</a></h2>
1740 <table class="directive">
1741 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Modify restrictions on HTTP Request Messages</td></tr>
1742 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>HTTPProtocolOptions [Strict|Unsafe] [Allow0.9|Require1.0]
1743 [StrictWhitespace|LenientWhitespace] [RegisteredMethods|LenientMethods]</code></td></tr>
1744 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>HTTPProtocolOptions Strict Allow0.9 LenientWhitespace
1745 LenientMethods</code></td></tr>
1746 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
1747 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1748 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1749 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>2.2.32 or 2.4.24 and later</td></tr>
1750 </table><p>The documentation for this directive has
1751 not been translated yet. Please have a look at the English
1753 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1754 <div class="directive-section"><h2><a name="If" id="If"><If></a> <a name="if" id="if">Directiva</a></h2>
1755 <table class="directive">
1756 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply only if a condition is
1757 satisfied by a request at runtime</td></tr>
1758 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><If <var>expression</var>> ... </If></code></td></tr>
1759 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1760 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
1761 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1762 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1764 <p>The <code class="directive"><If></code> directive
1765 evaluates an expression at runtime, and applies the enclosed
1766 directives if and only if the expression evaluates to true.
1769 <div class="example"><p><code>
1770 <If "$req{Host} = ''">
1773 <p>would match HTTP/1.0 requests without a <var>Host:</var> header.</p>
1775 <p>You may compare the value of any variable in the request headers
1776 ($req), response headers ($resp) or environment ($env) in your
1779 <p>Apart from <code>=</code>, <code>If</code> can use the <code>IN</code>
1780 operator to compare if the expression is in a given range:</p>
1782 <div class="example"><p><code>
1783 <If %{REQUEST_METHOD} IN GET,HEAD,OPTIONS>
1787 <h3>Consulte también</h3>
1789 <li><a href="../expr.html">Expressions in Apache HTTP Server</a>,
1790 for a complete reference and more examples.</li>
1791 <li><a href="../sections.html">How <Directory>, <Location>,
1792 <Files> sections work</a> for an explanation of how these
1793 different sections are combined when a request is received.
1794 <code class="directive"><If></code> has the same precedence
1795 and usage as <code class="directive"><Files></code></li>
1798 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1799 <div class="directive-section"><h2><a name="IfDefine" id="IfDefine"><IfDefine></a> <a name="ifdefine" id="ifdefine">Directiva</a></h2>
1800 <table class="directive">
1801 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Encloses directives that will be processed only
1802 if a test is true at startup</td></tr>
1803 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><IfDefine [!]<var>parameter-name</var>> ...
1804 </IfDefine></code></td></tr>
1805 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1806 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
1807 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1808 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1810 <p>The <code><IfDefine <var>test</var>>...</IfDefine>
1811 </code> section is used to mark directives that are conditional. The
1812 directives within an <code class="directive"><IfDefine></code>
1813 section are only processed if the <var>test</var> is true. If <var>
1814 test</var> is false, everything between the start and end markers is
1817 <p>The <var>test</var> in the <code class="directive"><IfDefine></code> section directive can be one of two forms:</p>
1820 <li><var>parameter-name</var></li>
1822 <li><code>!</code><var>parameter-name</var></li>
1825 <p>In the former case, the directives between the start and end
1826 markers are only processed if the parameter named
1827 <var>parameter-name</var> is defined. The second format reverses
1828 the test, and only processes the directives if
1829 <var>parameter-name</var> is <strong>not</strong> defined.</p>
1831 <p>The <var>parameter-name</var> argument is a define as given on the
1832 <code class="program"><a href="../programs/httpd.html">httpd</a></code> command line via <code>-D<var>parameter</var>
1833 </code> at the time the server was started or by the <code class="directive"><a href="#define">Define</a></code> directive.</p>
1835 <p><code class="directive"><IfDefine></code> sections are
1836 nest-able, which can be used to implement simple
1837 multiple-parameter tests. Example:</p>
1839 <div class="example"><p><code>
1840 httpd -DReverseProxy -DUseCache -DMemCache ...<br />
1843 <IfDefine ReverseProxy><br />
1844 <span class="indent">
1845 LoadModule proxy_module modules/mod_proxy.so<br />
1846 LoadModule proxy_http_module modules/mod_proxy_http.so<br />
1847 <IfDefine UseCache><br />
1848 <span class="indent">
1849 LoadModule cache_module modules/mod_cache.so<br />
1850 <IfDefine MemCache><br />
1851 <span class="indent">
1852 LoadModule mem_cache_module modules/mod_mem_cache.so<br />
1854 </IfDefine><br />
1855 <IfDefine !MemCache><br />
1856 <span class="indent">
1857 LoadModule cache_disk_module modules/mod_cache_disk.so<br />
1867 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1868 <div class="directive-section"><h2><a name="IfModule" id="IfModule"><IfModule></a> <a name="ifmodule" id="ifmodule">Directiva</a></h2>
1869 <table class="directive">
1870 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Encloses directives that are processed conditional on the
1871 presence or absence of a specific module</td></tr>
1872 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><IfModule [!]<var>module-file</var>|<var>module-identifier</var>> ...
1873 </IfModule></code></td></tr>
1874 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1875 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
1876 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1877 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1878 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Module identifiers are available in version 2.1 and
1881 <p>The <code><IfModule <var>test</var>>...</IfModule></code>
1882 section is used to mark directives that are conditional on the presence of
1883 a specific module. The directives within an <code class="directive"><IfModule></code> section are only processed if the <var>test</var>
1884 is true. If <var>test</var> is false, everything between the start and
1885 end markers is ignored.</p>
1887 <p>The <var>test</var> in the <code class="directive"><IfModule></code> section directive can be one of two forms:</p>
1890 <li><var>module</var></li>
1892 <li>!<var>module</var></li>
1895 <p>In the former case, the directives between the start and end
1896 markers are only processed if the module named <var>module</var>
1897 is included in Apache httpd -- either compiled in or
1898 dynamically loaded using <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code>. The second format reverses the test,
1899 and only processes the directives if <var>module</var> is
1900 <strong>not</strong> included.</p>
1902 <p>The <var>module</var> argument can be either the module identifier or
1903 the file name of the module, at the time it was compiled. For example,
1904 <code>rewrite_module</code> is the identifier and
1905 <code>mod_rewrite.c</code> is the file name. If a module consists of
1906 several source files, use the name of the file containing the string
1907 <code>STANDARD20_MODULE_STUFF</code>.</p>
1909 <p><code class="directive"><IfModule></code> sections are
1910 nest-able, which can be used to implement simple multiple-module
1913 <div class="note">This section should only be used if you need to have one
1914 configuration file that works whether or not a specific module
1915 is available. In normal operation, directives need not be
1916 placed in <code class="directive"><IfModule></code>
1920 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1921 <div class="directive-section"><h2><a name="Include" id="Include">Include</a> <a name="include" id="include">Directiva</a></h2>
1922 <table class="directive">
1923 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Includes other configuration files from within
1924 the server configuration files</td></tr>
1925 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Include [<var>optional</var>|<var>strict</var>] <var>file-path</var>|<var>directory-path</var>|<var>wildcard</var></code></td></tr>
1926 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
1927 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1928 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1929 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Wildcard matching available in 2.0.41 and later, directory
1930 wildcard matching available in 2.3.6 and later</td></tr>
1932 <p>This directive allows inclusion of other configuration files
1933 from within the server configuration files.</p>
1935 <p>Shell-style (<code>fnmatch()</code>) wildcard characters can be used
1936 in the filename or directory parts of the path to include several files
1937 at once, in alphabetical order. In addition, if
1938 <code class="directive">Include</code> points to a directory, rather than a file,
1939 Apache httpd will read all files in that directory and any subdirectory.
1940 However, including entire directories is not recommended, because it is
1941 easy to accidentally leave temporary files in a directory that can cause
1942 <code class="program"><a href="../programs/httpd.html">httpd</a></code> to fail. Instead, we encourage you to use the
1943 wildcard syntax shown below, to include files that match a particular
1944 pattern, such as *.conf, for example.</p>
1946 <p>When a wildcard is specified for a <strong>file</strong> component of
1947 the path, and no file matches the wildcard, the
1948 <code class="directive"><a href="#include">Include</a></code>
1949 directive will be <strong>silently ignored</strong>. When a wildcard is
1950 specified for a <strong>directory</strong> component of the path, and
1951 no directory matches the wildcard, the
1952 <code class="directive"><a href="#include">Include</a></code> directive will
1953 <strong>fail with an error</strong> saying the directory cannot be found.
1956 <p>For further control over the behaviour of the server when no files or
1957 directories match, prefix the path with the modifiers <var>optional</var>
1958 or <var>strict</var>. If <var>optional</var> is specified, any wildcard
1959 file or directory that does not match will be silently ignored. If
1960 <var>strict</var> is specified, any wildcard file or directory that does
1961 not match at least one file will cause server startup to fail.</p>
1963 <p>When a directory or file component of the path is
1964 specified exactly, and that directory or file does not exist,
1965 <code class="directive"><a href="#include">Include</a></code> directive will fail with an
1966 error saying the file or directory cannot be found.</p>
1968 <p>The file path specified may be an absolute path, or may be relative
1969 to the <code class="directive"><a href="#serverroot">ServerRoot</a></code> directory.</p>
1973 <div class="example"><p><code>
1974 Include /usr/local/apache2/conf/ssl.conf<br />
1975 Include /usr/local/apache2/conf/vhosts/*.conf
1978 <p>Or, providing paths relative to your <code class="directive"><a href="#serverroot">ServerRoot</a></code> directory:</p>
1980 <div class="example"><p><code>
1981 Include conf/ssl.conf<br />
1982 Include conf/vhosts/*.conf
1985 <p>Wildcards may be included in the directory or file portion of the
1986 path. In the following example, the server will fail to load if no
1987 directories match conf/vhosts/*, but will load successfully if no
1988 files match *.conf.</p>
1990 <div class="example"><p><code>
1991 Include conf/vhosts/*/vhost.conf<br />
1992 Include conf/vhosts/*/*.conf
1995 <p>In this example, the server will fail to load if either
1996 conf/vhosts/* matches no directories, or if *.conf matches no files:</p>
1998 <div class="example"><p><code>
1999 Include strict conf/vhosts/*/*.conf
2002 <p>In this example, the server load successfully if either conf/vhosts/*
2003 matches no directories, or if *.conf matches no files:</p>
2005 <div class="example"><p><code>
2006 Include optional conf/vhosts/*/*.conf
2010 <h3>Consulte también</h3>
2012 <li><code class="program"><a href="../programs/apachectl.html">apachectl</a></code></li>
2015 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2016 <div class="directive-section"><h2><a name="IncludeOptional" id="IncludeOptional">IncludeOptional</a> <a name="includeoptional" id="includeoptional">Directiva</a></h2>
2017 <table class="directive">
2018 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Includes other configuration files from within
2019 the server configuration files</td></tr>
2020 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>IncludeOptional <var>file-path</var>|<var>directory-path</var>|<var>wildcard</var></code></td></tr>
2021 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
2022 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2023 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2024 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in 2.3.6 and later</td></tr>
2025 </table><p>The documentation for this directive has
2026 not been translated yet. Please have a look at the English
2027 version.</p><h3>Consulte también</h3>
2029 <li><code class="directive"><a href="#include">Include</a></code></li>
2030 <li><code class="program"><a href="../programs/apachectl.html">apachectl</a></code></li>
2033 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2034 <div class="directive-section"><h2><a name="KeepAlive" id="KeepAlive">KeepAlive</a> <a name="keepalive" id="keepalive">Directiva</a></h2>
2035 <table class="directive">
2036 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enables HTTP persistent connections</td></tr>
2037 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>KeepAlive On|Off</code></td></tr>
2038 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>KeepAlive On</code></td></tr>
2039 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2040 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2041 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2043 <p>The Keep-Alive extension to HTTP/1.0 and the persistent
2044 connection feature of HTTP/1.1 provide long-lived HTTP sessions
2045 which allow multiple requests to be sent over the same TCP
2046 connection. In some cases this has been shown to result in an
2047 almost 50% speedup in latency times for HTML documents with
2048 many images. To enable Keep-Alive connections, set
2049 <code>KeepAlive On</code>.</p>
2051 <p>For HTTP/1.0 clients, Keep-Alive connections will only be
2052 used if they are specifically requested by a client. In
2053 addition, a Keep-Alive connection with an HTTP/1.0 client can
2054 only be used when the length of the content is known in
2055 advance. This implies that dynamic content such as CGI output,
2056 SSI pages, and server-generated directory listings will
2057 generally not use Keep-Alive connections to HTTP/1.0 clients.
2058 For HTTP/1.1 clients, persistent connections are the default
2059 unless otherwise specified. If the client requests it, chunked
2060 encoding will be used in order to send content of unknown
2061 length over persistent connections.</p>
2063 <p>When a client uses a Keep-Alive connection it will be counted
2064 as a single "request" for the <code class="directive"><a href="../mod/mpm_common.html#maxconnectionsperchild">MaxConnectionsPerChild</a></code> directive, regardless
2065 of how many requests are sent using the connection.</p>
2067 <h3>Consulte también</h3>
2069 <li><code class="directive"><a href="#maxkeepaliverequests">MaxKeepAliveRequests</a></code></li>
2072 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2073 <div class="directive-section"><h2><a name="KeepAliveTimeout" id="KeepAliveTimeout">KeepAliveTimeout</a> <a name="keepalivetimeout" id="keepalivetimeout">Directiva</a></h2>
2074 <table class="directive">
2075 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Amount of time the server will wait for subsequent
2076 requests on a persistent connection</td></tr>
2077 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>KeepAliveTimeout <var>num</var>[ms]</code></td></tr>
2078 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>KeepAliveTimeout 5</code></td></tr>
2079 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2080 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2081 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2082 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Specifying a value in milliseconds is available in
2083 Apache httpd 2.3.2 and later</td></tr>
2085 <p>The number of seconds Apache httpd will wait for a subsequent
2086 request before closing the connection. By adding a postfix of ms the
2087 timeout can be also set in milliseconds. Once a request has been
2088 received, the timeout value specified by the
2089 <code class="directive"><a href="#timeout">Timeout</a></code> directive applies.</p>
2091 <p>Setting <code class="directive">KeepAliveTimeout</code> to a high value
2092 may cause performance problems in heavily loaded servers. The
2093 higher the timeout, the more server processes will be kept
2094 occupied waiting on connections with idle clients.</p>
2096 <p>In a name-based virtual host context, the value of the first
2097 defined virtual host (the default host) in a set of <code class="directive"><a href="#namevirtualhost">NameVirtualHost</a></code> will be used.
2098 The other values will be ignored.</p>
2101 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2102 <div class="directive-section"><h2><a name="Limit" id="Limit"><Limit></a> <a name="limit" id="limit">Directiva</a></h2>
2103 <table class="directive">
2104 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Restrict enclosed access controls to only certain HTTP
2106 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><Limit <var>method</var> [<var>method</var>] ... > ...
2107 </Limit></code></td></tr>
2108 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
2109 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>AuthConfig, Limit</td></tr>
2110 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2111 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2113 <p>Access controls are normally effective for
2114 <strong>all</strong> access methods, and this is the usual
2115 desired behavior. <strong>In the general case, access control
2116 directives should not be placed within a
2117 <code class="directive"><Limit></code> section.</strong></p>
2119 <p>The purpose of the <code class="directive"><Limit></code>
2120 directive is to restrict the effect of the access controls to the
2121 nominated HTTP methods. For all other methods, the access
2122 restrictions that are enclosed in the <code class="directive"><Limit></code> bracket <strong>will have no
2123 effect</strong>. The following example applies the access control
2124 only to the methods <code>POST</code>, <code>PUT</code>, and
2125 <code>DELETE</code>, leaving all other methods unprotected:</p>
2127 <div class="example"><p><code>
2128 <Limit POST PUT DELETE><br />
2129 <span class="indent">
2130 Require valid-user<br />
2135 <p>The method names listed can be one or more of: <code>GET</code>,
2136 <code>POST</code>, <code>PUT</code>, <code>DELETE</code>,
2137 <code>CONNECT</code>, <code>OPTIONS</code>,
2138 <code>PATCH</code>, <code>PROPFIND</code>, <code>PROPPATCH</code>,
2139 <code>MKCOL</code>, <code>COPY</code>, <code>MOVE</code>,
2140 <code>LOCK</code>, and <code>UNLOCK</code>. <strong>The method name is
2141 case-sensitive.</strong> If <code>GET</code> is used it will also
2142 restrict <code>HEAD</code> requests. The <code>TRACE</code> method
2143 cannot be limited (see <code class="directive"><a href="#traceenable">TraceEnable</a></code>).</p>
2145 <div class="warning">A <code class="directive"><a href="#limitexcept"><LimitExcept></a></code> section should always be
2146 used in preference to a <code class="directive"><Limit></code>
2147 section when restricting access, since a <code class="directive"><a href="#limitexcept"><LimitExcept></a></code> section provides protection
2148 against arbitrary methods.</div>
2150 <p>The <code class="directive"><Limit></code> and
2151 <code class="directive"><a href="#limitexcept"><LimitExcept></a></code>
2152 directives may be nested. In this case, each successive level of
2153 <code class="directive"><Limit></code> or <code class="directive"><a href="#limitexcept"><LimitExcept></a></code> directives must
2154 further restrict the set of methods to which access controls apply.</p>
2156 <div class="warning">When using
2157 <code class="directive"><Limit></code> or
2158 <code class="directive"><LimitExcept></code> directives with
2159 the <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> directive,
2160 note that the first <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>
2161 to succeed authorizes the request, regardless of the presence of other
2162 <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> directives.</div>
2164 <p>For example, given the following configuration, all users will
2165 be authorized for <code>POST</code> requests, and the
2166 <code>Require group editors</code> directive will be ignored
2169 <div class="example"><p><code>
2170 <LimitExcept GET>
2171 <span class="indent">
2174 </LimitExcept><br />
2176 <span class="indent">
2177 Require group editors
2183 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2184 <div class="directive-section"><h2><a name="LimitExcept" id="LimitExcept"><LimitExcept></a> <a name="limitexcept" id="limitexcept">Directiva</a></h2>
2185 <table class="directive">
2186 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Restrict access controls to all HTTP methods
2187 except the named ones</td></tr>
2188 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><LimitExcept <var>method</var> [<var>method</var>] ... > ...
2189 </LimitExcept></code></td></tr>
2190 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
2191 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>AuthConfig, Limit</td></tr>
2192 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2193 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2195 <p><code class="directive"><LimitExcept></code> and
2196 <code></LimitExcept></code> are used to enclose
2197 a group of access control directives which will then apply to any
2198 HTTP access method <strong>not</strong> listed in the arguments;
2199 i.e., it is the opposite of a <code class="directive"><a href="#limit"><Limit></a></code> section and can be used to control
2200 both standard and nonstandard/unrecognized methods. See the
2201 documentation for <code class="directive"><a href="#limit"><Limit></a></code> for more details.</p>
2205 <div class="example"><p><code>
2206 <LimitExcept POST GET><br />
2207 <span class="indent">
2208 Require valid-user<br />
2210 </LimitExcept>
2215 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2216 <div class="directive-section"><h2><a name="LimitInternalRecursion" id="LimitInternalRecursion">LimitInternalRecursion</a> <a name="limitinternalrecursion" id="limitinternalrecursion">Directiva</a></h2>
2217 <table class="directive">
2218 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determine maximum number of internal redirects and nested
2219 subrequests</td></tr>
2220 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitInternalRecursion <var>number</var> [<var>number</var>]</code></td></tr>
2221 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitInternalRecursion 10</code></td></tr>
2222 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2223 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2224 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2225 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache httpd 2.0.47 and later</td></tr>
2227 <p>An internal redirect happens, for example, when using the <code class="directive"><a href="../mod/mod_actions.html#action">Action</a></code> directive, which internally
2228 redirects the original request to a CGI script. A subrequest is Apache httpd's
2229 mechanism to find out what would happen for some URI if it were requested.
2230 For example, <code class="module"><a href="../mod/mod_dir.html">mod_dir</a></code> uses subrequests to look for the
2231 files listed in the <code class="directive"><a href="../mod/mod_dir.html#directoryindex">DirectoryIndex</a></code>
2234 <p><code class="directive">LimitInternalRecursion</code> prevents the server
2235 from crashing when entering an infinite loop of internal redirects or
2236 subrequests. Such loops are usually caused by misconfigurations.</p>
2238 <p>The directive stores two different limits, which are evaluated on
2239 per-request basis. The first <var>number</var> is the maximum number of
2240 internal redirects, that may follow each other. The second <var>number</var>
2241 determines, how deep subrequests may be nested. If you specify only one
2242 <var>number</var>, it will be assigned to both limits.</p>
2244 <div class="example"><h3>Example</h3><p><code>
2245 LimitInternalRecursion 5
2249 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2250 <div class="directive-section"><h2><a name="LimitRequestBody" id="LimitRequestBody">LimitRequestBody</a> <a name="limitrequestbody" id="limitrequestbody">Directiva</a></h2>
2251 <table class="directive">
2252 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Restricts the total size of the HTTP request body sent
2253 from the client</td></tr>
2254 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitRequestBody <var>bytes</var></code></td></tr>
2255 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitRequestBody 0</code></td></tr>
2256 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
2257 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
2258 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2259 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2261 <p>This directive specifies the number of <var>bytes</var> from 0
2262 (meaning unlimited) to 2147483647 (2GB) that are allowed in a
2263 request body. See the note below for the limited applicability
2264 to proxy requests.</p>
2266 <p>The <code class="directive">LimitRequestBody</code> directive allows
2267 the user to set a limit on the allowed size of an HTTP request
2268 message body within the context in which the directive is given
2269 (server, per-directory, per-file or per-location). If the client
2270 request exceeds that limit, the server will return an error
2271 response instead of servicing the request. The size of a normal
2272 request message body will vary greatly depending on the nature of
2273 the resource and the methods allowed on that resource. CGI scripts
2274 typically use the message body for retrieving form information.
2275 Implementations of the <code>PUT</code> method will require
2276 a value at least as large as any representation that the server
2277 wishes to accept for that resource.</p>
2279 <p>This directive gives the server administrator greater
2280 control over abnormal client request behavior, which may be
2281 useful for avoiding some forms of denial-of-service
2284 <p>If, for example, you are permitting file upload to a particular
2285 location, and wish to limit the size of the uploaded file to 100K,
2286 you might use the following directive:</p>
2288 <div class="example"><p><code>
2289 LimitRequestBody 102400
2292 <div class="note"><p>For a full description of how this directive is interpreted by
2293 proxy requests, see the <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> documentation.</p>
2298 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2299 <div class="directive-section"><h2><a name="LimitRequestFields" id="LimitRequestFields">LimitRequestFields</a> <a name="limitrequestfields" id="limitrequestfields">Directiva</a></h2>
2300 <table class="directive">
2301 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the number of HTTP request header fields that
2302 will be accepted from the client</td></tr>
2303 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitRequestFields <var>number</var></code></td></tr>
2304 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitRequestFields 100</code></td></tr>
2305 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2306 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2307 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2309 <p><var>Number</var> is an integer from 0 (meaning unlimited) to
2310 32767. The default value is defined by the compile-time
2311 constant <code>DEFAULT_LIMIT_REQUEST_FIELDS</code> (100 as
2314 <p>The <code class="directive">LimitRequestFields</code> directive allows
2315 the server administrator to modify the limit on the number of
2316 request header fields allowed in an HTTP request. A server needs
2317 this value to be larger than the number of fields that a normal
2318 client request might include. The number of request header fields
2319 used by a client rarely exceeds 20, but this may vary among
2320 different client implementations, often depending upon the extent
2321 to which a user has configured their browser to support detailed
2322 content negotiation. Optional HTTP extensions are often expressed
2323 using request header fields.</p>
2325 <p>This directive gives the server administrator greater
2326 control over abnormal client request behavior, which may be
2327 useful for avoiding some forms of denial-of-service attacks.
2328 The value should be increased if normal clients see an error
2329 response from the server that indicates too many fields were
2330 sent in the request.</p>
2334 <div class="example"><p><code>
2335 LimitRequestFields 50
2338 <div class="warning"><h3>Warning</h3>
2339 <p> When name-based virtual hosting is used, the value for this
2340 directive is taken from the default (first-listed) virtual host for the
2341 <code class="directive">NameVirtualHost</code> the connection was mapped to.</p>
2346 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2347 <div class="directive-section"><h2><a name="LimitRequestFieldSize" id="LimitRequestFieldSize">LimitRequestFieldSize</a> <a name="limitrequestfieldsize" id="limitrequestfieldsize">Directiva</a></h2>
2348 <table class="directive">
2349 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the size of the HTTP request header allowed from the
2351 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitRequestFieldSize <var>bytes</var></code></td></tr>
2352 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitRequestFieldSize 8190</code></td></tr>
2353 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2354 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2355 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2357 <p>This directive specifies the number of <var>bytes</var>
2358 that will be allowed in an HTTP request header.</p>
2360 <p>The <code class="directive">LimitRequestFieldSize</code> directive
2361 allows the server administrator to reduce or increase the limit
2362 on the allowed size of an HTTP request header field. A server
2363 needs this value to be large enough to hold any one header field
2364 from a normal client request. The size of a normal request header
2365 field will vary greatly among different client implementations,
2366 often depending upon the extent to which a user has configured
2367 their browser to support detailed content negotiation. SPNEGO
2368 authentication headers can be up to 12392 bytes.</p>
2370 <p>This directive gives the server administrator greater
2371 control over abnormal client request behavior, which may be
2372 useful for avoiding some forms of denial-of-service attacks.</p>
2376 <div class="example"><p><code>
2377 LimitRequestFieldSize 4094
2380 <div class="note">Under normal conditions, the value should not be changed from
2383 <div class="warning"><h3>Warning</h3>
2384 <p> When name-based virtual hosting is used, the value for this
2385 directive is taken from the default (first-listed) virtual host for the
2386 <code class="directive">NameVirtualHost</code> the connection was mapped to.</p>
2391 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2392 <div class="directive-section"><h2><a name="LimitRequestLine" id="LimitRequestLine">LimitRequestLine</a> <a name="limitrequestline" id="limitrequestline">Directiva</a></h2>
2393 <table class="directive">
2394 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limit the size of the HTTP request line that will be accepted
2395 from the client</td></tr>
2396 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitRequestLine <var>bytes</var></code></td></tr>
2397 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitRequestLine 8190</code></td></tr>
2398 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2399 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2400 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2402 <p>This directive sets the number of <var>bytes</var> that will be
2403 allowed on the HTTP request-line.</p>
2405 <p>The <code class="directive">LimitRequestLine</code> directive allows
2406 the server administrator to reduce or increase the limit on the allowed size
2407 of a client's HTTP request-line. Since the request-line consists of the
2408 HTTP method, URI, and protocol version, the
2409 <code class="directive">LimitRequestLine</code> directive places a
2410 restriction on the length of a request-URI allowed for a request
2411 on the server. A server needs this value to be large enough to
2412 hold any of its resource names, including any information that
2413 might be passed in the query part of a <code>GET</code> request.</p>
2415 <p>This directive gives the server administrator greater
2416 control over abnormal client request behavior, which may be
2417 useful for avoiding some forms of denial-of-service attacks.</p>
2421 <div class="example"><p><code>
2422 LimitRequestLine 4094
2425 <div class="note">Under normal conditions, the value should not be changed from
2428 <div class="warning"><h3>Warning</h3>
2429 <p> When name-based virtual hosting is used, the value for this
2430 directive is taken from the default (first-listed) virtual host for the
2431 <code class="directive">NameVirtualHost</code> the connection was mapped to.</p>
2436 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2437 <div class="directive-section"><h2><a name="LimitXMLRequestBody" id="LimitXMLRequestBody">LimitXMLRequestBody</a> <a name="limitxmlrequestbody" id="limitxmlrequestbody">Directiva</a></h2>
2438 <table class="directive">
2439 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the size of an XML-based request body</td></tr>
2440 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitXMLRequestBody <var>bytes</var></code></td></tr>
2441 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitXMLRequestBody 1000000</code></td></tr>
2442 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
2443 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
2444 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2445 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2447 <p>Limit (in bytes) on maximum size of an XML-based request
2448 body. A value of <code>0</code> will disable any checking.</p>
2452 <div class="example"><p><code>
2453 LimitXMLRequestBody 0
2458 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2459 <div class="directive-section"><h2><a name="Location" id="Location"><Location></a> <a name="location" id="location">Directiva</a></h2>
2460 <table class="directive">
2461 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Applies the enclosed directives only to matching
2463 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><Location
2464 <var>URL-path</var>|<var>URL</var>> ... </Location></code></td></tr>
2465 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2466 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2467 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2469 <p>The <code class="directive"><Location></code> directive
2470 limits the scope of the enclosed directives by URL. It is similar to the
2471 <code class="directive"><a href="#directory"><Directory></a></code>
2472 directive, and starts a subsection which is terminated with a
2473 <code></Location></code> directive. <code class="directive"><Location></code> sections are processed in the
2474 order they appear in the configuration file, after the <code class="directive"><a href="#directory"><Directory></a></code> sections and
2475 <code>.htaccess</code> files are read, and after the <code class="directive"><a href="#files"><Files></a></code> sections.</p>
2477 <p><code class="directive"><Location></code> sections operate
2478 completely outside the filesystem. This has several consequences.
2479 Most importantly, <code class="directive"><Location></code>
2480 directives should not be used to control access to filesystem
2481 locations. Since several different URLs may map to the same
2482 filesystem location, such access controls may by circumvented.</p>
2484 <p>The enclosed directives will be applied to the request if the path component
2485 of the URL meets <em>any</em> of the following criteria:
2488 <li>The specified location matches exactly the path component of the URL.
2490 <li>The specified location, which ends in a forward slash, is a prefix
2491 of the path component of the URL (treated as a context root).
2493 <li>The specified location, with the addition of a trailing slash, is a
2494 prefix of the path component of the URL (also treated as a context root).
2498 In the example below, where no trailing slash is used, requests to
2499 /private1, /private1/ and /private1/file.txt will have the enclosed
2500 directives applied, but /private1other would not.
2502 <div class="example"><p><code>
2503 <Location /private1>
2507 In the example below, where a trailing slash is used, requests to
2508 /private2/ and /private2/file.txt will have the enclosed
2509 directives applied, but /private2 and /private2other would not.
2511 <div class="example"><p><code>
2512 <Location /private2<em>/</em>>
2516 <div class="note"><h3>When to use <code class="directive"><Location></code></h3>
2518 <p>Use <code class="directive"><Location></code> to apply
2519 directives to content that lives outside the filesystem. For
2520 content that lives in the filesystem, use <code class="directive"><a href="#directory"><Directory></a></code> and <code class="directive"><a href="#files"><Files></a></code>. An exception is
2521 <code><Location /></code>, which is an easy way to
2522 apply a configuration to the entire server.</p>
2525 <p>For all origin (non-proxy) requests, the URL to be matched is a
2526 URL-path of the form <code>/path/</code>. <em>No scheme, hostname,
2527 port, or query string may be included.</em> For proxy requests, the
2528 URL to be matched is of the form
2529 <code>scheme://servername/path</code>, and you must include the
2532 <p>The URL may use wildcards. In a wild-card string, <code>?</code> matches
2533 any single character, and <code>*</code> matches any sequences of
2534 characters. Neither wildcard character matches a / in the URL-path.</p>
2536 <p><a class="glossarylink" href="../glossary.html#regex" title="ver glosario">Regular expressions</a>
2537 can also be used, with the addition of the <code>~</code>
2538 character. For example:</p>
2540 <div class="example"><p><code>
2541 <Location ~ "/(extra|special)/data">
2544 <p>would match URLs that contained the substring <code>/extra/data</code>
2545 or <code>/special/data</code>. The directive <code class="directive"><a href="#locationmatch"><LocationMatch></a></code> behaves
2546 identical to the regex version of <code class="directive"><Location></code>, and is preferred, for the
2547 simple reason that <code>~</code> is hard to distinguish from
2548 <code>-</code> in many fonts.</p>
2550 <p>The <code class="directive"><Location></code>
2551 functionality is especially useful when combined with the
2552 <code class="directive"><a href="#sethandler">SetHandler</a></code>
2553 directive. For example, to enable status requests, but allow them
2554 only from browsers at <code>example.com</code>, you might use:</p>
2556 <div class="example"><p><code>
2557 <Location /status><br />
2558 <span class="indent">
2559 SetHandler server-status<br />
2560 Require host example.com<br />
2565 <div class="note"><h3>Note about / (slash)</h3>
2566 <p>The slash character has special meaning depending on where in a
2567 URL it appears. People may be used to its behavior in the filesystem
2568 where multiple adjacent slashes are frequently collapsed to a single
2569 slash (<em>i.e.</em>, <code>/home///foo</code> is the same as
2570 <code>/home/foo</code>). In URL-space this is not necessarily true.
2571 The <code class="directive"><a href="#locationmatch"><LocationMatch></a></code>
2572 directive and the regex version of <code class="directive"><Location></code> require you to explicitly specify multiple
2573 slashes if that is your intention.</p>
2575 <p>For example, <code><LocationMatch ^/abc></code> would match
2576 the request URL <code>/abc</code> but not the request URL <code>
2577 //abc</code>. The (non-regex) <code class="directive"><Location></code> directive behaves similarly when used for
2578 proxy requests. But when (non-regex) <code class="directive"><Location></code> is used for non-proxy requests it will
2579 implicitly match multiple slashes with a single slash. For example,
2580 if you specify <code><Location /abc/def></code> and the
2581 request is to <code>/abc//def</code> then it will match.</p>
2584 <h3>Consulte también</h3>
2586 <li><a href="../sections.html">How <Directory>, <Location>
2587 and <Files> sections work</a> for an explanation of how these
2588 different sections are combined when a request is received.</li>
2589 <li><code class="directive"><a href="#locationmatch">LocationMatch</a></code></li>
2592 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2593 <div class="directive-section"><h2><a name="LocationMatch" id="LocationMatch"><LocationMatch></a> <a name="locationmatch" id="locationmatch">Directiva</a></h2>
2594 <table class="directive">
2595 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Applies the enclosed directives only to regular-expression
2596 matching URLs</td></tr>
2597 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><LocationMatch
2598 <var>regex</var>> ... </LocationMatch></code></td></tr>
2599 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2600 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2601 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2603 <p>The <code class="directive"><LocationMatch></code> directive
2604 limits the scope of the enclosed directives by URL, in an identical manner
2605 to <code class="directive"><a href="#location"><Location></a></code>. However,
2606 it takes a <a class="glossarylink" href="../glossary.html#regex" title="ver glosario">regular expression</a>
2607 as an argument instead of a simple string. For example:</p>
2609 <div class="example"><p><code>
2610 <LocationMatch "/(extra|special)/data">
2613 <p>would match URLs that contained the substring <code>/extra/data</code>
2614 or <code>/special/data</code>.</p>
2616 <h3>Consulte también</h3>
2618 <li><a href="../sections.html">How <Directory>, <Location>
2619 and <Files> sections work</a> for an explanation of how these
2620 different sections are combined when a request is received</li>
2623 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2624 <div class="directive-section"><h2><a name="LogLevel" id="LogLevel">LogLevel</a> <a name="loglevel" id="loglevel">Directiva</a></h2>
2625 <table class="directive">
2626 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Controls the verbosity of the ErrorLog</td></tr>
2627 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LogLevel [<var>module</var>:]<var>level</var>
2628 [<var>module</var>:<var>level</var>] ...
2630 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LogLevel warn</code></td></tr>
2631 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
2632 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2633 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2634 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Per-module and per-directory configuration is available in
2635 Apache HTTP Server 2.3.6 and later</td></tr>
2637 <p><code class="directive">LogLevel</code> adjusts the verbosity of the
2638 messages recorded in the error logs (see <code class="directive"><a href="#errorlog">ErrorLog</a></code> directive). The following
2639 <var>level</var>s are available, in order of decreasing
2642 <table class="bordered">
2645 <th><strong>Level</strong> </th>
2647 <th><strong>Description</strong> </th>
2649 <th><strong>Example</strong> </th>
2653 <td><code>emerg</code> </td>
2655 <td>Emergencies - system is unusable.</td>
2657 <td>"Child cannot open lock file. Exiting"</td>
2661 <td><code>alert</code> </td>
2663 <td>Action must be taken immediately.</td>
2665 <td>"getpwuid: couldn't determine user name from uid"</td>
2669 <td><code>crit</code> </td>
2671 <td>Critical Conditions.</td>
2673 <td>"socket: Failed to get a socket, exiting child"</td>
2677 <td><code>error</code> </td>
2679 <td>Error conditions.</td>
2681 <td>"Premature end of script headers"</td>
2685 <td><code>warn</code> </td>
2687 <td>Warning conditions.</td>
2689 <td>"child process 1234 did not exit, sending another
2694 <td><code>notice</code> </td>
2696 <td>Normal but significant condition.</td>
2698 <td>"httpd: caught SIGBUS, attempting to dump core in
2703 <td><code>info</code> </td>
2705 <td>Informational.</td>
2707 <td>"Server seems busy, (you may need to increase
2708 StartServers, or Min/MaxSpareServers)..."</td>
2712 <td><code>debug</code> </td>
2714 <td>Debug-level messages</td>
2716 <td>"Opening config file ..."</td>
2719 <td><code>trace1</code> </td>
2721 <td>Trace messages</td>
2723 <td>"proxy: FTP: control connection complete"</td>
2726 <td><code>trace2</code> </td>
2728 <td>Trace messages</td>
2730 <td>"proxy: CONNECT: sending the CONNECT request to the remote proxy"</td>
2733 <td><code>trace3</code> </td>
2735 <td>Trace messages</td>
2737 <td>"openssl: Handshake: start"</td>
2740 <td><code>trace4</code> </td>
2742 <td>Trace messages</td>
2744 <td>"read from buffered SSL brigade, mode 0, 17 bytes"</td>
2747 <td><code>trace5</code> </td>
2749 <td>Trace messages</td>
2751 <td>"map lookup FAILED: map=rewritemap key=keyname"</td>
2754 <td><code>trace6</code> </td>
2756 <td>Trace messages</td>
2758 <td>"cache lookup FAILED, forcing new map lookup"</td>
2761 <td><code>trace7</code> </td>
2763 <td>Trace messages, dumping large amounts of data</td>
2765 <td>"| 0000: 02 23 44 30 13 40 ac 34 df 3d bf 9a 19 49 39 15 |"</td>
2768 <td><code>trace8</code> </td>
2770 <td>Trace messages, dumping large amounts of data</td>
2772 <td>"| 0000: 02 23 44 30 13 40 ac 34 df 3d bf 9a 19 49 39 15 |"</td>
2776 <p>When a particular level is specified, messages from all
2777 other levels of higher significance will be reported as well.
2778 <em>E.g.</em>, when <code>LogLevel info</code> is specified,
2779 then messages with log levels of <code>notice</code> and
2780 <code>warn</code> will also be posted.</p>
2782 <p>Using a level of at least <code>crit</code> is
2787 <div class="example"><p><code>
2791 <div class="note"><h3>Note</h3>
2792 <p>When logging to a regular file messages of the level
2793 <code>notice</code> cannot be suppressed and thus are always
2794 logged. However, this doesn't apply when logging is done
2795 using <code>syslog</code>.</p>
2798 <p>Specifying a level without a module name will reset the level
2799 for all modules to that level. Specifying a level with a module
2800 name will set the level for that module only. It is possible to
2801 use the module source file name, the module identifier, or the
2802 module identifier with the trailing <code>_module</code> omitted
2803 as module specification. This means the following three specifications
2806 <div class="example"><p><code>
2807 LogLevel info ssl:warn<br />
2808 LogLevel info mod_ssl.c:warn<br />
2809 LogLevel info ssl_module:warn<br />
2812 <p>It is also possible to change the level per directory:</p>
2814 <div class="example"><p><code>
2816 <Directory /usr/local/apache/htdocs/app><br />
2817 LogLevel debug<br />
2822 Per directory loglevel configuration only affects messages that are
2823 logged after the request has been parsed and that are associated with
2824 the request. Log messages which are associated with the connection or
2825 the server are not affected.
2829 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2830 <div class="directive-section"><h2><a name="LogLevelOverride" id="LogLevelOverride">LogLevelOverride</a> <a name="logleveloverride" id="logleveloverride">Directiva</a></h2>
2831 <table class="directive">
2832 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Override the verbosity of the ErrorLog for certain clients</td></tr>
2833 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LogLevel <var>ipaddress</var>[/<var>prefixlen</var>]
2834 [<var>module</var>:]<var>level</var> [<var>module</var>:<var>level</var>] ...
2836 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>unset</code></td></tr>
2837 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2838 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2839 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2840 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.5.0 and later</td></tr>
2841 </table><p>The documentation for this directive has
2842 not been translated yet. Please have a look at the English
2843 version.</p><h3>Consulte también</h3>
2845 <li><code class="directive"><a href="#loglevel">LogLevel</a></code></li>
2848 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2849 <div class="directive-section"><h2><a name="MaxKeepAliveRequests" id="MaxKeepAliveRequests">MaxKeepAliveRequests</a> <a name="maxkeepaliverequests" id="maxkeepaliverequests">Directiva</a></h2>
2850 <table class="directive">
2851 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Number of requests allowed on a persistent
2852 connection</td></tr>
2853 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>MaxKeepAliveRequests <var>number</var></code></td></tr>
2854 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>MaxKeepAliveRequests 100</code></td></tr>
2855 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2856 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2857 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2859 <p>The <code class="directive">MaxKeepAliveRequests</code> directive
2860 limits the number of requests allowed per connection when
2861 <code class="directive"><a href="#keepalive">KeepAlive</a></code> is on. If it is
2862 set to <code>0</code>, unlimited requests will be allowed. We
2863 recommend that this setting be kept to a high value for maximum
2864 server performance.</p>
2868 <div class="example"><p><code>
2869 MaxKeepAliveRequests 500
2873 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2874 <div class="directive-section"><h2><a name="MaxRangeOverlaps" id="MaxRangeOverlaps">MaxRangeOverlaps</a> <a name="maxrangeoverlaps" id="maxrangeoverlaps">Directiva</a></h2>
2875 <table class="directive">
2876 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Number of overlapping ranges (eg: <code>100-200,150-300</code>) allowed before returning the complete
2878 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>MaxRangeOverlaps default | unlimited | none | <var>number-of-ranges</var></code></td></tr>
2879 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>MaxRangeOverlaps 20</code></td></tr>
2880 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
2881 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2882 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2883 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.3.15 and later</td></tr>
2884 </table><p>The documentation for this directive has
2885 not been translated yet. Please have a look at the English
2887 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2888 <div class="directive-section"><h2><a name="MaxRangeReversals" id="MaxRangeReversals">MaxRangeReversals</a> <a name="maxrangereversals" id="maxrangereversals">Directiva</a></h2>
2889 <table class="directive">
2890 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Number of range reversals (eg: <code>100-200,50-70</code>) allowed before returning the complete
2892 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>MaxRangeReversals default | unlimited | none | <var>number-of-ranges</var></code></td></tr>
2893 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>MaxRangeReversals 20</code></td></tr>
2894 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
2895 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2896 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2897 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.3.15 and later</td></tr>
2898 </table><p>The documentation for this directive has
2899 not been translated yet. Please have a look at the English
2901 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2902 <div class="directive-section"><h2><a name="MaxRanges" id="MaxRanges">MaxRanges</a> <a name="maxranges" id="maxranges">Directiva</a></h2>
2903 <table class="directive">
2904 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Number of ranges allowed before returning the complete
2906 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>MaxRanges default | unlimited | none | <var>number-of-ranges</var></code></td></tr>
2907 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>MaxRanges 200</code></td></tr>
2908 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
2909 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2910 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2911 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.3.15 and later</td></tr>
2912 </table><p>The documentation for this directive has
2913 not been translated yet. Please have a look at the English
2915 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2916 <div class="directive-section"><h2><a name="MergeTrailers" id="MergeTrailers">MergeTrailers</a> <a name="mergetrailers" id="mergetrailers">Directiva</a></h2>
2917 <table class="directive">
2918 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determines whether trailers are merged into headers</td></tr>
2919 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>MergeTrailers [on|off]</code></td></tr>
2920 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>MergeTrailers off</code></td></tr>
2921 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2922 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2923 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2924 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>2.4.11 and later</td></tr>
2925 </table><p>The documentation for this directive has
2926 not been translated yet. Please have a look at the English
2928 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2929 <div class="directive-section"><h2><a name="Mutex" id="Mutex">Mutex</a> <a name="mutex" id="mutex">Directiva</a></h2>
2930 <table class="directive">
2931 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures mutex mechanism and lock file directory for all
2932 or specified mutexes</td></tr>
2933 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Mutex <var>mechanism</var> [default|<var>mutex-name</var>] ... [OmitPID]</code></td></tr>
2934 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Mutex default</code></td></tr>
2935 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
2936 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2937 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2938 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.3.4 and later</td></tr>
2940 <p>The <code class="directive">Mutex</code> directive sets the mechanism,
2941 and optionally the lock file location, that httpd and modules use
2942 to serialize access to resources. Specify <code>default</code> as
2943 the first argument to change the settings for all mutexes; specify
2944 a mutex name (see table below) as the first argument to override
2945 defaults only for that mutex.</p>
2947 <p>The <code class="directive">Mutex</code> directive is typically used in
2948 the following exceptional situations:</p>
2951 <li>change the mutex mechanism when the default mechanism selected
2952 by <a class="glossarylink" href="../glossary.html#apr" title="ver glosario">APR</a> has a functional or performance
2955 <li>change the directory used by file-based mutexes when the
2956 default directory does not support locking</li>
2959 <div class="note"><h3>Supported modules</h3>
2960 <p>This directive only configures mutexes which have been registered
2961 with the core server using the <code>ap_mutex_register()</code> API.
2962 All modules bundled with httpd support the <code class="directive">Mutex</code>
2963 directive, but third-party modules may not. Consult the documentation
2964 of the third-party module, which must indicate the mutex name(s) which
2965 can be configured if this directive is supported.</p>
2968 <p>The following mutex <em>mechanisms</em> are available:</p>
2970 <li><code>default | yes</code>
2971 <p>This selects the default locking implementation, as determined by
2972 <a class="glossarylink" href="../glossary.html#apr" title="ver glosario">APR</a>. The default locking implementation can
2973 be displayed by running <code class="program"><a href="../programs/httpd.html">httpd</a></code> with the
2974 <code>-V</code> option.</p></li>
2976 <li><code>none | no</code>
2977 <p>This effectively disables the mutex, and is only allowed for a
2978 mutex if the module indicates that it is a valid choice. Consult the
2979 module documentation for more information.</p></li>
2981 <li><code>posixsem</code>
2982 <p>This is a mutex variant based on a Posix semaphore.</p>
2984 <div class="warning"><h3>Warning</h3>
2985 <p>The semaphore ownership is not recovered if a thread in the process
2986 holding the mutex segfaults, resulting in a hang of the web server.</p>
2990 <li><code>sysvsem</code>
2991 <p>This is a mutex variant based on a SystemV IPC semaphore.</p>
2993 <div class="warning"><h3>Warning</h3>
2994 <p>It is possible to "leak" SysV semaphores if processes crash
2995 before the semaphore is removed.</p>
2998 <div class="warning"><h3>Security</h3>
2999 <p>The semaphore API allows for a denial of service attack by any
3000 CGIs running under the same uid as the webserver (<em>i.e.</em>,
3001 all CGIs, unless you use something like <code class="program"><a href="../programs/suexec.html">suexec</a></code>
3002 or <code>cgiwrapper</code>).</p>
3006 <li><code>sem</code>
3007 <p>This selects the "best" available semaphore implementation, choosing
3008 between Posix and SystemV IPC semaphores, in that order.</p></li>
3010 <li><code>pthread</code>
3011 <p>This is a mutex variant based on cross-process Posix thread
3014 <div class="warning"><h3>Warning</h3>
3015 <p>On most systems, if a child process terminates abnormally while
3016 holding a mutex that uses this implementation, the server will deadlock
3017 and stop responding to requests. When this occurs, the server will
3018 require a manual restart to recover.</p>
3019 <p>Solaris is a notable exception as it provides a mechanism which
3020 usually allows the mutex to be recovered after a child process
3021 terminates abnormally while holding a mutex.</p>
3022 <p>If your system implements the
3023 <code>pthread_mutexattr_setrobust_np()</code> function, you may be able
3024 to use the <code>pthread</code> option safely.</p>
3028 <li><code>fcntl:/path/to/mutex</code>
3029 <p>This is a mutex variant where a physical (lock-)file and the
3030 <code>fcntl()</code> function are used as the mutex.</p>
3032 <div class="warning"><h3>Warning</h3>
3033 <p>When multiple mutexes based on this mechanism are used within
3034 multi-threaded, multi-process environments, deadlock errors (EDEADLK)
3035 can be reported for valid mutex operations if <code>fcntl()</code>
3036 is not thread-aware, such as on Solaris.</p>
3040 <li><code>flock:/path/to/mutex</code>
3041 <p>This is similar to the <code>fcntl:/path/to/mutex</code> method
3042 with the exception that the <code>flock()</code> function is used to
3043 provide file locking.</p></li>
3045 <li><code>file:/path/to/mutex</code>
3046 <p>This selects the "best" available file locking implementation,
3047 choosing between <code>fcntl</code> and <code>flock</code>, in that
3051 <p>Most mechanisms are only available on selected platforms, where the
3052 underlying platform and <a class="glossarylink" href="../glossary.html#apr" title="ver glosario">APR</a> support it. Mechanisms
3053 which aren't available on all platforms are <em>posixsem</em>,
3054 <em>sysvsem</em>, <em>sem</em>, <em>pthread</em>, <em>fcntl</em>,
3055 <em>flock</em>, and <em>file</em>.</p>
3057 <p>With the file-based mechanisms <em>fcntl</em> and <em>flock</em>,
3058 the path, if provided, is a directory where the lock file will be created.
3059 The default directory is httpd's run-time file directory relative to
3060 <code class="directive"><a href="#serverroot">ServerRoot</a></code>. Always use a local disk
3061 filesystem for <code>/path/to/mutex</code> and never a directory residing
3062 on a NFS- or AFS-filesystem. The basename of the file will be the mutex
3063 type, an optional instance string provided by the module, and unless the
3064 <code>OmitPID</code> keyword is specified, the process id of the httpd
3065 parent process will be appended to to make the file name unique, avoiding
3066 conflicts when multiple httpd instances share a lock file directory. For
3067 example, if the mutex name is <code>mpm-accept</code> and the lock file
3068 directory is <code>/var/httpd/locks</code>, the lock file name for the
3069 httpd instance with parent process id 12345 would be
3070 <code>/var/httpd/locks/mpm-accept.12345</code>.</p>
3072 <div class="warning"><h3>Security</h3>
3073 <p>It is best to <em>avoid</em> putting mutex files in a world-writable
3074 directory such as <code>/var/tmp</code> because someone could create
3075 a denial of service attack and prevent the server from starting by
3076 creating a lockfile with the same name as the one the server will try
3080 <p>The following table documents the names of mutexes used by httpd
3081 and bundled modules.</p>
3083 <table class="bordered"><tr class="header">
3086 <th>Protected resource</th>
3089 <td><code>mpm-accept</code></td>
3090 <td><code class="module"><a href="../mod/prefork.html">prefork</a></code> and <code class="module"><a href="../mod/worker.html">worker</a></code> MPMs</td>
3091 <td>incoming connections, to avoid the thundering herd problem;
3092 for more information, refer to the
3093 <a href="../misc/perf-tuning.html">performance tuning</a>
3097 <td><code>authdigest-client</code></td>
3098 <td><code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code></td>
3099 <td>client list in shared memory</td>
3102 <td><code>authdigest-opaque</code></td>
3103 <td><code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code></td>
3104 <td>counter in shared memory</td>
3107 <td><code>ldap-cache</code></td>
3108 <td><code class="module"><a href="../mod/mod_ldap.html">mod_ldap</a></code></td>
3109 <td>LDAP result cache</td>
3112 <td><code>rewrite-map</code></td>
3113 <td><code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code></td>
3114 <td>communication with external mapping programs, to avoid
3115 intermixed I/O from multiple requests</td>
3118 <td><code>ssl-cache</code></td>
3119 <td><code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code></td>
3120 <td>SSL session cache</td>
3123 <td><code>ssl-stapling</code></td>
3124 <td><code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code></td>
3125 <td>OCSP stapling response cache</td>
3128 <td><code>watchdog-callback</code></td>
3129 <td><code class="module"><a href="../mod/mod_watchdog.html">mod_watchdog</a></code></td>
3130 <td>callback function of a particular client module</td>
3134 <p>The <code>OmitPID</code> keyword suppresses the addition of the httpd
3135 parent process id from the lock file name.</p>
3137 <p>In the following example, the mutex mechanism for the MPM accept
3138 mutex will be changed from the compiled-in default to <code>fcntl</code>,
3139 with the associated lock file created in directory
3140 <code>/var/httpd/locks</code>. The mutex mechanism for all other mutexes
3141 will be changed from the compiled-in default to <code>sysvsem</code>.</p>
3143 <div class="example"><p><code>
3144 Mutex default sysvsem<br />
3145 Mutex mpm-accept fcntl:/var/httpd/locks
3149 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3150 <div class="directive-section"><h2><a name="NameVirtualHost" id="NameVirtualHost">NameVirtualHost</a> <a name="namevirtualhost" id="namevirtualhost">Directiva</a></h2>
3151 <table class="directive">
3152 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Designates an IP address for name-virtual
3154 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>NameVirtualHost <var>addr</var>[:<var>port</var>]</code></td></tr>
3155 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
3156 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3157 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3160 <p>A single <code class="directive">NameVirtualHost</code> directive
3161 identifies a set of identical virtual hosts on which the server will
3162 further select from on the basis of the <em>hostname</em>
3163 requested by the client. The <code class="directive">NameVirtualHost</code>
3164 directive is a required directive if you want to configure
3165 <a href="../vhosts/">name-based virtual hosts</a>.</p>
3167 <p>This directive, and the corresponding <code class="directive">VirtualHost</code>,
3168 <em>must</em> be qualified with a port number if the server supports both HTTP
3169 and HTTPS connections.</p>
3171 <p>Although <var>addr</var> can be a hostname, it is recommended
3172 that you always use an IP address or a wildcard. A wildcard
3173 NameVirtualHost matches only virtualhosts that also have a literal wildcard
3174 as their argument.</p>
3176 <p>In cases where a firewall or other proxy receives the requests and
3177 forwards them on a different IP address to the server, you must specify the
3178 IP address of the physical interface on the machine which will be
3179 servicing the requests. </p>
3181 <p> In the example below, requests received on interface 192.0.2.1 and port 80
3182 will only select among the first two virtual hosts. Requests received on
3183 port 80 on any other interface will only select among the third and fourth
3184 virtual hosts. In the common case where the interface isn't important
3185 to the mapping, only the "*:80" NameVirtualHost and VirtualHost directives
3188 <div class="example"><p><code>
3189 NameVirtualHost 192.0.2.1:80<br />
3190 NameVirtualHost *:80<br /><br />
3192 <VirtualHost 192.0.2.1:80><br />
3193 ServerName namebased-a.example.com<br />
3194 </VirtualHost><br />
3196 <VirtualHost 192.0.2.1:80><br />
3197 Servername namebased-b.example.com<br />
3198 </VirtualHost><br />
3200 <VirtualHost *:80><br />
3201 ServerName namebased-c.example.com <br />
3202 </VirtualHost><br />
3204 <VirtualHost *:80><br />
3205 ServerName namebased-d.example.com <br />
3206 </VirtualHost><br />
3211 <p>If no matching virtual host is found, then the first listed
3212 virtual host that matches the IP address and port will be used.</p>
3215 <p>IPv6 addresses must be enclosed in square brackets, as shown
3216 in the following example:</p>
3218 <div class="example"><p><code>
3219 NameVirtualHost [2001:db8::a00:20ff:fea7:ccea]:8080
3222 <div class="note"><h3>Argument to <code class="directive"><VirtualHost></code>
3224 <p>Note that the argument to the <code class="directive"><VirtualHost></code> directive must
3225 exactly match the argument to the <code class="directive">NameVirtualHost</code> directive.</p>
3227 <div class="example"><p><code>
3228 NameVirtualHost 192.0.2.2:80<br />
3229 <VirtualHost 192.0.2.2:80><br />
3231 </VirtualHost><br />
3235 <h3>Consulte también</h3>
3237 <li><a href="../vhosts/">Virtual Hosts
3238 documentation</a></li>
3241 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3242 <div class="directive-section"><h2><a name="Options" id="Options">Options</a> <a name="options" id="options">Directiva</a></h2>
3243 <table class="directive">
3244 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures what features are available in a particular
3246 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Options
3247 [+|-]<var>option</var> [[+|-]<var>option</var>] ...</code></td></tr>
3248 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Options All</code></td></tr>
3249 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3250 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>Options</td></tr>
3251 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3252 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3254 <p>The <code class="directive">Options</code> directive controls which
3255 server features are available in a particular directory.</p>
3257 <p><var>option</var> can be set to <code>None</code>, in which
3258 case none of the extra features are enabled, or one or more of
3262 <dt><code>All</code></dt>
3264 <dd>All options except for <code>MultiViews</code>. This is the default
3267 <dt><code>ExecCGI</code></dt>
3270 Execution of CGI scripts using <code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code>
3273 <dt><code>FollowSymLinks</code></dt>
3277 The server will follow symbolic links in this directory.
3279 <p>Even though the server follows the symlink it does <em>not</em>
3280 change the pathname used to match against <code class="directive"><a href="#directory"><Directory></a></code> sections.</p>
3281 <p>Note also, that this option <strong>gets ignored</strong> if set
3282 inside a <code class="directive"><a href="#location"><Location></a></code>
3284 <p>Omitting this option should not be considered a security restriction,
3285 since symlink testing is subject to race conditions that make it
3289 <dt><code>Includes</code></dt>
3292 Server-side includes provided by <code class="module"><a href="../mod/mod_include.html">mod_include</a></code>
3295 <dt><code>IncludesNOEXEC</code></dt>
3299 Server-side includes are permitted, but the <code>#exec
3300 cmd</code> and <code>#exec cgi</code> are disabled. It is still
3301 possible to <code>#include virtual</code> CGI scripts from
3302 <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code>ed
3305 <dt><code>Indexes</code></dt>
3308 If a URL which maps to a directory is requested, and there
3309 is no <code class="directive"><a href="../mod/mod_dir.html#directoryindex">DirectoryIndex</a></code>
3310 (<em>e.g.</em>, <code>index.html</code>) in that directory, then
3311 <code class="module"><a href="../mod/mod_autoindex.html">mod_autoindex</a></code> will return a formatted listing
3312 of the directory.</dd>
3314 <dt><code>MultiViews</code></dt>
3317 <a href="../content-negotiation.html">Content negotiated</a>
3318 "MultiViews" are allowed using
3319 <code class="module"><a href="../mod/mod_negotiation.html">mod_negotiation</a></code>.
3320 <div class="note"><h3>Note</h3> <p>This option gets ignored if set
3321 anywhere other than <code class="directive"><a href="#directory"><Directory></a></code>, as <code class="module"><a href="../mod/mod_negotiation.html">mod_negotiation</a></code>
3322 needs real resources to compare against and evaluate from.</p></div>
3325 <dt><code>SymLinksIfOwnerMatch</code></dt>
3327 <dd>The server will only follow symbolic links for which the
3328 target file or directory is owned by the same user id as the
3331 <div class="note"><h3>Note</h3> <p>This option gets ignored if
3332 set inside a <code class="directive"><a href="#location"><Location></a></code> section.</p>
3333 <p>This option should not be considered a security restriction,
3334 since symlink testing is subject to race conditions that make it
3335 circumventable.</p></div>
3339 <p>Normally, if multiple <code class="directive">Options</code> could
3340 apply to a directory, then the most specific one is used and
3341 others are ignored; the options are not merged. (See <a href="../sections.html#mergin">how sections are merged</a>.)
3342 However if <em>all</em> the options on the
3343 <code class="directive">Options</code> directive are preceded by a
3344 <code>+</code> or <code>-</code> symbol, the options are
3345 merged. Any options preceded by a <code>+</code> are added to the
3346 options currently in force, and any options preceded by a
3347 <code>-</code> are removed from the options currently in
3350 <div class="warning"><h3>Warning</h3>
3351 <p>Mixing <code class="directive">Options</code> with a <code>+</code> or
3352 <code>-</code> with those without is not valid syntax, and is likely
3353 to cause unexpected results.</p>
3356 <p>For example, without any <code>+</code> and <code>-</code> symbols:</p>
3358 <div class="example"><p><code>
3359 <Directory /web/docs><br />
3360 <span class="indent">
3361 Options Indexes FollowSymLinks<br />
3363 </Directory><br />
3365 <Directory /web/docs/spec><br />
3366 <span class="indent">
3367 Options Includes<br />
3372 <p>then only <code>Includes</code> will be set for the
3373 <code>/web/docs/spec</code> directory. However if the second
3374 <code class="directive">Options</code> directive uses the <code>+</code> and
3375 <code>-</code> symbols:</p>
3377 <div class="example"><p><code>
3378 <Directory /web/docs><br />
3379 <span class="indent">
3380 Options Indexes FollowSymLinks<br />
3382 </Directory><br />
3384 <Directory /web/docs/spec><br />
3385 <span class="indent">
3386 Options +Includes -Indexes<br />
3391 <p>then the options <code>FollowSymLinks</code> and
3392 <code>Includes</code> are set for the <code>/web/docs/spec</code>
3395 <div class="note"><h3>Note</h3>
3396 <p>Using <code>-IncludesNOEXEC</code> or
3397 <code>-Includes</code> disables server-side includes completely
3398 regardless of the previous setting.</p>
3401 <p>The default in the absence of any other settings is
3402 <code>All</code>.</p>
3405 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3406 <div class="directive-section"><h2><a name="Protocol" id="Protocol">Protocol</a> <a name="protocol" id="protocol">Directiva</a></h2>
3407 <table class="directive">
3408 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Protocol for a listening socket</td></tr>
3409 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Protocol <var>protocol</var></code></td></tr>
3410 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
3411 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3412 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3413 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache 2.1.5 and later.
3414 On Windows from Apache 2.3.3 and later.</td></tr>
3416 <p>This directive specifies the protocol used for a specific listening socket.
3417 The protocol is used to determine which module should handle a request, and
3418 to apply protocol specific optimizations with the <code class="directive">AcceptFilter</code>
3421 <p>You only need to set the protocol if you are running on non-standard ports, otherwise <code>http</code> is assumed for port 80 and <code>https</code> for port 443.</p>
3423 <p>For example, if you are running <code>https</code> on a non-standard port, specify the protocol explicitly:</p>
3425 <div class="example"><p><code>
3429 <p>You can also specify the protocol using the <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> directive.</p>
3431 <h3>Consulte también</h3>
3433 <li><code class="directive">AcceptFilter</code></li>
3434 <li><code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code></li>
3437 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3438 <div class="directive-section"><h2><a name="Protocols" id="Protocols">Protocols</a> <a name="protocols" id="protocols">Directiva</a></h2>
3439 <table class="directive">
3440 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Protocols available for a server/virtual host</td></tr>
3441 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Protocols <var>protocol</var> ...</code></td></tr>
3442 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Protocols http/1.1</code></td></tr>
3443 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
3444 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3445 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3446 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Only available from Apache 2.4.17 and later.</td></tr>
3447 </table><p>The documentation for this directive has
3448 not been translated yet. Please have a look at the English
3449 version.</p><h3>Consulte también</h3>
3451 <li><code class="directive"><a href="#protocolshonororder">ProtocolsHonorOrder</a></code></li>
3454 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3455 <div class="directive-section"><h2><a name="ProtocolsHonorOrder" id="ProtocolsHonorOrder">ProtocolsHonorOrder</a> <a name="protocolshonororder" id="protocolshonororder">Directiva</a></h2>
3456 <table class="directive">
3457 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determines if order of Protocols determines precedence during negotiation</td></tr>
3458 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ProtocolsHonorOrder On|Off</code></td></tr>
3459 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ProtocolsHonorOrder On</code></td></tr>
3460 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
3461 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3462 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3463 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Only available from Apache 2.4.17 and later.</td></tr>
3464 </table><p>The documentation for this directive has
3465 not been translated yet. Please have a look at the English
3466 version.</p><h3>Consulte también</h3>
3468 <li><code class="directive"><a href="#protocols">Protocols</a></code></li>
3471 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3472 <div class="directive-section"><h2><a name="QualifyRedirectURL" id="QualifyRedirectURL">QualifyRedirectURL</a> <a name="qualifyredirecturl" id="qualifyredirecturl">Directiva</a></h2>
3473 <table class="directive">
3474 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Controls whether the REDIRECT_URL environment variable is
3475 fully qualified</td></tr>
3476 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>QualifyRedirectURL ON|OFF</code></td></tr>
3477 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>QualifyRedirectURL OFF</code></td></tr>
3478 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
3479 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
3480 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3481 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3482 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Directive supported in 2.4.18 and later. 2.4.17 acted
3483 as if 'QualifyRedirectURL ON' was configured.</td></tr>
3484 </table><p>The documentation for this directive has
3485 not been translated yet. Please have a look at the English
3487 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3488 <div class="directive-section"><h2><a name="RegisterHttpMethod" id="RegisterHttpMethod">RegisterHttpMethod</a> <a name="registerhttpmethod" id="registerhttpmethod">Directiva</a></h2>
3489 <table class="directive">
3490 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Register non-standard HTTP methods</td></tr>
3491 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>RegisterHttpMethod <var>method</var> [<var>method</var> [...]]</code></td></tr>
3492 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
3493 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3494 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3495 </table><p>The documentation for this directive has
3496 not been translated yet. Please have a look at the English
3498 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3499 <div class="directive-section"><h2><a name="RLimitCPU" id="RLimitCPU">RLimitCPU</a> <a name="rlimitcpu" id="rlimitcpu">Directiva</a></h2>
3500 <table class="directive">
3501 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the CPU consumption of processes launched
3502 by Apache httpd children</td></tr>
3503 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>RLimitCPU <var>seconds</var>|max [<var>seconds</var>|max]</code></td></tr>
3504 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Unset; uses operating system defaults</code></td></tr>
3505 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3506 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
3507 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3508 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3510 <p>Takes 1 or 2 parameters. The first parameter sets the soft
3511 resource limit for all processes and the second parameter sets
3512 the maximum resource limit. Either parameter can be a number,
3513 or <code>max</code> to indicate to the server that the limit should
3514 be set to the maximum allowed by the operating system
3515 configuration. Raising the maximum resource limit requires that
3516 the server is running as <code>root</code>, or in the initial startup
3519 <p>This applies to processes forked off from Apache httpd children
3520 servicing requests, not the Apache httpd children themselves. This
3521 includes CGI scripts and SSI exec commands, but not any
3522 processes forked off from the Apache httpd parent such as piped
3525 <p>CPU resource limits are expressed in seconds per
3528 <h3>Consulte también</h3>
3530 <li><code class="directive"><a href="#rlimitmem">RLimitMEM</a></code></li>
3531 <li><code class="directive"><a href="#rlimitnproc">RLimitNPROC</a></code></li>
3534 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3535 <div class="directive-section"><h2><a name="RLimitMEM" id="RLimitMEM">RLimitMEM</a> <a name="rlimitmem" id="rlimitmem">Directiva</a></h2>
3536 <table class="directive">
3537 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the memory consumption of processes launched
3538 by Apache httpd children</td></tr>
3539 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>RLimitMEM <var>bytes</var>|max [<var>bytes</var>|max]</code></td></tr>
3540 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Unset; uses operating system defaults</code></td></tr>
3541 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3542 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
3543 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3544 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3546 <p>Takes 1 or 2 parameters. The first parameter sets the soft
3547 resource limit for all processes and the second parameter sets
3548 the maximum resource limit. Either parameter can be a number,
3549 or <code>max</code> to indicate to the server that the limit should
3550 be set to the maximum allowed by the operating system
3551 configuration. Raising the maximum resource limit requires that
3552 the server is running as <code>root</code>, or in the initial startup
3555 <p>This applies to processes forked off from Apache httpd children
3556 servicing requests, not the Apache httpd children themselves. This
3557 includes CGI scripts and SSI exec commands, but not any
3558 processes forked off from the Apache httpd parent such as piped
3561 <p>Memory resource limits are expressed in bytes per
3564 <h3>Consulte también</h3>
3566 <li><code class="directive"><a href="#rlimitcpu">RLimitCPU</a></code></li>
3567 <li><code class="directive"><a href="#rlimitnproc">RLimitNPROC</a></code></li>
3570 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3571 <div class="directive-section"><h2><a name="RLimitNPROC" id="RLimitNPROC">RLimitNPROC</a> <a name="rlimitnproc" id="rlimitnproc">Directiva</a></h2>
3572 <table class="directive">
3573 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the number of processes that can be launched by
3574 processes launched by Apache httpd children</td></tr>
3575 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>RLimitNPROC <var>number</var>|max [<var>number</var>|max]</code></td></tr>
3576 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Unset; uses operating system defaults</code></td></tr>
3577 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3578 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
3579 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3580 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3582 <p>Takes 1 or 2 parameters. The first parameter sets the soft
3583 resource limit for all processes and the second parameter sets
3584 the maximum resource limit. Either parameter can be a number,
3585 or <code>max</code> to indicate to the server that the limit
3586 should be set to the maximum allowed by the operating system
3587 configuration. Raising the maximum resource limit requires that
3588 the server is running as <code>root</code>, or in the initial startup
3591 <p>This applies to processes forked off from Apache httpd children
3592 servicing requests, not the Apache httpd children themselves. This
3593 includes CGI scripts and SSI exec commands, but not any
3594 processes forked off from the Apache httpd parent such as piped
3597 <p>Process limits control the number of processes per user.</p>
3599 <div class="note"><h3>Note</h3>
3600 <p>If CGI processes are <strong>not</strong> running
3601 under user ids other than the web server user id, this directive
3602 will limit the number of processes that the server itself can
3603 create. Evidence of this situation will be indicated by
3604 <strong><code>cannot fork</code></strong> messages in the
3605 <code>error_log</code>.</p>
3608 <h3>Consulte también</h3>
3610 <li><code class="directive"><a href="#rlimitmem">RLimitMEM</a></code></li>
3611 <li><code class="directive"><a href="#rlimitcpu">RLimitCPU</a></code></li>
3614 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3615 <div class="directive-section"><h2><a name="ScriptInterpreterSource" id="ScriptInterpreterSource">ScriptInterpreterSource</a> <a name="scriptinterpretersource" id="scriptinterpretersource">Directiva</a></h2>
3616 <table class="directive">
3617 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Technique for locating the interpreter for CGI
3619 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ScriptInterpreterSource Registry|Registry-Strict|Script</code></td></tr>
3620 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ScriptInterpreterSource Script</code></td></tr>
3621 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3622 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
3623 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3624 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3625 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Win32 only;
3626 option <code>Registry-Strict</code> is available in Apache HTTP Server 2.0 and
3629 <p>This directive is used to control how Apache httpd finds the
3630 interpreter used to run CGI scripts. The default setting is
3631 <code>Script</code>. This causes Apache httpd to use the interpreter pointed to
3632 by the shebang line (first line, starting with <code>#!</code>) in the
3633 script. On Win32 systems this line usually looks like:</p>
3635 <div class="example"><p><code>
3636 #!C:/Perl/bin/perl.exe
3639 <p>or, if <code>perl</code> is in the <code>PATH</code>, simply:</p>
3641 <div class="example"><p><code>
3645 <p>Setting <code>ScriptInterpreterSource Registry</code> will
3646 cause the Windows Registry tree <code>HKEY_CLASSES_ROOT</code> to be
3647 searched using the script file extension (e.g., <code>.pl</code>) as a
3648 search key. The command defined by the registry subkey
3649 <code>Shell\ExecCGI\Command</code> or, if it does not exist, by the subkey
3650 <code>Shell\Open\Command</code> is used to open the script file. If the
3651 registry keys cannot be found, Apache httpd falls back to the behavior of the
3652 <code>Script</code> option.</p>
3654 <div class="warning"><h3>Security</h3>
3655 <p>Be careful when using <code>ScriptInterpreterSource
3656 Registry</code> with <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code>'ed directories, because
3657 Apache httpd will try to execute <strong>every</strong> file within this
3658 directory. The <code>Registry</code> setting may cause undesired
3659 program calls on files which are typically not executed. For
3660 example, the default open command on <code>.htm</code> files on
3661 most Windows systems will execute Microsoft Internet Explorer, so
3662 any HTTP request for an <code>.htm</code> file existing within the
3663 script directory would start the browser in the background on the
3664 server. This is a good way to crash your system within a minute or
3668 <p>The option <code>Registry-Strict</code> which is new in Apache HTTP Server
3669 2.0 does the same thing as <code>Registry</code> but uses only the
3670 subkey <code>Shell\ExecCGI\Command</code>. The
3671 <code>ExecCGI</code> key is not a common one. It must be
3672 configured manually in the windows registry and hence prevents
3673 accidental program calls on your system.</p>
3676 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3677 <div class="directive-section"><h2><a name="SeeRequestTail" id="SeeRequestTail">SeeRequestTail</a> <a name="seerequesttail" id="seerequesttail">Directiva</a></h2>
3678 <table class="directive">
3679 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determine if mod_status displays the first 63 characters
3680 of a request or the last 63, assuming the request itself is greater than
3682 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>SeeRequestTail On|Off</code></td></tr>
3683 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>SeeRequestTail Off</code></td></tr>
3684 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
3685 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3686 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3687 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache httpd 2.2.7 and later.</td></tr>
3689 <p>mod_status with <code>ExtendedStatus On</code>
3690 displays the actual request being handled.
3691 For historical purposes, only 63 characters of the request
3692 are actually stored for display purposes. This directive
3693 controls whether the 1st 63 characters are stored (the previous
3694 behavior and the default) or if the last 63 characters are. This
3695 is only applicable, of course, if the length of the request is
3696 64 characters or greater.</p>
3698 <p>If Apache httpd is handling <code>GET /disk1/storage/apache/htdocs/images/imagestore1/food/apples.jpg HTTP/1.1</code> mod_status displays as follows:
3701 <table class="bordered">
3703 <th>Off (default)</th>
3704 <td>GET /disk1/storage/apache/htdocs/images/imagestore1/food/apples</td>
3708 <td>orage/apache/htdocs/images/imagestore1/food/apples.jpg HTTP/1.1</td>
3714 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3715 <div class="directive-section"><h2><a name="ServerAdmin" id="ServerAdmin">ServerAdmin</a> <a name="serveradmin" id="serveradmin">Directiva</a></h2>
3716 <table class="directive">
3717 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Email address that the server includes in error
3718 messages sent to the client</td></tr>
3719 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ServerAdmin <var>email-address</var>|<var>URL</var></code></td></tr>
3720 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
3721 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3722 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3724 <p>The <code class="directive">ServerAdmin</code> sets the contact address
3725 that the server includes in any error messages it returns to the
3726 client. If the <code>httpd</code> doesn't recognize the supplied argument
3728 assumes, that it's an <var>email-address</var> and prepends it with
3729 <code>mailto:</code> in hyperlink targets. However, it's recommended to
3730 actually use an email address, since there are a lot of CGI scripts that
3731 make that assumption. If you want to use an URL, it should point to another
3732 server under your control. Otherwise users may not be able to contact you in
3735 <p>It may be worth setting up a dedicated address for this, e.g.</p>
3737 <div class="example"><p><code>
3738 ServerAdmin www-admin@foo.example.com
3740 <p>as users do not always mention that they are talking about the
3744 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3745 <div class="directive-section"><h2><a name="ServerAlias" id="ServerAlias">ServerAlias</a> <a name="serveralias" id="serveralias">Directiva</a></h2>
3746 <table class="directive">
3747 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Alternate names for a host used when matching requests
3748 to name-virtual hosts</td></tr>
3749 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ServerAlias <var>hostname</var> [<var>hostname</var>] ...</code></td></tr>
3750 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>virtual host</td></tr>
3751 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3752 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3754 <p>The <code class="directive">ServerAlias</code> directive sets the
3755 alternate names for a host, for use with <a href="../vhosts/name-based.html">name-based virtual hosts</a>. The
3756 <code class="directive">ServerAlias</code> may include wildcards, if appropriate.</p>
3758 <div class="example"><p><code>
3759 <VirtualHost *:80><br />
3760 ServerName server.domain.com<br />
3761 ServerAlias server server2.domain.com server2<br />
3762 ServerAlias *.example.com<br />
3763 UseCanonicalName Off<br />
3765 </VirtualHost>
3768 <h3>Consulte también</h3>
3770 <li><code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code></li>
3771 <li><a href="../vhosts/">Apache HTTP Server Virtual Host documentation</a></li>
3774 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3775 <div class="directive-section"><h2><a name="ServerName" id="ServerName">ServerName</a> <a name="servername" id="servername">Directiva</a></h2>
3776 <table class="directive">
3777 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Hostname and port that the server uses to identify
3779 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ServerName [<var>scheme</var>://]<var>fully-qualified-domain-name</var>[:<var>port</var>]</code></td></tr>
3780 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
3781 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3782 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3784 <p>The <code class="directive">ServerName</code> directive sets the
3785 request scheme, hostname and
3786 port that the server uses to identify itself. This is used when
3787 creating redirection URLs.</p>
3789 <p>Additionally, <code class="directive">ServerName</code> is used (possibly
3790 in conjunction with <code class="directive">ServerAlias</code>) to uniquely
3791 identify a virtual host, when using <a href="../vhosts/name-based.html">name-based virtual hosts</a>.</p>
3793 <p>For example, if the name of the
3794 machine hosting the web server is <code>simple.example.com</code>,
3795 but the machine also has the DNS alias <code>www.example.com</code>
3796 and you wish the web server to be so identified, the following
3797 directive should be used:</p>
3799 <div class="example"><p><code>
3800 ServerName www.example.com:80
3803 <p>The <code class="directive">ServerName</code> directive
3804 may appear anywhere within the definition of a server. However,
3805 each appearance overrides the previous appearance (within that
3808 <p>If no <code class="directive">ServerName</code> is specified, then the
3809 server attempts to deduce the hostname by performing a reverse
3810 lookup on the IP address. If no port is specified in the
3811 <code class="directive">ServerName</code>, then the server will use the
3812 port from the incoming request. For optimal reliability and
3813 predictability, you should specify an explicit hostname and port
3814 using the <code class="directive">ServerName</code> directive.</p>
3816 <p>If you are using <a href="../vhosts/name-based.html">name-based virtual hosts</a>,
3817 the <code class="directive">ServerName</code> inside a
3818 <code class="directive"><a href="#virtualhost"><VirtualHost></a></code>
3819 section specifies what hostname must appear in the request's
3820 <code>Host:</code> header to match this virtual host.</p>
3822 <p>Sometimes, the server runs behind a device that processes SSL,
3823 such as a reverse proxy, load balancer or SSL offload
3824 appliance. When this is the case, specify the
3825 <code>https://</code> scheme and the port number to which the
3826 clients connect in the <code class="directive">ServerName</code> directive
3827 to make sure that the server generates the correct
3828 self-referential URLs.
3831 <p>See the description of the
3832 <code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code> and
3833 <code class="directive"><a href="#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></code> directives for
3834 settings which determine whether self-referential URLs (e.g., by the
3835 <code class="module"><a href="../mod/mod_dir.html">mod_dir</a></code> module) will refer to the
3836 specified port, or to the port number given in the client's request.
3839 <div class="warning">
3840 <p>Failure to set <code class="directive">ServerName</code> to a name that
3841 your server can resolve to an IP address will result in a startup
3842 warning. <code>httpd</code> will then use whatever hostname it can
3843 determine, using the system's <code>hostname</code> command. This
3844 will almost never be the hostname you actually want.</p>
3845 <div class="example"><p><code>
3846 httpd: Could not reliably determine the server's fully qualified domain name, using rocinante.local for ServerName
3851 <h3>Consulte también</h3>
3853 <li><a href="../dns-caveats.html">Issues Regarding DNS and
3854 Apache HTTP Server</a></li>
3855 <li><a href="../vhosts/">Apache HTTP Server virtual host
3856 documentation</a></li>
3857 <li><code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code></li>
3858 <li><code class="directive"><a href="#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></code></li>
3859 <li><code class="directive"><a href="#namevirtualhost">NameVirtualHost</a></code></li>
3860 <li><code class="directive"><a href="#serveralias">ServerAlias</a></code></li>
3863 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3864 <div class="directive-section"><h2><a name="ServerPath" id="ServerPath">ServerPath</a> <a name="serverpath" id="serverpath">Directiva</a></h2>
3865 <table class="directive">
3866 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Legacy URL pathname for a name-based virtual host that
3867 is accessed by an incompatible browser</td></tr>
3868 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ServerPath <var>URL-path</var></code></td></tr>
3869 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>virtual host</td></tr>
3870 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3871 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3873 <p>The <code class="directive">ServerPath</code> directive sets the legacy
3874 URL pathname for a host, for use with <a href="../vhosts/">name-based virtual hosts</a>.</p>
3876 <h3>Consulte también</h3>
3878 <li><a href="../vhosts/">Apache HTTP Server Virtual Host documentation</a></li>
3881 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3882 <div class="directive-section"><h2><a name="ServerRoot" id="ServerRoot">ServerRoot</a> <a name="serverroot" id="serverroot">Directiva</a></h2>
3883 <table class="directive">
3884 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Base directory for the server installation</td></tr>
3885 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ServerRoot <var>directory-path</var></code></td></tr>
3886 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ServerRoot /usr/local/apache</code></td></tr>
3887 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
3888 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3889 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3891 <p>The <code class="directive">ServerRoot</code> directive sets the
3892 directory in which the server lives. Typically it will contain the
3893 subdirectories <code>conf/</code> and <code>logs/</code>. Relative
3894 paths in other configuration directives (such as <code class="directive"><a href="#include">Include</a></code> or <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code>, for example) are taken as
3895 relative to this directory.</p>
3897 <div class="example"><h3>Example</h3><p><code>
3898 ServerRoot /home/httpd
3902 <h3>Consulte también</h3>
3904 <li><a href="../invoking.html">the <code>-d</code>
3905 option to <code>httpd</code></a></li>
3906 <li><a href="../misc/security_tips.html#serverroot">the
3907 security tips</a> for information on how to properly set
3908 permissions on the <code class="directive">ServerRoot</code></li>
3911 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3912 <div class="directive-section"><h2><a name="ServerSignature" id="ServerSignature">ServerSignature</a> <a name="serversignature" id="serversignature">Directiva</a></h2>
3913 <table class="directive">
3914 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures the footer on server-generated documents</td></tr>
3915 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ServerSignature On|Off|EMail</code></td></tr>
3916 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ServerSignature Off</code></td></tr>
3917 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3918 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
3919 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3920 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3922 <p>The <code class="directive">ServerSignature</code> directive allows the
3923 configuration of a trailing footer line under server-generated
3924 documents (error messages, <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> ftp directory
3925 listings, <code class="module"><a href="../mod/mod_info.html">mod_info</a></code> output, ...). The reason why you
3926 would want to enable such a footer line is that in a chain of proxies,
3927 the user often has no possibility to tell which of the chained servers
3928 actually produced a returned error message.</p>
3930 <p>The <code>Off</code>
3931 setting, which is the default, suppresses the footer line (and is
3932 therefore compatible with the behavior of Apache-1.2 and
3933 below). The <code>On</code> setting simply adds a line with the
3934 server version number and <code class="directive"><a href="#servername">ServerName</a></code> of the serving virtual host,
3935 and the <code>EMail</code> setting additionally creates a
3936 "mailto:" reference to the <code class="directive"><a href="#serveradmin">ServerAdmin</a></code> of the referenced
3939 <p>After version 2.0.44, the details of the server version number
3940 presented are controlled by the <code class="directive"><a href="#servertokens">ServerTokens</a></code> directive.</p>
3942 <h3>Consulte también</h3>
3944 <li><code class="directive"><a href="#servertokens">ServerTokens</a></code></li>
3947 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3948 <div class="directive-section"><h2><a name="ServerTokens" id="ServerTokens">ServerTokens</a> <a name="servertokens" id="servertokens">Directiva</a></h2>
3949 <table class="directive">
3950 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures the <code>Server</code> HTTP response
3952 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ServerTokens Major|Minor|Min[imal]|Prod[uctOnly]|OS|Full</code></td></tr>
3953 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ServerTokens Full</code></td></tr>
3954 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
3955 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3956 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3958 <p>This directive controls whether <code>Server</code> response
3959 header field which is sent back to clients includes a
3960 description of the generic OS-type of the server as well as
3961 information about compiled-in modules.</p>
3964 <dt><code>ServerTokens Full</code> (or not specified)</dt>
3966 <dd>Server sends (<em>e.g.</em>): <code>Server: Apache/2.4.1
3967 (Unix) PHP/4.2.2 MyMod/1.2</code></dd>
3969 <dt><code>ServerTokens Prod[uctOnly]</code></dt>
3971 <dd>Server sends (<em>e.g.</em>): <code>Server:
3974 <dt><code>ServerTokens Major</code></dt>
3976 <dd>Server sends (<em>e.g.</em>): <code>Server:
3977 Apache/2</code></dd>
3979 <dt><code>ServerTokens Minor</code></dt>
3981 <dd>Server sends (<em>e.g.</em>): <code>Server:
3982 Apache/2.4</code></dd>
3984 <dt><code>ServerTokens Min[imal]</code></dt>
3986 <dd>Server sends (<em>e.g.</em>): <code>Server:
3987 Apache/2.4.1</code></dd>
3989 <dt><code>ServerTokens OS</code></dt>
3991 <dd>Server sends (<em>e.g.</em>): <code>Server: Apache/2.4.1
3996 <p>This setting applies to the entire server, and cannot be
3997 enabled or disabled on a virtualhost-by-virtualhost basis.</p>
3999 <p>After version 2.0.44, this directive also controls the
4000 information presented by the <code class="directive"><a href="#serversignature">ServerSignature</a></code> directive.</p>
4002 <div class="note">Setting <code class="directive">ServerTokens</code> to less than
4003 <code>minimal</code> is not recommended because it makes it more
4004 difficult to debug interoperational problems. Also note that
4005 disabling the Server: header does nothing at all to make your
4006 server more secure; the idea of "security through obscurity"
4007 is a myth and leads to a false sense of safety.</div>
4010 <h3>Consulte también</h3>
4012 <li><code class="directive"><a href="#serversignature">ServerSignature</a></code></li>
4015 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4016 <div class="directive-section"><h2><a name="SetHandler" id="SetHandler">SetHandler</a> <a name="sethandler" id="sethandler">Directiva</a></h2>
4017 <table class="directive">
4018 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Forces all matching files to be processed by a
4020 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>SetHandler <var>handler-name</var>|None</code></td></tr>
4021 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
4022 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
4023 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4024 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4025 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Moved into the core in Apache httpd 2.0</td></tr>
4027 <p>When placed into an <code>.htaccess</code> file or a
4028 <code class="directive"><a href="#directory"><Directory></a></code> or
4029 <code class="directive"><a href="#location"><Location></a></code>
4030 section, this directive forces all matching files to be parsed
4031 through the <a href="../handler.html">handler</a> given by
4032 <var>handler-name</var>. For example, if you had a directory you
4033 wanted to be parsed entirely as imagemap rule files, regardless
4034 of extension, you might put the following into an
4035 <code>.htaccess</code> file in that directory:</p>
4037 <div class="example"><p><code>
4038 SetHandler imap-file
4041 <p>Another example: if you wanted to have the server display a
4042 status report whenever a URL of
4043 <code>http://servername/status</code> was called, you might put
4044 the following into <code>httpd.conf</code>:</p>
4046 <div class="example"><p><code>
4047 <Location /status><br />
4048 <span class="indent">
4049 SetHandler server-status<br />
4054 <p>You can override an earlier defined <code class="directive">SetHandler</code>
4055 directive by using the value <code>None</code>.</p>
4056 <p><strong>Note:</strong> because SetHandler overrides default handlers,
4057 normal behaviour such as handling of URLs ending in a slash (/) as
4058 directories or index files is suppressed.</p>
4060 <h3>Consulte también</h3>
4062 <li><code class="directive"><a href="../mod/mod_mime.html#addhandler">AddHandler</a></code></li>
4065 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4066 <div class="directive-section"><h2><a name="SetInputFilter" id="SetInputFilter">SetInputFilter</a> <a name="setinputfilter" id="setinputfilter">Directiva</a></h2>
4067 <table class="directive">
4068 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Sets the filters that will process client requests and POST
4070 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>SetInputFilter <var>filter</var>[;<var>filter</var>...]</code></td></tr>
4071 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
4072 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
4073 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4074 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4076 <p>The <code class="directive">SetInputFilter</code> directive sets the
4077 filter or filters which will process client requests and POST
4078 input when they are received by the server. This is in addition to
4079 any filters defined elsewhere, including the
4080 <code class="directive"><a href="../mod/mod_mime.html#addinputfilter">AddInputFilter</a></code>
4083 <p>If more than one filter is specified, they must be separated
4084 by semicolons in the order in which they should process the
4087 <h3>Consulte también</h3>
4089 <li><a href="../filter.html">Filters</a> documentation</li>
4092 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4093 <div class="directive-section"><h2><a name="SetOutputFilter" id="SetOutputFilter">SetOutputFilter</a> <a name="setoutputfilter" id="setoutputfilter">Directiva</a></h2>
4094 <table class="directive">
4095 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Sets the filters that will process responses from the
4097 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>SetOutputFilter <var>filter</var>[;<var>filter</var>...]</code></td></tr>
4098 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
4099 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
4100 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4101 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4103 <p>The <code class="directive">SetOutputFilter</code> directive sets the filters
4104 which will process responses from the server before they are
4105 sent to the client. This is in addition to any filters defined
4106 elsewhere, including the
4107 <code class="directive"><a href="../mod/mod_mime.html#addoutputfilter">AddOutputFilter</a></code>
4110 <p>For example, the following configuration will process all files
4111 in the <code>/www/data/</code> directory for server-side
4114 <div class="example"><p><code>
4115 <Directory /www/data/><br />
4116 <span class="indent">
4117 SetOutputFilter INCLUDES<br />
4122 <p>If more than one filter is specified, they must be separated
4123 by semicolons in the order in which they should process the
4126 <h3>Consulte también</h3>
4128 <li><a href="../filter.html">Filters</a> documentation</li>
4131 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4132 <div class="directive-section"><h2><a name="TimeOut" id="TimeOut">TimeOut</a> <a name="timeout" id="timeout">Directiva</a></h2>
4133 <table class="directive">
4134 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Amount of time the server will wait for
4135 certain events before failing a request</td></tr>
4136 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>TimeOut <var>seconds</var></code></td></tr>
4137 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>TimeOut 60</code></td></tr>
4138 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
4139 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4140 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4142 <p>The <code class="directive">TimeOut</code> directive defines the length
4143 of time Apache httpd will wait for I/O in various circumstances:</p>
4146 <li>When reading data from the client, the length of time to
4147 wait for a TCP packet to arrive if the read buffer is
4150 <li>When writing data to the client, the length of time to wait
4151 for an acknowledgement of a packet if the send buffer is
4154 <li>In <code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code>, the length of time to wait for
4155 output from a CGI script.</li>
4157 <li>In <code class="module"><a href="../mod/mod_ext_filter.html">mod_ext_filter</a></code>, the length of time to
4158 wait for output from a filtering process.</li>
4160 <li>In <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>, the default timeout value if
4161 <code class="directive"><a href="../mod/mod_proxy.html#proxytimeout">ProxyTimeout</a></code> is not
4167 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4168 <div class="directive-section"><h2><a name="TraceEnable" id="TraceEnable">TraceEnable</a> <a name="traceenable" id="traceenable">Directiva</a></h2>
4169 <table class="directive">
4170 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determines the behaviour on <code>TRACE</code> requests</td></tr>
4171 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>TraceEnable <var>[on|off|extended]</var></code></td></tr>
4172 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>TraceEnable on</code></td></tr>
4173 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
4174 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4175 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4176 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 1.3.34, 2.0.55 and later</td></tr>
4178 <p>This directive overrides the behavior of <code>TRACE</code> for both
4179 the core server and <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>. The default
4180 <code>TraceEnable on</code> permits <code>TRACE</code> requests per
4181 RFC 2616, which disallows any request body to accompany the request.
4182 <code>TraceEnable off</code> causes the core server and
4183 <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> to return a <code>405</code> (Method not
4184 allowed) error to the client.</p>
4186 <p>Finally, for testing and diagnostic purposes only, request
4187 bodies may be allowed using the non-compliant <code>TraceEnable
4188 extended</code> directive. The core (as an origin server) will
4189 restrict the request body to 64k (plus 8k for chunk headers if
4190 <code>Transfer-Encoding: chunked</code> is used). The core will
4191 reflect the full headers and all chunk headers with the response
4192 body. As a proxy server, the request body is not restricted to 64k.</p>
4195 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4196 <div class="directive-section"><h2><a name="UnDefine" id="UnDefine">UnDefine</a> <a name="undefine" id="undefine">Directiva</a></h2>
4197 <table class="directive">
4198 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Undefine the existence of a variable</td></tr>
4199 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>UnDefine <var>parameter-name</var></code></td></tr>
4200 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
4201 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4202 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4204 <p>Undoes the effect of a <code class="directive"><a href="#define">Define</a></code> or
4205 of passing a <code>-D</code> argument to <code class="program"><a href="../programs/httpd.html">httpd</a></code>.</p>
4206 <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
4207 <code>-D</code> arguments in any startup scripts.</p>
4210 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4211 <div class="directive-section"><h2><a name="UseCanonicalName" id="UseCanonicalName">UseCanonicalName</a> <a name="usecanonicalname" id="usecanonicalname">Directiva</a></h2>
4212 <table class="directive">
4213 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures how the server determines its own name and
4215 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>UseCanonicalName On|Off|DNS</code></td></tr>
4216 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>UseCanonicalName Off</code></td></tr>
4217 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
4218 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4219 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4221 <p>In many situations Apache httpd must construct a <em>self-referential</em>
4222 URL -- that is, a URL that refers back to the same server. With
4223 <code>UseCanonicalName On</code> Apache httpd will use the hostname and port
4224 specified in the <code class="directive"><a href="#servername">ServerName</a></code>
4225 directive to construct the canonical name for the server. This name
4226 is used in all self-referential URLs, and for the values of
4227 <code>SERVER_NAME</code> and <code>SERVER_PORT</code> in CGIs.</p>
4229 <p>With <code>UseCanonicalName Off</code> Apache httpd will form
4230 self-referential URLs using the hostname and port supplied by
4231 the client if any are supplied (otherwise it will use the
4232 canonical name, as defined above). These values are the same
4233 that are used to implement <a href="../vhosts/name-based.html">name-based virtual hosts</a>,
4234 and are available with the same clients. The CGI variables
4235 <code>SERVER_NAME</code> and <code>SERVER_PORT</code> will be
4236 constructed from the client supplied values as well.</p>
4238 <p>An example where this may be useful is on an intranet server
4239 where you have users connecting to the machine using short
4240 names such as <code>www</code>. You'll notice that if the users
4241 type a shortname, and a URL which is a directory, such as
4242 <code>http://www/splat</code>, <em>without the trailing
4243 slash</em> then Apache httpd will redirect them to
4244 <code>http://www.domain.com/splat/</code>. If you have
4245 authentication enabled, this will cause the user to have to
4246 authenticate twice (once for <code>www</code> and once again
4247 for <code>www.domain.com</code> -- see <a href="http://httpd.apache.org/docs/misc/FAQ.html#prompted-twice">the
4248 FAQ on this subject for more information</a>). But if
4249 <code class="directive">UseCanonicalName</code> is set <code>Off</code>, then
4250 Apache httpd will redirect to <code>http://www/splat/</code>.</p>
4252 <p>There is a third option, <code>UseCanonicalName DNS</code>,
4253 which is intended for use with mass IP-based virtual hosting to
4254 support ancient clients that do not provide a
4255 <code>Host:</code> header. With this option Apache httpd does a
4256 reverse DNS lookup on the server IP address that the client
4257 connected to in order to work out self-referential URLs.</p>
4259 <div class="warning"><h3>Warning</h3>
4260 <p>If CGIs make assumptions about the values of <code>SERVER_NAME</code>
4261 they may be broken by this option. The client is essentially free
4262 to give whatever value they want as a hostname. But if the CGI is
4263 only using <code>SERVER_NAME</code> to construct self-referential URLs
4264 then it should be just fine.</p>
4267 <h3>Consulte también</h3>
4269 <li><code class="directive"><a href="#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></code></li>
4270 <li><code class="directive"><a href="#servername">ServerName</a></code></li>
4271 <li><code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code></li>
4274 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4275 <div class="directive-section"><h2><a name="UseCanonicalPhysicalPort" id="UseCanonicalPhysicalPort">UseCanonicalPhysicalPort</a> <a name="usecanonicalphysicalport" id="usecanonicalphysicalport">Directiva</a></h2>
4276 <table class="directive">
4277 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures how the server determines its own name and
4279 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>UseCanonicalPhysicalPort On|Off</code></td></tr>
4280 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>UseCanonicalPhysicalPort Off</code></td></tr>
4281 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
4282 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4283 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4285 <p>In many situations Apache httpd must construct a <em>self-referential</em>
4286 URL -- that is, a URL that refers back to the same server. With
4287 <code>UseCanonicalPhysicalPort On</code> Apache httpd will, when
4288 constructing the canonical port for the server to honor
4289 the <code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code> directive,
4290 provide the actual physical port number being used by this request
4291 as a potential port. With <code>UseCanonicalPhysicalPort Off</code>
4292 Apache httpd will not ever use the actual physical port number, instead
4293 relying on all configured information to construct a valid port number.</p>
4295 <div class="note"><h3>Note</h3>
4296 <p>The ordering of when the physical port is used is as follows:<br /><br />
4297 <code>UseCanonicalName On</code></p>
4299 <li>Port provided in <code>Servername</code></li>
4300 <li>Physical port</li>
4301 <li>Default port</li>
4303 <code>UseCanonicalName Off | DNS</code>
4305 <li>Parsed port from <code>Host:</code> header</li>
4306 <li>Physical port</li>
4307 <li>Port provided in <code>Servername</code></li>
4308 <li>Default port</li>
4311 <p>With <code>UseCanonicalPhysicalPort Off</code>, the
4312 physical ports are removed from the ordering.</p>
4316 <h3>Consulte también</h3>
4318 <li><code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code></li>
4319 <li><code class="directive"><a href="#servername">ServerName</a></code></li>
4320 <li><code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code></li>
4323 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4324 <div class="directive-section"><h2><a name="VirtualHost" id="VirtualHost"><VirtualHost></a> <a name="virtualhost" id="virtualhost">Directiva</a></h2>
4325 <table class="directive">
4326 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply only to a specific
4327 hostname or IP address</td></tr>
4328 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><VirtualHost
4329 <var>addr</var>[:<var>port</var>] [<var>addr</var>[:<var>port</var>]]
4330 ...> ... </VirtualHost></code></td></tr>
4331 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
4332 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4333 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4335 <p><code class="directive"><VirtualHost></code> and
4336 <code></VirtualHost></code> are used to enclose a group of
4337 directives that will apply only to a particular virtual host. Any
4338 directive that is allowed in a virtual host context may be
4339 used. When the server receives a request for a document on a
4340 particular virtual host, it uses the configuration directives
4341 enclosed in the <code class="directive"><VirtualHost></code>
4342 section. <var>Addr</var> can be:</p>
4345 <li>The IP address of the virtual host;</li>
4347 <li>A fully qualified domain name for the IP address of the
4348 virtual host (not recommended);</li>
4350 <li>The character <code>*</code>, which is used only in combination with
4351 <code>NameVirtualHost *</code> to match all IP addresses; or</li>
4353 <li>The string <code>_default_</code>, which is used only
4354 with IP virtual hosting to catch unmatched IP addresses.</li>
4357 <div class="example"><h3>Example</h3><p><code>
4358 <VirtualHost 10.1.2.3><br />
4359 <span class="indent">
4360 ServerAdmin webmaster@host.example.com<br />
4361 DocumentRoot /www/docs/host.example.com<br />
4362 ServerName host.example.com<br />
4363 ErrorLog logs/host.example.com-error_log<br />
4364 TransferLog logs/host.example.com-access_log<br />
4366 </VirtualHost>
4370 <p>IPv6 addresses must be specified in square brackets because
4371 the optional port number could not be determined otherwise. An
4372 IPv6 example is shown below:</p>
4374 <div class="example"><p><code>
4375 <VirtualHost [2001:db8::a00:20ff:fea7:ccea]><br />
4376 <span class="indent">
4377 ServerAdmin webmaster@host.example.com<br />
4378 DocumentRoot /www/docs/host.example.com<br />
4379 ServerName host.example.com<br />
4380 ErrorLog logs/host.example.com-error_log<br />
4381 TransferLog logs/host.example.com-access_log<br />
4383 </VirtualHost>
4386 <p>Each Virtual Host must correspond to a different IP address,
4387 different port number or a different host name for the server,
4388 in the former case the server machine must be configured to
4389 accept IP packets for multiple addresses. (If the machine does
4390 not have multiple network interfaces, then this can be
4391 accomplished with the <code>ifconfig alias</code> command -- if
4392 your OS supports it).</p>
4394 <div class="note"><h3>Note</h3>
4395 <p>The use of <code class="directive"><VirtualHost></code> does
4396 <strong>not</strong> affect what addresses Apache httpd listens on. You
4397 may need to ensure that Apache httpd is listening on the correct addresses
4398 using <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>.</p>
4401 <p>When using IP-based virtual hosting, the special name
4402 <code>_default_</code> can be specified in
4403 which case this virtual host will match any IP address that is
4404 not explicitly listed in another virtual host. In the absence
4405 of any <code>_default_</code> virtual host the "main" server config,
4406 consisting of all those definitions outside any VirtualHost
4407 section, is used when no IP-match occurs.</p>
4409 <p>You can specify a <code>:port</code> to change the port that is
4410 matched. If unspecified then it defaults to the same port as the
4411 most recent <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>
4412 statement of the main server. You may also specify <code>:*</code>
4413 to match all ports on that address. (This is recommended when used
4414 with <code>_default_</code>.)</p>
4416 <p>A <code class="directive"><a href="#servername">ServerName</a></code> should be
4417 specified inside each <code class="directive"><VirtualHost></code> block. If it is absent, the
4418 <code class="directive"><a href="#servername">ServerName</a></code> from the "main"
4419 server configuration will be inherited.</p>
4421 <p>If no matching virtual host is found, then the first listed
4422 virtual host that matches the IP address will be used. As a
4423 consequence, the first listed virtual host is the default virtual
4426 <div class="warning"><h3>Security</h3>
4427 <p>See the <a href="../misc/security_tips.html">security tips</a>
4428 document for details on why your security could be compromised if the
4429 directory where log files are stored is writable by anyone other
4430 than the user that starts the server.</p>
4433 <h3>Consulte también</h3>
4435 <li><a href="../vhosts/">Apache HTTP Server Virtual Host documentation</a></li>
4436 <li><a href="../dns-caveats.html">Issues Regarding DNS and
4437 Apache HTTP Server</a></li>
4438 <li><a href="../bind.html">Setting
4439 which addresses and ports Apache HTTP Server uses</a></li>
4440 <li><a href="../sections.html">How <Directory>, <Location>
4441 and <Files> sections work</a> for an explanation of how these
4442 different sections are combined when a request is received</li>
4445 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4446 <div class="directive-section"><h2><a name="Warning" id="Warning">Warning</a> <a name="warning" id="warning">Directiva</a></h2>
4447 <table class="directive">
4448 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Warn from configuration parsing with a custom message</td></tr>
4449 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Warning <var>message</var></code></td></tr>
4450 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
4451 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4452 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4453 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>2.5 and later</td></tr>
4454 </table><p>The documentation for this directive has
4455 not been translated yet. Please have a look at the English
4458 <div class="bottomlang">
4459 <p><span>Idiomas disponibles: </span><a href="../de/mod/core.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> |
4460 <a href="../en/mod/core.html" hreflang="en" rel="alternate" title="English"> en </a> |
4461 <a href="../es/mod/core.html" title="Español"> es </a> |
4462 <a href="../fr/mod/core.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
4463 <a href="../ja/mod/core.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
4464 <a href="../tr/mod/core.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p>
4465 </div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comentarios</a></h2><div class="warning"><strong>Notice:</strong><br />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 <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div>
4466 <script type="text/javascript"><!--//--><![CDATA[//><!--
4467 var comments_shortname = 'httpd';
4468 var comments_identifier = 'http://httpd.apache.org/docs/trunk/mod/core.html';
4470 if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
4471 d.write('<div id="comments_thread"><\/div>');
4472 var s = d.createElement('script');
4473 s.type = 'text/javascript';
4475 s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
4476 (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
4479 d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
4481 })(window, document);
4482 //--><!]]></script></div><div id="footer">
4483 <p class="apache">Copyright 2016 The Apache Software Foundation.<br />Licencia bajo los términos de la <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
4484 <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></div><script type="text/javascript"><!--//--><
projects / apache / blob