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="#if"><If></a></li>
79 <li><img alt="" src="../images/down.gif" /> <a href="#ifdefine"><IfDefine></a></li>
80 <li><img alt="" src="../images/down.gif" /> <a href="#ifmodule"><IfModule></a></li>
81 <li><img alt="" src="../images/down.gif" /> <a href="#include">Include</a></li>
82 <li><img alt="" src="../images/down.gif" /> <a href="#includeoptional">IncludeOptional</a></li>
83 <li><img alt="" src="../images/down.gif" /> <a href="#keepalive">KeepAlive</a></li>
84 <li><img alt="" src="../images/down.gif" /> <a href="#keepalivetimeout">KeepAliveTimeout</a></li>
85 <li><img alt="" src="../images/down.gif" /> <a href="#limit"><Limit></a></li>
86 <li><img alt="" src="../images/down.gif" /> <a href="#limitexcept"><LimitExcept></a></li>
87 <li><img alt="" src="../images/down.gif" /> <a href="#limitinternalrecursion">LimitInternalRecursion</a></li>
88 <li><img alt="" src="../images/down.gif" /> <a href="#limitrequestbody">LimitRequestBody</a></li>
89 <li><img alt="" src="../images/down.gif" /> <a href="#limitrequestfields">LimitRequestFields</a></li>
90 <li><img alt="" src="../images/down.gif" /> <a href="#limitrequestfieldsize">LimitRequestFieldSize</a></li>
91 <li><img alt="" src="../images/down.gif" /> <a href="#limitrequestline">LimitRequestLine</a></li>
92 <li><img alt="" src="../images/down.gif" /> <a href="#limitxmlrequestbody">LimitXMLRequestBody</a></li>
93 <li><img alt="" src="../images/down.gif" /> <a href="#location"><Location></a></li>
94 <li><img alt="" src="../images/down.gif" /> <a href="#locationmatch"><LocationMatch></a></li>
95 <li><img alt="" src="../images/down.gif" /> <a href="#loglevel">LogLevel</a></li>
96 <li><img alt="" src="../images/down.gif" /> <a href="#logleveloverride">LogLevelOverride</a></li>
97 <li><img alt="" src="../images/down.gif" /> <a href="#maxkeepaliverequests">MaxKeepAliveRequests</a></li>
98 <li><img alt="" src="../images/down.gif" /> <a href="#maxrangeoverlaps">MaxRangeOverlaps</a></li>
99 <li><img alt="" src="../images/down.gif" /> <a href="#maxrangereversals">MaxRangeReversals</a></li>
100 <li><img alt="" src="../images/down.gif" /> <a href="#maxranges">MaxRanges</a></li>
101 <li><img alt="" src="../images/down.gif" /> <a href="#mergetrailers">MergeTrailers</a></li>
102 <li><img alt="" src="../images/down.gif" /> <a href="#mutex">Mutex</a></li>
103 <li><img alt="" src="../images/down.gif" /> <a href="#namevirtualhost">NameVirtualHost</a></li>
104 <li><img alt="" src="../images/down.gif" /> <a href="#options">Options</a></li>
105 <li><img alt="" src="../images/down.gif" /> <a href="#protocol">Protocol</a></li>
106 <li><img alt="" src="../images/down.gif" /> <a href="#protocols">Protocols</a></li>
107 <li><img alt="" src="../images/down.gif" /> <a href="#protocolshonororder">ProtocolsHonorOrder</a></li>
108 <li><img alt="" src="../images/down.gif" /> <a href="#qualifyredirecturl">QualifyRedirectURL</a></li>
109 <li><img alt="" src="../images/down.gif" /> <a href="#registerhttpmethod">RegisterHttpMethod</a></li>
110 <li><img alt="" src="../images/down.gif" /> <a href="#rlimitcpu">RLimitCPU</a></li>
111 <li><img alt="" src="../images/down.gif" /> <a href="#rlimitmem">RLimitMEM</a></li>
112 <li><img alt="" src="../images/down.gif" /> <a href="#rlimitnproc">RLimitNPROC</a></li>
113 <li><img alt="" src="../images/down.gif" /> <a href="#scriptinterpretersource">ScriptInterpreterSource</a></li>
114 <li><img alt="" src="../images/down.gif" /> <a href="#seerequesttail">SeeRequestTail</a></li>
115 <li><img alt="" src="../images/down.gif" /> <a href="#serveradmin">ServerAdmin</a></li>
116 <li><img alt="" src="../images/down.gif" /> <a href="#serveralias">ServerAlias</a></li>
117 <li><img alt="" src="../images/down.gif" /> <a href="#servername">ServerName</a></li>
118 <li><img alt="" src="../images/down.gif" /> <a href="#serverpath">ServerPath</a></li>
119 <li><img alt="" src="../images/down.gif" /> <a href="#serverroot">ServerRoot</a></li>
120 <li><img alt="" src="../images/down.gif" /> <a href="#serversignature">ServerSignature</a></li>
121 <li><img alt="" src="../images/down.gif" /> <a href="#servertokens">ServerTokens</a></li>
122 <li><img alt="" src="../images/down.gif" /> <a href="#sethandler">SetHandler</a></li>
123 <li><img alt="" src="../images/down.gif" /> <a href="#setinputfilter">SetInputFilter</a></li>
124 <li><img alt="" src="../images/down.gif" /> <a href="#setoutputfilter">SetOutputFilter</a></li>
125 <li><img alt="" src="../images/down.gif" /> <a href="#timeout">TimeOut</a></li>
126 <li><img alt="" src="../images/down.gif" /> <a href="#traceenable">TraceEnable</a></li>
127 <li><img alt="" src="../images/down.gif" /> <a href="#undefine">UnDefine</a></li>
128 <li><img alt="" src="../images/down.gif" /> <a href="#usecanonicalname">UseCanonicalName</a></li>
129 <li><img alt="" src="../images/down.gif" /> <a href="#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></li>
130 <li><img alt="" src="../images/down.gif" /> <a href="#virtualhost"><VirtualHost></a></li>
131 <li><img alt="" src="../images/down.gif" /> <a href="#warning">Warning</a></li>
133 <ul class="seealso"><li><a href="#comments_section">Comentarios</a></li></ul></div>
135 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
136 <div class="directive-section"><h2><a name="AcceptFilter" id="AcceptFilter">AcceptFilter</a> <a name="acceptfilter" id="acceptfilter">Directiva</a></h2>
137 <table class="directive">
138 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configura mejoras para un Protocolo de Escucha de Sockets</td></tr>
139 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AcceptFilter <var>protocol</var> <var>accept_filter</var></code></td></tr>
140 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
141 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
142 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
143 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Disponible en Apache httpd 2.1.5 y posteriores.
144 En Windows desde Apache httpd 2.3.3 y posteriores.</td></tr>
146 <p>Esta directiva hace posible mejoras específicas a nivel de sistema operativo
147 y a través del tipo de Protocolo para un socket que escucha.
148 La premisa básica es que el kernel no envíe un socket al servidor
149 hasta que o bien los datos se hayan recibido o bien se haya almacenado
150 en el buffer una Respuesta HTTP completa.
151 Actualmente sólo están soportados
152 <a href="http://www.freebsd.org/cgi/man.cgi?query=accept_filter&sektion=9">
153 Accept Filters</a> sobre FreeBSD, <code>TCP_DEFER_ACCEPT</code> sobre Linux,
154 y AcceptEx() sobre Windows.</p>
156 <p>El uso de <code>none</code> para un argumento desactiva cualquier filtro
157 aceptado para ese protocolo. Esto es útil para protocolos que requieren que un
158 servidor envíe datos primeros, tales como <code>ftp:</code> o <code>nntp</code>:</p>
159 <div class="example"><p><code>AcceptFilter nntp none</code></p></div>
161 <p>Los nombres de protocolo por defecto son <code>https</code> para el puerto 443
162 y <code>http</code> para todos los demás puertos. Para especificar que se está
163 utilizando otro protocolo con un puerto escuchando, añade el argumento <var>protocol</var>
164 a la directiva <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>.</p>
166 <p>Sobre FreeBDS los valores por defecto:</p>
167 <div class="example"><p><code>
168 AcceptFilter http httpready <br />
169 AcceptFilter https dataready
172 <p>El filtro <code>httpready</code> almacena en el buffer peticiones HTTP completas
173 a nivel de kernel. Una vez que la petición es recibida, el kernel la envía al servidor.
174 Consulta la página man de
175 <a href="http://www.freebsd.org/cgi/man.cgi?query=accf_http&sektion=9">
176 accf_http(9)</a> para más detalles. Puesto que las peticiones HTTPS
177 están encriptadas, sólo se utiliza el filtro
178 <a href="http://www.freebsd.org/cgi/man.cgi?query=accf_data&sektion=9">accf_data(9)</a>.</p>
180 <p>Sobre Linux los valores por defecto son:</p>
181 <div class="example"><p><code>
182 AcceptFilter http data <br />
183 AcceptFilter https data
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://homepages.cwi.nl/~aeb/linux/man2html/man7/tcp.7.html">
193 <p>Sobre Windows los valores por defecto son:</p>
194 <div class="example"><p><code>
195 AcceptFilter http data <br />
196 AcceptFilter https data
199 <p>Sobre Windows mpm_winnt interpreta el argumento AcceptFilter para conmutar la API
200 AcceptEx(), y no soporta el buffering sobre el protocolo http. Hay dos valores
201 que utilizan la API Windows AcceptEx() y que recuperan sockets de red
202 entre conexciones. <code>data</code> espera hasta que los datos han sido
203 transmitidos como se comentaba anteriormente, y el buffer inicial de datos y las
204 direcciones de red son recuperadas a partir de una única llamada AcceptEx().
205 <code>connect</code> utiliza la API AcceptEx() API, y recupera también
206 las direcciones de red, pero a diferencia de <code>none</code>
207 la opción <code>connect</code> no espera a la transmisión inicial de los datos.</p>
209 <p>Sobre Windows, <code>none</code> prefiere accept() antes que AcceptEx()
210 y no recuperará sockets entre las conexiones. Lo que es útil para los adaptadores de
211 red con un soporte precario de drivers, así como para algunos proveedores de red
212 tales como drivers vpn, o filtros de spam, de virus o de spyware.</p>
215 <h3>Consulte también</h3>
217 <li><code class="directive">Protocol</code></li>
220 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
221 <div class="directive-section"><h2><a name="AcceptPathInfo" id="AcceptPathInfo">AcceptPathInfo</a> <a name="acceptpathinfo" id="acceptpathinfo">Directiva</a></h2>
222 <table class="directive">
223 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Los recursos aceptan información sobre su ruta</td></tr>
224 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AcceptPathInfo On|Off|Default</code></td></tr>
225 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AcceptPathInfo Default</code></td></tr>
226 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
227 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
228 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
229 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
230 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Disponible en Apache httpd 2.0.30 y posteriores</td></tr>
233 <p>Esta directiva controla si las peticiones que contienen información sobre la ruta
234 que sigue un fichero que existe (o un fichero que no existe pero en un directorio que
235 sí existe) serán aceptadas o denegadas. La información de ruta puede estar disponible
236 para los scripts en la variable de entorno <code>PATH_INFO</code>.</p>
238 <p>Por ejemplo, asumamos que la ubicación <code>/test/</code> apunta a
239 un directorio que contiene únicamente el fichero
240 <code>here.html</code>. Entonces, las peticiones tanto para
241 <code>/test/here.html/more</code> como para
242 <code>/test/nothere.html/more</code> recogen
243 <code>/more</code> como <code>PATH_INFO</code>.</p>
245 <p>Los tres posibles argumentos para la directiva
246 <code class="directive">AcceptPathInfo</code> son los siguientes:</p>
248 <dt><code>Off</code></dt><dd>Una petición sólo será aceptada si
249 se corresponde con una ruta literal que existe. Por lo tanto, una petición
250 con una información de ruta después del nombre de fichero tal como
251 <code>/test/here.html/more</code> en el ejemplo anterior devolverá
252 un error 404 NOT FOUND.</dd>
254 <dt><code>On</code></dt><dd>Una petición será aceptada si una
255 ruta principal de acceso se corresponde con un fichero que existe. El ejemplo
256 anterior <code>/test/here.html/more</code> será aceptado si
257 <code>/test/here.html</code> corresponde a un fichero válido.</dd>
259 <dt><code>Default</code></dt><dd>La gestión de las peticiones
260 con información de ruta está determinada por el <a href="../handler.html">controlador</a> responsable de la petición.
261 El controlador principal para para ficheros normales rechaza por defecto
262 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
263 <code>PATH_INFO</code> por defecto.</dd>
266 <p>El objetivo principal de la directiva <code>AcceptPathInfo</code>
267 es permitirte sobreescribir la opción del controlador
268 de aceptar or rechazar <code>PATH_INFO</code>. Este tipo de sobreescritura se necesita,
269 por ejemplo, cuando utilizas un <a href="../filter.html">filtro</a>, tal como
270 <a href="mod_include.html">INCLUDES</a>, para generar contenido
271 basado en <code>PATH_INFO</code>. El controlador principal normalmente rechazaría
272 la petición, de modo que puedes utilizar la siguiente configuración para habilitarla
275 <div class="example"><p><code>
276 <Files "mypaths.shtml"><br />
277 <span class="indent">
278 Options +Includes<br />
279 SetOutputFilter INCLUDES<br />
280 AcceptPathInfo On<br />
287 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
288 <div class="directive-section"><h2><a name="AccessFileName" id="AccessFileName">AccessFileName</a> <a name="accessfilename" id="accessfilename">Directiva</a></h2>
289 <table class="directive">
290 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Nombre del fichero distribuido de configuración</td></tr>
291 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AccessFileName <var>filename</var> [<var>filename</var>] ...</code></td></tr>
292 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AccessFileName .htaccess</code></td></tr>
293 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
294 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
295 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
297 <p>Mientras que procesa una petición el servidor busca
298 el primer fichero de configuración existente dentro de un listado de nombres en
299 cada directorio de la ruta del documento, si los ficheros distribuidos
300 de configuración están <a href="#allowoverride">habilitados para ese
301 directorio</a>. Por ejemplo:</p>
303 <div class="example"><p><code>
307 <p>antes de servir el documento
308 <code>/usr/local/web/index.html</code>, el servidor leerá
309 <code>/.acl</code>, <code>/usr/.acl</code>,
310 <code>/usr/local/.acl</code> and <code>/usr/local/web/.acl</code>
311 para las directivas, salvo que estén deshabilitadas with</p>
313 <div class="example"><p><code>
314 <Directory /><br />
315 <span class="indent">
316 AllowOverride None<br />
321 <h3>Consulte también</h3>
323 <li><code class="directive"><a href="#allowoverride">AllowOverride</a></code></li>
324 <li><a href="../configuring.html">Configuration Files</a></li>
325 <li><a href="../howto/htaccess.html">.htaccess Files</a></li>
328 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
329 <div class="directive-section"><h2><a name="AddDefaultCharset" id="AddDefaultCharset">AddDefaultCharset</a> <a name="adddefaultcharset" id="adddefaultcharset">Directiva</a></h2>
330 <table class="directive">
331 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Default charset parameter to be added when a response
332 content-type is <code>text/plain</code> or <code>text/html</code></td></tr>
333 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AddDefaultCharset On|Off|<var>charset</var></code></td></tr>
334 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AddDefaultCharset Off</code></td></tr>
335 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
336 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
337 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
338 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
340 <p>This directive specifies a default value for the media type
341 charset parameter (the name of a character encoding) to be added
342 to a response if and only if the response's content-type is either
343 <code>text/plain</code> or <code>text/html</code>. This should override
344 any charset specified in the body of the response via a <code>META</code>
345 element, though the exact behavior is often dependent on the user's client
346 configuration. A setting of <code>AddDefaultCharset Off</code>
347 disables this functionality. <code>AddDefaultCharset On</code> enables
348 a default charset of <code>iso-8859-1</code>. Any other value is assumed
349 to be the <var>charset</var> to be used, which should be one of the
350 <a href="http://www.iana.org/assignments/character-sets">IANA registered
351 charset values</a> for use in Internet media types (MIME types).
354 <div class="example"><p><code>
355 AddDefaultCharset utf-8
358 <p><code class="directive">AddDefaultCharset</code> should only be used when all
359 of the text resources to which it applies are known to be in that
360 character encoding and it is too inconvenient to label their charset
361 individually. One such example is to add the charset parameter
362 to resources containing generated content, such as legacy CGI
363 scripts, that might be vulnerable to cross-site scripting attacks
364 due to user-provided data being included in the output. Note, however,
365 that a better solution is to just fix (or delete) those scripts, since
366 setting a default charset does not protect users that have enabled
367 the "auto-detect character encoding" feature on their browser.</p>
369 <h3>Consulte también</h3>
371 <li><code class="directive"><a href="../mod/mod_mime.html#addcharset">AddCharset</a></code></li>
374 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
375 <div class="directive-section"><h2><a name="AllowEncodedSlashes" id="AllowEncodedSlashes">AllowEncodedSlashes</a> <a name="allowencodedslashes" id="allowencodedslashes">Directiva</a></h2>
376 <table class="directive">
377 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determines whether encoded path separators in URLs are allowed to
378 be passed through</td></tr>
379 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AllowEncodedSlashes On|Off</code></td></tr>
380 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AllowEncodedSlashes Off</code></td></tr>
381 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
382 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
383 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
384 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache httpd 2.0.46 and later</td></tr>
386 <p>The <code class="directive">AllowEncodedSlashes</code> directive allows URLs
387 which contain encoded path separators (<code>%2F</code> for <code>/</code>
388 and additionally <code>%5C</code> for <code>\</code> on according systems)
389 to be used. Normally such URLs are refused with a 404 (Not found) error.</p>
391 <p>Turning <code class="directive">AllowEncodedSlashes</code> <code>On</code> is
392 mostly useful when used in conjunction with <code>PATH_INFO</code>.</p>
394 <div class="note"><h3>Note</h3>
395 <p>Allowing encoded slashes does <em>not</em> imply <em>decoding</em>.
396 Occurrences of <code>%2F</code> or <code>%5C</code> (<em>only</em> on
397 according systems) will be left as such in the otherwise decoded URL
401 <h3>Consulte también</h3>
403 <li><code class="directive"><a href="#acceptpathinfo">AcceptPathInfo</a></code></li>
406 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
407 <div class="directive-section"><h2><a name="AllowOverride" id="AllowOverride">AllowOverride</a> <a name="allowoverride" id="allowoverride">Directiva</a></h2>
408 <table class="directive">
409 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Types of directives that are allowed in
410 <code>.htaccess</code> files</td></tr>
411 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AllowOverride All|None|<var>directive-type</var>
412 [<var>directive-type</var>] ...</code></td></tr>
413 <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>
414 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory</td></tr>
415 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
416 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
418 <p>When the server finds an <code>.htaccess</code> file (as
419 specified by <code class="directive"><a href="#accessfilename">AccessFileName</a></code>)
420 it needs to know which directives declared in that file can override
421 earlier configuration directives.</p>
423 <div class="note"><h3>Only available in <Directory> sections</h3>
424 <code class="directive">AllowOverride</code> is valid only in
425 <code class="directive"><a href="#directory"><Directory></a></code>
426 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
427 <code class="directive"><a href="#files"><Files></a></code> sections.
430 <p>When this directive is set to <code>None</code>, then
431 <a href="#accessfilename">.htaccess</a> files are completely ignored.
432 In this case, the server will not even attempt to read
433 <code>.htaccess</code> files in the filesystem.</p>
435 <p>When this directive is set to <code>All</code>, then any
436 directive which has the .htaccess <a href="directive-dict.html#Context">Context</a> is allowed in
437 <code>.htaccess</code> files.</p>
439 <p>The <var>directive-type</var> can be one of the following
440 groupings of directives.</p>
447 Allow use of the authorization directives (<code class="directive"><a href="../mod/mod_authn_dbm.html#authdbmgroupfile">AuthDBMGroupFile</a></code>,
448 <code class="directive"><a href="../mod/mod_authn_dbm.html#authdbmuserfile">AuthDBMUserFile</a></code>,
449 <code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code>,
450 <code class="directive"><a href="../mod/mod_authn_core.html#authname">AuthName</a></code>,
451 <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>
456 Allow use of the directives controlling document types
457 (<code class="directive"><a href="#errordocument">ErrorDocument</a></code>,
458 <code class="directive"><a href="#forcetype">ForceType</a></code>,
459 <code class="directive"><a href="../mod/mod_negotiation.html#languagepriority">LanguagePriority</a></code>,
460 <code class="directive"><a href="#sethandler">SetHandler</a></code>,
461 <code class="directive"><a href="#setinputfilter">SetInputFilter</a></code>,
462 <code class="directive"><a href="#setoutputfilter">SetOutputFilter</a></code>, and
463 <code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code> Add* and Remove* directives),
464 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>),
465 <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
466 <code class="directive"><a href="../mod/mod_actions.html#action">Action</a></code> from
467 <code class="module"><a href="../mod/mod_actions.html">mod_actions</a></code>.
473 Allow use of the directives controlling directory indexing
474 (<code class="directive"><a href="../mod/mod_autoindex.html#adddescription">AddDescription</a></code>,
475 <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>,
476 <code class="directive"><a href="../mod/mod_autoindex.html#addiconbytype">AddIconByType</a></code>,
477 <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>,
483 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>
485 <dt>Options[=<var>Option</var>,...]</dt>
488 Allow use of the directives controlling specific directory
489 features (<code class="directive"><a href="#options">Options</a></code> and
490 <code class="directive"><a href="../mod/mod_include.html#xbithack">XBitHack</a></code>).
491 An equal sign may be given followed by a comma (but no spaces)
492 separated lists of options that may be set using the <code class="directive"><a href="#options">Options</a></code> command.</dd>
497 <div class="example"><p><code>
498 AllowOverride AuthConfig Indexes
501 <p>In the example above all directives that are neither in the group
502 <code>AuthConfig</code> nor <code>Indexes</code> cause an internal
505 <div class="note"><p>For security and performance reasons, do not set
506 <code>AllowOverride</code> to anything other than <code>None</code>
507 in your <code><Directory /></code> block. Instead, find (or
508 create) the <code><Directory></code> block that refers to the
509 directory where you're actually planning to place a
510 <code>.htaccess</code> file.</p>
513 <h3>Consulte también</h3>
515 <li><code class="directive"><a href="#accessfilename">AccessFileName</a></code></li>
516 <li><a href="../configuring.html">Configuration Files</a></li>
517 <li><a href="../howto/htaccess.html">.htaccess Files</a></li>
520 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
521 <div class="directive-section"><h2><a name="AllowOverrideList" id="AllowOverrideList">AllowOverrideList</a> <a name="allowoverridelist" id="allowoverridelist">Directiva</a></h2>
522 <table class="directive">
523 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Individual directives that are allowed in
524 <code>.htaccess</code> files</td></tr>
525 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AllowOverrideList None|<var>directive</var>
526 [<var>directive-type</var>] ...</code></td></tr>
527 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AllowOverrideList None</code></td></tr>
528 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory</td></tr>
529 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
530 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
531 </table><p>The documentation for this directive has
532 not been translated yet. Please have a look at the English
533 version.</p><h3>Consulte también</h3>
535 <li><code class="directive"><a href="#accessfilename">AccessFileName</a></code></li>
536 <li><code class="directive"><a href="#allowoverride">AllowOverride</a></code></li>
537 <li><a href="../configuring.html">Configuration Files</a></li>
538 <li><a href="../howto/htaccess.html">.htaccess Files</a></li>
541 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
542 <div class="directive-section"><h2><a name="AsyncFilter" id="AsyncFilter">AsyncFilter</a> <a name="asyncfilter" id="asyncfilter">Directiva</a></h2>
543 <table class="directive">
544 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Set the minimum filter type eligible for asynchronous handling</td></tr>
545 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AsyncFilter request|connection|network</code></td></tr>
546 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AsyncFilter request</code></td></tr>
547 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
548 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
549 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
550 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Only available from Apache 2.5.0 and later.</td></tr>
551 </table><p>The documentation for this directive has
552 not been translated yet. Please have a look at the English
554 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
555 <div class="directive-section"><h2><a name="CGIMapExtension" id="CGIMapExtension">CGIMapExtension</a> <a name="cgimapextension" id="cgimapextension">Directiva</a></h2>
556 <table class="directive">
557 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Technique for locating the interpreter for CGI
559 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>CGIMapExtension <var>cgi-path</var> <var>.extension</var></code></td></tr>
560 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
561 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
562 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
563 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
564 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>NetWare only</td></tr>
566 <p>This directive is used to control how Apache httpd finds the
567 interpreter used to run CGI scripts. For example, setting
568 <code>CGIMapExtension sys:\foo.nlm .foo</code> will
569 cause all CGI script files with a <code>.foo</code> extension to
570 be passed to the FOO interpreter.</p>
573 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
574 <div class="directive-section"><h2><a name="CGIPassAuth" id="CGIPassAuth">CGIPassAuth</a> <a name="cgipassauth" id="cgipassauth">Directiva</a></h2>
575 <table class="directive">
576 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enables passing HTTP authorization headers to scripts as CGI
578 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>CGIPassAuth On|Off</code></td></tr>
579 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>CGIPassAuth Off</code></td></tr>
580 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
581 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>AuthConfig</td></tr>
582 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
583 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
584 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.4.13 and later</td></tr>
585 </table><p>The documentation for this directive has
586 not been translated yet. Please have a look at the English
588 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
589 <div class="directive-section"><h2><a name="CGIVar" id="CGIVar">CGIVar</a> <a name="cgivar" id="cgivar">Directiva</a></h2>
590 <table class="directive">
591 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Controls how some CGI variables are set</td></tr>
592 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>CGIVar <var>variable</var> <var>rule</var></code></td></tr>
593 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
594 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
595 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
596 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
597 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.5 and later</td></tr>
598 </table><p>The documentation for this directive has
599 not been translated yet. Please have a look at the English
601 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
602 <div class="directive-section"><h2><a name="ContentDigest" id="ContentDigest">ContentDigest</a> <a name="contentdigest" id="contentdigest">Directiva</a></h2>
603 <table class="directive">
604 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enables the generation of <code>Content-MD5</code> HTTP Response
606 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ContentDigest On|Off</code></td></tr>
607 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ContentDigest Off</code></td></tr>
608 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
609 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>Options</td></tr>
610 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
611 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
613 <p>This directive enables the generation of
614 <code>Content-MD5</code> headers as defined in RFC1864
615 respectively RFC2616.</p>
617 <p>MD5 is an algorithm for computing a "message digest"
618 (sometimes called "fingerprint") of arbitrary-length data, with
619 a high degree of confidence that any alterations in the data
620 will be reflected in alterations in the message digest.</p>
622 <p>The <code>Content-MD5</code> header provides an end-to-end
623 message integrity check (MIC) of the entity-body. A proxy or
624 client may check this header for detecting accidental
625 modification of the entity-body in transit. Example header:</p>
627 <div class="example"><p><code>
628 Content-MD5: AuLb7Dp1rqtRtxz2m9kRpA==
631 <p>Note that this can cause performance problems on your server
632 since the message digest is computed on every request (the
633 values are not cached).</p>
635 <p><code>Content-MD5</code> is only sent for documents served
636 by the <code class="module"><a href="../mod/core.html">core</a></code>, and not by any module. For example,
637 SSI documents, output from CGI scripts, and byte range responses
638 do not have this header.</p>
641 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
642 <div class="directive-section"><h2><a name="DefaultRuntimeDir" id="DefaultRuntimeDir">DefaultRuntimeDir</a> <a name="defaultruntimedir" id="defaultruntimedir">Directiva</a></h2>
643 <table class="directive">
644 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Base directory for the server run-time files</td></tr>
645 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>DefaultRuntimeDir <var>directory-path</var></code></td></tr>
646 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>DefaultRuntimeDir DEFAULT_REL_RUNTIMEDIR (logs/)</code></td></tr>
647 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
648 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
649 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
650 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache 2.4.2 and later</td></tr>
651 </table><p>The documentation for this directive has
652 not been translated yet. Please have a look at the English
653 version.</p><h3>Consulte también</h3>
655 <li><a href="../misc/security_tips.html#serverroot">the
656 security tips</a> for information on how to properly set
657 permissions on the <code class="directive">ServerRoot</code></li>
660 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
661 <div class="directive-section"><h2><a name="DefaultType" id="DefaultType">DefaultType</a> <a name="defaulttype" id="defaulttype">Directiva</a></h2>
662 <table class="directive">
663 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>This directive has no effect other than to emit warnings
664 if the value is not <code>none</code>. In prior versions, DefaultType
665 would specify a default media type to assign to response content for
666 which no other media type configuration could be found.
668 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>DefaultType <var>media-type|none</var></code></td></tr>
669 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>DefaultType none</code></td></tr>
670 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
671 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
672 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
673 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
674 <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>
676 <p>This directive has been disabled. For backwards compatibility
677 of configuration files, it may be specified with the value
678 <code>none</code>, meaning no default media type. For example:</p>
680 <div class="example"><p><code>
684 <p><code>DefaultType None</code> is only available in
685 httpd-2.2.7 and later.</p>
687 <p>Use the mime.types configuration file and the
688 <code class="directive"><a href="../mod/mod_mime.html#addtype">AddType</a></code> to configure media
689 type assignments via file extensions, or the
690 <code class="directive"><a href="#forcetype">ForceType</a></code> directive to configure
691 the media type for specific resources. Otherwise, the server will
692 send the response without a Content-Type header field and the
693 recipient may attempt to guess the media type.</p>
696 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
697 <div class="directive-section"><h2><a name="Define" id="Define">Define</a> <a name="define" id="define">Directiva</a></h2>
698 <table class="directive">
699 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Define the existence of a variable</td></tr>
700 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Define <var>parameter-name</var></code></td></tr>
701 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
702 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
703 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
705 <p>Equivalent to passing the <code>-D</code> argument to <code class="program"><a href="../programs/httpd.html">httpd</a></code>.</p>
706 <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
707 <code>-D</code> arguments in any startup scripts.</p>
710 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
711 <div class="directive-section"><h2><a name="Directory" id="Directory"><Directory></a> <a name="directory" id="directory">Directiva</a></h2>
712 <table class="directive">
713 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enclose a group of directives that apply only to the
714 named file-system directory, sub-directories, and their contents.</td></tr>
715 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><Directory <var>directory-path</var>>
716 ... </Directory></code></td></tr>
717 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
718 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
719 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
721 <p><code class="directive"><Directory></code> and
722 <code></Directory></code> are used to enclose a group of
723 directives that will apply only to the named directory,
724 sub-directories of that directory, and the files within the respective
725 directories. Any directive that is allowed
726 in a directory context may be used. <var>Directory-path</var> is
727 either the full path to a directory, or a wild-card string using
728 Unix shell-style matching. In a wild-card string, <code>?</code> matches
729 any single character, and <code>*</code> matches any sequences of
730 characters. You may also use <code>[]</code> character ranges. None
731 of the wildcards match a `/' character, so <code><Directory
732 /*/public_html></code> will not match
733 <code>/home/user/public_html</code>, but <code><Directory
734 /home/*/public_html></code> will match. Example:</p>
736 <div class="example"><p><code>
737 <Directory /usr/local/httpd/htdocs><br />
738 <span class="indent">
739 Options Indexes FollowSymLinks<br />
745 <p>Be careful with the <var>directory-path</var> arguments:
746 They have to literally match the filesystem path which Apache httpd uses
747 to access the files. Directives applied to a particular
748 <code><Directory></code> will not apply to files accessed from
749 that same directory via a different path, such as via different symbolic
753 <p><a class="glossarylink" href="../glossary.html#regex" title="ver glosario">Regular
754 expressions</a> can also be used, with the addition of the
755 <code>~</code> character. For example:</p>
757 <div class="example"><p><code>
758 <Directory ~ "^/www/.*/[0-9]{3}">
761 <p>would match directories in <code>/www/</code> that consisted of
764 <p>If multiple (non-regular expression) <code class="directive"><Directory></code> sections
765 match the directory (or one of its parents) containing a document,
766 then the directives are applied in the order of shortest match
767 first, interspersed with the directives from the <a href="#accessfilename">.htaccess</a> files. For example,
770 <div class="example"><p><code>
771 <Directory /><br />
772 <span class="indent">
773 AllowOverride None<br />
775 </Directory><br />
777 <Directory /home/><br />
778 <span class="indent">
779 AllowOverride FileInfo<br />
784 <p>for access to the document <code>/home/web/dir/doc.html</code>
788 <li>Apply directive <code>AllowOverride None</code>
789 (disabling <code>.htaccess</code> files).</li>
791 <li>Apply directive <code>AllowOverride FileInfo</code> (for
792 directory <code>/home</code>).</li>
794 <li>Apply any <code>FileInfo</code> directives in
795 <code>/home/.htaccess</code>, <code>/home/web/.htaccess</code> and
796 <code>/home/web/dir/.htaccess</code> in that order.</li>
799 <p>Regular expressions are not considered until after all of the
800 normal sections have been applied. Then all of the regular
801 expressions are tested in the order they appeared in the
802 configuration file. For example, with</p>
804 <div class="example"><p><code>
805 <Directory ~ abc$><br />
806 <span class="indent">
807 # ... directives here ...<br />
812 <p>the regular expression section won't be considered until after
813 all normal <code class="directive"><Directory></code>s and
814 <code>.htaccess</code> files have been applied. Then the regular
815 expression will match on <code>/home/abc/public_html/abc</code> and
816 the corresponding <code class="directive"><Directory></code> will
819 <p><strong>Note that the default access for
820 <code><Directory /></code> is <code>Allow from All</code>.
821 This means that Apache httpd will serve any file mapped from an URL. It is
822 recommended that you change this with a block such
825 <div class="example"><p><code>
826 <Directory /><br />
827 <span class="indent">
828 Order Deny,Allow<br />
834 <p><strong>and then override this for directories you
835 <em>want</em> accessible. See the <a href="../misc/security_tips.html">Security Tips</a> page for more
836 details.</strong></p>
838 <p>The directory sections occur in the <code>httpd.conf</code> file.
839 <code class="directive"><Directory></code> directives
840 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>
842 <h3>Consulte también</h3>
844 <li><a href="../sections.html">How <Directory>,
845 <Location> and <Files> sections work</a> for an
846 explanation of how these different sections are combined when a
847 request is received</li>
850 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
851 <div class="directive-section"><h2><a name="DirectoryMatch" id="DirectoryMatch"><DirectoryMatch></a> <a name="directorymatch" id="directorymatch">Directiva</a></h2>
852 <table class="directive">
853 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enclose directives that apply to
854 the contents of file-system directories matching a regular expression.</td></tr>
855 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><DirectoryMatch <var>regex</var>>
856 ... </DirectoryMatch></code></td></tr>
857 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
858 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
859 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
861 <p><code class="directive"><DirectoryMatch></code> and
862 <code></DirectoryMatch></code> are used to enclose a group
863 of directives which will apply only to the named directory (and the files within),
864 the same as <code class="directive"><a href="#directory"><Directory></a></code>.
865 However, it takes as an argument a
866 <a class="glossarylink" href="../glossary.html#regex" title="ver glosario">regular expression</a>. For example:</p>
868 <div class="example"><p><code>
869 <DirectoryMatch "^/www/(.+/)?[0-9]{3}">
872 <p>would match directories in <code>/www/</code> that consisted of three
875 <div class="note"><h3>Compatability</h3>
876 Prior to 2.3.9, this directive implicitly applied to sub-directories
877 (like <code class="directive"><a href="#directory"><Directory></a></code>) and
878 could not match the end of line symbol ($). In 2.3.9 and later,
879 only directories that match the expression are affected by the enclosed
883 <div class="note"><h3>Trailing Slash</h3>
884 This directive applies to requests for directories that may or may
885 not end in a trailing slash, so expressions that are anchored to the
886 end of line ($) must be written with care.
889 <h3>Consulte también</h3>
891 <li><code class="directive"><a href="#directory"><Directory></a></code> for
892 a description of how regular expressions are mixed in with normal
893 <code class="directive"><Directory></code>s</li>
894 <li><a href="../sections.html">How <Directory>, <Location> and
895 <Files> sections work</a> for an explanation of how these different
896 sections are combined when a request is received</li>
899 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
900 <div class="directive-section"><h2><a name="DocumentRoot" id="DocumentRoot">DocumentRoot</a> <a name="documentroot" id="documentroot">Directiva</a></h2>
901 <table class="directive">
902 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Directory that forms the main document tree visible
903 from the web</td></tr>
904 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>DocumentRoot <var>directory-path</var></code></td></tr>
905 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>DocumentRoot /usr/local/apache/htdocs</code></td></tr>
906 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
907 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
908 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
910 <p>This directive sets the directory from which <code class="program"><a href="../programs/httpd.html">httpd</a></code>
911 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
912 path from the requested URL to the document root to make the
913 path to the document. Example:</p>
915 <div class="example"><p><code>
916 DocumentRoot /usr/web
920 <code>http://www.my.host.com/index.html</code> refers to
921 <code>/usr/web/index.html</code>. If the <var>directory-path</var> is
922 not absolute then it is assumed to be relative to the <code class="directive"><a href="#serverroot">ServerRoot</a></code>.</p>
924 <p>The <code class="directive">DocumentRoot</code> should be specified without
925 a trailing slash.</p>
927 <h3>Consulte también</h3>
929 <li><a href="../urlmapping.html#documentroot">Mapping URLs to Filesystem
933 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
934 <div class="directive-section"><h2><a name="Else" id="Else"><Else></a> <a name="else" id="else">Directiva</a></h2>
935 <table class="directive">
936 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply only if the condition of a
937 previous <code class="directive"><a href="#if"><If></a></code> or
938 <code class="directive"><a href="#elseif"><ElseIf></a></code> section is not
939 satisfied by a request at runtime</td></tr>
940 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><Else> ... </Else></code></td></tr>
941 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
942 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
943 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
944 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
945 </table><p>The documentation for this directive has
946 not been translated yet. Please have a look at the English
947 version.</p><h3>Consulte también</h3>
949 <li><code class="directive"><a href="#if"><If></a></code></li>
950 <li><code class="directive"><a href="#elseif"><ElseIf></a></code></li>
951 <li><a href="../sections.html">How <Directory>, <Location>,
952 <Files> sections work</a> for an explanation of how these
953 different sections are combined when a request is received.
954 <code class="directive"><If></code>,
955 <code class="directive"><ElseIf></code>, and
956 <code class="directive"><Else></code> are applied last.</li>
959 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
960 <div class="directive-section"><h2><a name="ElseIf" id="ElseIf"><ElseIf></a> <a name="elseif" id="elseif">Directiva</a></h2>
961 <table class="directive">
962 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply only if a condition is satisfied
963 by a request at runtime while the condition of a previous
964 <code class="directive"><a href="#if"><If></a></code> or
965 <code class="directive"><ElseIf></code> section is not
967 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><ElseIf <var>expression</var>> ... </ElseIf></code></td></tr>
968 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
969 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
970 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
971 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
972 </table><p>The documentation for this directive has
973 not been translated yet. Please have a look at the English
974 version.</p><h3>Consulte también</h3>
976 <li><a href="../expr.html">Expressions in Apache HTTP Server</a>,
977 for a complete reference and more examples.</li>
978 <li><code class="directive"><a href="#if"><If></a></code></li>
979 <li><code class="directive"><a href="#else"><Else></a></code></li>
980 <li><a href="../sections.html">How <Directory>, <Location>,
981 <Files> sections work</a> for an explanation of how these
982 different sections are combined when a request is received.
983 <code class="directive"><If></code>,
984 <code class="directive"><ElseIf></code>, and
985 <code class="directive"><Else></code> are applied last.</li>
988 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
989 <div class="directive-section"><h2><a name="EnableMMAP" id="EnableMMAP">EnableMMAP</a> <a name="enablemmap" id="enablemmap">Directiva</a></h2>
990 <table class="directive">
991 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Use memory-mapping to read files during delivery</td></tr>
992 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>EnableMMAP On|Off</code></td></tr>
993 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>EnableMMAP On</code></td></tr>
994 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
995 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
996 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
997 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
999 <p>This directive controls whether the <code class="program"><a href="../programs/httpd.html">httpd</a></code> may use
1000 memory-mapping if it needs to read the contents of a file during
1001 delivery. By default, when the handling of a request requires
1002 access to the data within a file -- for example, when delivering a
1003 server-parsed file using <code class="module"><a href="../mod/mod_include.html">mod_include</a></code> -- Apache httpd
1004 memory-maps the file if the OS supports it.</p>
1006 <p>This memory-mapping sometimes yields a performance improvement.
1007 But in some environments, it is better to disable the memory-mapping
1008 to prevent operational problems:</p>
1011 <li>On some multiprocessor systems, memory-mapping can reduce the
1012 performance of the <code class="program"><a href="../programs/httpd.html">httpd</a></code>.</li>
1013 <li>Deleting or truncating a file while <code class="program"><a href="../programs/httpd.html">httpd</a></code>
1014 has it memory-mapped can cause <code class="program"><a href="../programs/httpd.html">httpd</a></code> to
1015 crash with a segmentation fault.
1019 <p>For server configurations that are vulnerable to these problems,
1020 you should disable memory-mapping of delivered files by specifying:</p>
1022 <div class="example"><p><code>
1026 <p>For NFS mounted files, this feature may be disabled explicitly for
1027 the offending files by specifying:</p>
1029 <div class="example"><p><code>
1030 <Directory "/path-to-nfs-files">
1031 <span class="indent">
1038 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1039 <div class="directive-section"><h2><a name="EnableSendfile" id="EnableSendfile">EnableSendfile</a> <a name="enablesendfile" id="enablesendfile">Directiva</a></h2>
1040 <table class="directive">
1041 <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>
1042 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>EnableSendfile On|Off</code></td></tr>
1043 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>EnableSendfile Off</code></td></tr>
1044 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1045 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
1046 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1047 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1048 <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
1049 version 2.3.9.</td></tr>
1051 <p>This directive controls whether <code class="program"><a href="../programs/httpd.html">httpd</a></code> may use the
1052 sendfile support from the kernel to transmit file contents to the client.
1053 By default, when the handling of a request requires no access
1054 to the data within a file -- for example, when delivering a
1055 static file -- Apache httpd uses sendfile to deliver the file contents
1056 without ever reading the file if the OS supports it.</p>
1058 <p>This sendfile mechanism avoids separate read and send operations,
1059 and buffer allocations. But on some platforms or within some
1060 filesystems, it is better to disable this feature to avoid
1061 operational problems:</p>
1064 <li>Some platforms may have broken sendfile support that the build
1065 system did not detect, especially if the binaries were built on
1066 another box and moved to such a machine with broken sendfile
1068 <li>On Linux the use of sendfile triggers TCP-checksum
1069 offloading bugs on certain networking cards when using IPv6.</li>
1070 <li>On Linux on Itanium, sendfile may be unable to handle files
1071 over 2GB in size.</li>
1072 <li>With a network-mounted <code class="directive"><a href="#documentroot">DocumentRoot</a></code> (e.g., NFS, SMB, CIFS, FUSE),
1073 the kernel may be unable to serve the network file through
1077 <p>For server configurations that are not vulnerable to these problems,
1078 you may enable this feature by specifying:</p>
1080 <div class="example"><p><code>
1084 <p>For network mounted files, this feature may be disabled explicitly
1085 for the offending files by specifying:</p>
1087 <div class="example"><p><code>
1088 <Directory "/path-to-nfs-files">
1089 <span class="indent">
1094 <p>Please note that the per-directory and .htaccess configuration
1095 of <code class="directive">EnableSendfile</code> is not supported by
1096 <code class="module"><a href="../mod/mod_cache_disk.html">mod_cache_disk</a></code>.
1097 Only global definition of <code class="directive">EnableSendfile</code>
1098 is taken into account by the module.
1102 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1103 <div class="directive-section"><h2><a name="Error" id="Error">Error</a> <a name="error" id="error">Directiva</a></h2>
1104 <table class="directive">
1105 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Abort configuration parsing with a custom error message</td></tr>
1106 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Error <var>message</var></code></td></tr>
1107 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1108 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1109 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1110 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>2.3.9 and later</td></tr>
1112 <p>If an error can be detected within the configuration, this
1113 directive can be used to generate a custom error message, and halt
1114 configuration parsing. The typical use is for reporting required
1115 modules which are missing from the configuration.</p>
1117 <div class="example"><h3>Example</h3><p><code>
1118 # ensure that mod_include is loaded<br />
1119 <IfModule !include_module><br />
1120 Error mod_include is required by mod_foo. Load it with LoadModule.<br />
1121 </IfModule><br />
1123 # ensure that exactly one of SSL,NOSSL is defined<br />
1124 <IfDefine SSL><br />
1125 <IfDefine NOSSL><br />
1126 Error Both SSL and NOSSL are defined. Define only one of them.<br />
1127 </IfDefine><br />
1128 </IfDefine><br />
1129 <IfDefine !SSL><br />
1130 <IfDefine !NOSSL><br />
1131 Error Either SSL or NOSSL must be defined.<br />
1132 </IfDefine><br />
1133 </IfDefine><br />
1138 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1139 <div class="directive-section"><h2><a name="ErrorDocument" id="ErrorDocument">ErrorDocument</a> <a name="errordocument" id="errordocument">Directiva</a></h2>
1140 <table class="directive">
1141 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>What the server will return to the client
1142 in case of an error</td></tr>
1143 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ErrorDocument <var>error-code</var> <var>document</var></code></td></tr>
1144 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1145 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
1146 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1147 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1149 <p>In the event of a problem or error, Apache httpd can be configured
1150 to do one of four things,</p>
1153 <li>output a simple hardcoded error message</li>
1155 <li>output a customized message</li>
1157 <li>redirect to a local <var>URL-path</var> to handle the
1160 <li>redirect to an external <var>URL</var> to handle the
1164 <p>The first option is the default, while options 2-4 are
1165 configured using the <code class="directive">ErrorDocument</code>
1166 directive, which is followed by the HTTP response code and a URL
1167 or a message. Apache httpd will sometimes offer additional information
1168 regarding the problem/error.</p>
1170 <p>URLs can begin with a slash (/) for local web-paths (relative
1171 to the <code class="directive"><a href="#documentroot">DocumentRoot</a></code>), or be a
1172 full URL which the client can resolve. Alternatively, a message
1173 can be provided to be displayed by the browser. Examples:</p>
1175 <div class="example"><p><code>
1176 ErrorDocument 500 http://foo.example.com/cgi-bin/tester<br />
1177 ErrorDocument 404 /cgi-bin/bad_urls.pl<br />
1178 ErrorDocument 401 /subscription_info.html<br />
1179 ErrorDocument 403 "Sorry can't allow you access today"
1182 <p>Additionally, the special value <code>default</code> can be used
1183 to specify Apache httpd's simple hardcoded message. While not required
1184 under normal circumstances, <code>default</code> will restore
1185 Apache httpd's simple hardcoded message for configurations that would
1186 otherwise inherit an existing <code class="directive">ErrorDocument</code>.</p>
1188 <div class="example"><p><code>
1189 ErrorDocument 404 /cgi-bin/bad_urls.pl<br /><br />
1190 <Directory /web/docs><br />
1191 <span class="indent">
1192 ErrorDocument 404 default<br />
1197 <p>Note that when you specify an <code class="directive">ErrorDocument</code>
1198 that points to a remote URL (ie. anything with a method such as
1199 <code>http</code> in front of it), Apache HTTP Server will send a redirect to the
1200 client to tell it where to find the document, even if the
1201 document ends up being on the same server. This has several
1202 implications, the most important being that the client will not
1203 receive the original error status code, but instead will
1204 receive a redirect status code. This in turn can confuse web
1205 robots and other clients which try to determine if a URL is
1206 valid using the status code. In addition, if you use a remote
1207 URL in an <code>ErrorDocument 401</code>, the client will not
1208 know to prompt the user for a password since it will not
1209 receive the 401 status code. Therefore, <strong>if you use an
1210 <code>ErrorDocument 401</code> directive then it must refer to a local
1211 document.</strong></p>
1213 <p>Microsoft Internet Explorer (MSIE) will by default ignore
1214 server-generated error messages when they are "too small" and substitute
1215 its own "friendly" error messages. The size threshold varies depending on
1216 the type of error, but in general, if you make your error document
1217 greater than 512 bytes, then MSIE will show the server-generated
1218 error rather than masking it. More information is available in
1219 Microsoft Knowledge Base article <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294807">Q294807</a>.</p>
1221 <p>Although most error messages can be overriden, there are certain
1222 circumstances where the internal messages are used regardless of the
1223 setting of <code class="directive"><a href="#errordocument">ErrorDocument</a></code>. In
1224 particular, if a malformed request is detected, normal request processing
1225 will be immediately halted and the internal error message returned.
1226 This is necessary to guard against security problems caused by
1229 <p>If you are using mod_proxy, you may wish to enable
1230 <code class="directive"><a href="../mod/mod_proxy.html#proxyerroroverride">ProxyErrorOverride</a></code> so that you can provide
1231 custom error messages on behalf of your Origin servers. If you don't enable ProxyErrorOverride,
1232 Apache httpd will not generate custom error documents for proxied content.</p>
1234 <h3>Consulte también</h3>
1236 <li><a href="../custom-error.html">documentation of
1237 customizable responses</a></li>
1240 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1241 <div class="directive-section"><h2><a name="ErrorLog" id="ErrorLog">ErrorLog</a> <a name="errorlog" id="errorlog">Directiva</a></h2>
1242 <table class="directive">
1243 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Location where the server will log errors</td></tr>
1244 <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>
1245 <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>
1246 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
1247 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1248 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1250 <p>The <code class="directive">ErrorLog</code> directive sets the name of
1251 the file to which the server will log any errors it encounters. If
1252 the <var>file-path</var> is not absolute then it is assumed to be
1253 relative to the <code class="directive"><a href="#serverroot">ServerRoot</a></code>.</p>
1255 <div class="example"><h3>Example</h3><p><code>
1256 ErrorLog /var/log/httpd/error_log
1259 <p>If the <var>file-path</var>
1260 begins with a pipe character "<code>|</code>" then it is assumed to be a
1261 command to spawn to handle the error log.</p>
1263 <div class="example"><h3>Example</h3><p><code>
1264 ErrorLog "|/usr/local/bin/httpd_errors"
1267 <p>See the notes on <a href="../logs.html#piped">piped logs</a> for
1268 more information.</p>
1270 <p>Using <code>syslog</code> instead of a filename enables logging
1271 via syslogd(8) if the system supports it. The default is to use
1272 syslog facility <code>local7</code>, but you can override this by
1273 using the <code>syslog:<var>facility</var></code> syntax where
1274 <var>facility</var> can be one of the names usually documented in
1275 syslog(1). The facility is effectively global, and if it is changed
1276 in individual virtual hosts, the final facility specified affects the
1279 <div class="example"><h3>Example</h3><p><code>
1280 ErrorLog syslog:user
1283 <p>SECURITY: See the <a href="../misc/security_tips.html#serverroot">security tips</a>
1284 document for details on why your security could be compromised
1285 if the directory where log files are stored is writable by
1286 anyone other than the user that starts the server.</p>
1287 <div class="warning"><h3>Note</h3>
1288 <p>When entering a file path on non-Unix platforms, care should be taken
1289 to make sure that only forward slashed are used even though the platform
1290 may allow the use of back slashes. In general it is a good idea to always
1291 use forward slashes throughout the configuration files.</p>
1294 <h3>Consulte también</h3>
1296 <li><code class="directive"><a href="#loglevel">LogLevel</a></code></li>
1297 <li><a href="../logs.html">Apache HTTP Server Log Files</a></li>
1300 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1301 <div class="directive-section"><h2><a name="ErrorLogFormat" id="ErrorLogFormat">ErrorLogFormat</a> <a name="errorlogformat" id="errorlogformat">Directiva</a></h2>
1302 <table class="directive">
1303 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Format specification for error log entries</td></tr>
1304 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code> ErrorLog [connection|request] <var>format</var></code></td></tr>
1305 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
1306 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1307 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1308 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache httpd 2.3.9 and later</td></tr>
1310 <p><code class="directive">ErrorLogFormat</code> allows to specify what
1311 supplementary information is logged in the error log in addition to the
1312 actual log message.</p>
1314 <div class="example"><h3>Simple example</h3><p><code>
1315 ErrorLogFormat "[%t] [%l] [pid %P] %F: %E: [client %a] %M"
1318 <p>Specifying <code>connection</code> or <code>request</code> as first
1319 paramter allows to specify additional formats, causing additional
1320 information to be logged when the first message is logged for a specific
1321 connection or request, respectivly. This additional information is only
1322 logged once per connection/request. If a connection or request is processed
1323 without causing any log message, the additional information is not logged
1326 <p>It can happen that some format string items do not produce output. For
1327 example, the Referer header is only present if the log message is
1328 associated to a request and the log message happens at a time when the
1329 Referer header has already been read from the client. If no output is
1330 produced, the default behaviour is to delete everything from the preceeding
1331 space character to the next space character. This means the log line is
1332 implicitly divided into fields on non-whitespace to whitespace transitions.
1333 If a format string item does not produce output, the whole field is
1334 ommitted. For example, if the remote address <code>%a</code> in the log
1335 format <code>[%t] [%l] [%a] %M </code> is not available, the surrounding
1336 brackets are not logged either. Space characters can be escaped with a
1337 backslash to prevent them from delimiting a field. The combination '% '
1338 (percent space) is a zero-witdh field delimiter that does not produce any
1341 <p>The above behaviour can be changed by adding modifiers to the format
1342 string item. A <code>-</code> (minus) modifier causes a minus to be logged if the
1343 respective item does not produce any output. In once-per-connection/request
1344 formats, it is also possible to use the <code>+</code> (plus) modifier. If an
1345 item with the plus modifier does not produce any output, the whole line is
1348 <p>A number as modifier can be used to assign a log severity level to a
1349 format item. The item will only be logged if the severity of the log
1350 message is not higher than the specified log severity level. The number can
1351 range from 1 (alert) over 4 (warn) and 7 (debug) to 15 (trace8).</p>
1353 <p>Some format string items accept additional parameters in braces.</p>
1355 <table class="bordered"><tr class="header"><th>Format String</th> <th>Description</th></tr>
1356 <tr><td><code>%%</code></td>
1357 <td>The percent sign</td></tr>
1358 <tr class="odd"><td><code>%...a</code></td>
1359 <td>Remote IP-address and port</td></tr>
1360 <tr><td><code>%...A</code></td>
1361 <td>Local IP-address and port</td></tr>
1362 <tr class="odd"><td><code>%...{name}e</code></td>
1363 <td>Request environment variable <code>name</code></td></tr>
1364 <tr><td><code>%...E</code></td>
1365 <td>APR/OS error status code and string</td></tr>
1366 <tr class="odd"><td><code>%...F</code></td>
1367 <td>Source file name and line number of the log call</td></tr>
1368 <tr><td><code>%...{name}i</code></td>
1369 <td>Request header <code>name</code></td></tr>
1370 <tr class="odd"><td><code>%...k</code></td>
1371 <td>Number of keep-alive requests on this connection</td></tr>
1372 <tr><td><code>%...l</code></td>
1373 <td>Loglevel of the message</td></tr>
1374 <tr class="odd"><td><code>%...L</code></td>
1375 <td>Log ID of the request</td></tr>
1376 <tr><td><code>%...{c}L</code></td>
1377 <td>Log ID of the connection</td></tr>
1378 <tr class="odd"><td><code>%...{C}L</code></td>
1379 <td>Log ID of the connection if used in connection scope, empty otherwise</td></tr>
1380 <tr><td><code>%...m</code></td>
1381 <td>Name of the module logging the message</td></tr>
1382 <tr class="odd"><td><code>%M</code></td>
1383 <td>The actual log message</td></tr>
1384 <tr><td><code>%...{name}n</code></td>
1385 <td>Request note <code>name</code></td></tr>
1386 <tr class="odd"><td><code>%...P</code></td>
1387 <td>Process ID of current process</td></tr>
1388 <tr><td><code>%...T</code></td>
1389 <td>Thread ID of current thread</td></tr>
1390 <tr class="odd"><td><code>%...t</code></td>
1391 <td>The current time</td></tr>
1392 <tr><td><code>%...{u}t</code></td>
1393 <td>The current time including micro-seconds</td></tr>
1394 <tr class="odd"><td><code>%...{cu}t</code></td>
1395 <td>The current time in compact ISO 8601 format, including
1396 micro-seconds</td></tr>
1397 <tr><td><code>%...v</code></td>
1398 <td>The canonical <code class="directive"><a href="#servername">ServerName</a></code>
1399 of the current server.</td></tr>
1400 <tr class="odd"><td><code>%...V</code></td>
1401 <td>The server name of the server serving the request according to the
1402 <code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code>
1404 <tr><td><code>\ </code> (backslash space)</td>
1405 <td>Non-field delimiting space</td></tr>
1406 <tr class="odd"><td><code>% </code> (percent space)</td>
1407 <td>Field delimiter (no output)</td></tr>
1410 <p>The log ID format <code>%L</code> produces a unique id for a connection
1411 or request. This can be used to correlate which log lines belong to the
1412 same connection or request, which request happens on which connection.
1413 A <code>%L</code> format string is also available in
1414 <code class="module"><a href="../mod/mod_log_config.html">mod_log_config</a></code>, to allow to correlate access log entries
1415 with error log lines. If <code class="module"><a href="../mod/mod_unique_id.html">mod_unique_id</a></code> is loaded, its
1416 unique id will be used as log ID for requests.</p>
1418 <div class="example"><h3>Example (somewhat similar to default format)</h3><p><code>
1419 ErrorLogFormat "[%{u}t] [%-m:%l] [pid %P] %7F: %E: [client\ %a]
1420 %M% ,\ referer\ %{Referer}i"
1423 <div class="example"><h3>Example (similar to the 2.2.x format)</h3><p><code>
1424 ErrorLogFormat "[%t] [%l] %7F: %E: [client\ %a]
1425 %M% ,\ referer\ %{Referer}i"
1428 <div class="example"><h3>Advanced example with request/connection log IDs</h3><p><code>
1429 ErrorLogFormat "[%{uc}t] [%-m:%-l] [R:%L] [C:%{C}L] %7F: %E: %M"<br />
1430 ErrorLogFormat request "[%{uc}t] [R:%L] Request %k on C:%{c}L pid:%P tid:%T"<br />
1431 ErrorLogFormat request "[%{uc}t] [R:%L] UA:'%+{User-Agent}i'"<br />
1432 ErrorLogFormat request "[%{uc}t] [R:%L] Referer:'%+{Referer}i'"<br />
1433 ErrorLogFormat connection "[%{uc}t] [C:%{c}L] local\ %a remote\ %A"<br />
1437 <h3>Consulte también</h3>
1439 <li><code class="directive"><a href="#errorlog">ErrorLog</a></code></li>
1440 <li><code class="directive"><a href="#loglevel">LogLevel</a></code></li>
1441 <li><a href="../logs.html">Apache HTTP Server Log Files</a></li>
1444 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1445 <div class="directive-section"><h2><a name="ExtendedStatus" id="ExtendedStatus">ExtendedStatus</a> <a name="extendedstatus" id="extendedstatus">Directiva</a></h2>
1446 <table class="directive">
1447 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Keep track of extended status information for each
1449 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ExtendedStatus On|Off</code></td></tr>
1450 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ExtendedStatus Off[*]</code></td></tr>
1451 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
1452 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1453 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1455 <p>This option tracks additional data per worker about the
1456 currently executing request, and a utilization summary; you
1457 can see these variables during runtime by configuring
1458 <code class="module"><a href="../mod/mod_status.html">mod_status</a></code>. Note that other modules may
1459 rely on this scoreboard.</p>
1461 <p>This setting applies to the entire server, and cannot be
1462 enabled or disabled on a virtualhost-by-virtualhost basis.
1463 The collection of extended status information can slow down
1464 the server. Also note that this setting cannot be changed
1465 during a graceful restart.</p>
1468 <p>Note that loading <code class="module"><a href="../mod/mod_status.html">mod_status</a></code> will change
1469 the default behavior to ExtendedStatus On, while other
1470 third party modules may do the same. Such modules rely on
1471 collecting detailed information about the state of all workers.
1472 The default is changed by <code class="module"><a href="../mod/mod_status.html">mod_status</a></code> beginning
1473 with version 2.3.6; the previous default was always Off.</p>
1478 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1479 <div class="directive-section"><h2><a name="FileETag" id="FileETag">FileETag</a> <a name="fileetag" id="fileetag">Directiva</a></h2>
1480 <table class="directive">
1481 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>File attributes used to create the ETag
1482 HTTP response header for static files</td></tr>
1483 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>FileETag <var>component</var> ...</code></td></tr>
1484 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>FileETag INode MTime Size</code></td></tr>
1485 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1486 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
1487 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1488 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1491 The <code class="directive">FileETag</code> directive configures the file
1492 attributes that are used to create the <code>ETag</code> (entity
1493 tag) response header field when the document is based on a static file.
1494 (The <code>ETag</code> value is used in cache management to save
1495 network bandwidth.) The
1496 <code class="directive">FileETag</code> directive allows you to choose
1497 which of these -- if any -- should be used. The recognized keywords are:
1501 <dt><strong>INode</strong></dt>
1502 <dd>The file's i-node number will be included in the calculation</dd>
1503 <dt><strong>MTime</strong></dt>
1504 <dd>The date and time the file was last modified will be included</dd>
1505 <dt><strong>Size</strong></dt>
1506 <dd>The number of bytes in the file will be included</dd>
1507 <dt><strong>All</strong></dt>
1508 <dd>All available fields will be used. This is equivalent to:
1509 <div class="example"><p><code>FileETag INode MTime Size</code></p></div></dd>
1510 <dt><strong>None</strong></dt>
1511 <dd>If a document is file-based, no <code>ETag</code> field will be
1512 included in the response</dd>
1515 <p>The <code>INode</code>, <code>MTime</code>, and <code>Size</code>
1516 keywords may be prefixed with either <code>+</code> or <code>-</code>,
1517 which allow changes to be made to the default setting inherited
1518 from a broader scope. Any keyword appearing without such a prefix
1519 immediately and completely cancels the inherited setting.</p>
1521 <p>If a directory's configuration includes
1522 <code>FileETag INode MTime Size</code>, and a
1523 subdirectory's includes <code>FileETag -INode</code>,
1524 the setting for that subdirectory (which will be inherited by
1525 any sub-subdirectories that don't override it) will be equivalent to
1526 <code>FileETag MTime Size</code>.</p>
1527 <div class="warning"><h3>Warning</h3>
1528 Do not change the default for directories or locations that have WebDAV
1529 enabled and use <code class="module"><a href="../mod/mod_dav_fs.html">mod_dav_fs</a></code> as a storage provider.
1530 <code class="module"><a href="../mod/mod_dav_fs.html">mod_dav_fs</a></code> uses <code>INode MTime Size</code>
1531 as a fixed format for <code>ETag</code> comparisons on conditional requests.
1532 These conditional requests will break if the <code>ETag</code> format is
1533 changed via <code class="directive">FileETag</code>.
1535 <div class="note"><h3>Server Side Includes</h3>
1536 An ETag is not generated for responses parsed by <code class="module"><a href="../mod/mod_include.html">mod_include</a></code>,
1537 since the response entity can change without a change of the INode, MTime, or Size
1538 of the static file with embedded SSI directives.
1543 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1544 <div class="directive-section"><h2><a name="Files" id="Files"><Files></a> <a name="files" id="files">Directiva</a></h2>
1545 <table class="directive">
1546 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply to matched
1548 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><Files <var>filename</var>> ... </Files></code></td></tr>
1549 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1550 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
1551 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1552 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1554 <p>The <code class="directive"><Files></code> directive
1555 limits the scope of the enclosed directives by filename. It is comparable
1556 to the <code class="directive"><a href="#directory"><Directory></a></code>
1557 and <code class="directive"><a href="#location"><Location></a></code>
1558 directives. It should be matched with a <code></Files></code>
1559 directive. The directives given within this section will be applied to
1560 any object with a basename (last component of filename) matching the
1561 specified filename. <code class="directive"><Files></code>
1562 sections are processed in the order they appear in the
1563 configuration file, after the <code class="directive"><a href="#directory"><Directory></a></code> sections and
1564 <code>.htaccess</code> files are read, but before <code class="directive"><a href="#location"><Location></a></code> sections. Note
1565 that <code class="directive"><Files></code> can be nested
1566 inside <code class="directive"><a href="#directory"><Directory></a></code> sections to restrict the
1567 portion of the filesystem they apply to.</p>
1569 <p>The <var>filename</var> argument should include a filename, or
1570 a wild-card string, where <code>?</code> matches any single character,
1571 and <code>*</code> matches any sequences of characters.
1572 <a class="glossarylink" href="../glossary.html#regex" title="ver glosario">Regular expressions</a>
1573 can also be used, with the addition of the
1574 <code>~</code> character. For example:</p>
1576 <div class="example"><p><code>
1577 <Files ~ "\.(gif|jpe?g|png)$">
1580 <p>would match most common Internet graphics formats. <code class="directive"><a href="#filesmatch"><FilesMatch></a></code> is preferred,
1583 <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
1584 <code>.htaccess</code> files. This allows users to control access to
1585 their own files, at a file-by-file level.</p>
1588 <h3>Consulte también</h3>
1590 <li><a href="../sections.html">How <Directory>, <Location>
1591 and <Files> sections work</a> for an explanation of how these
1592 different sections are combined when a request is received</li>
1595 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1596 <div class="directive-section"><h2><a name="FilesMatch" id="FilesMatch"><FilesMatch></a> <a name="filesmatch" id="filesmatch">Directiva</a></h2>
1597 <table class="directive">
1598 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply to regular-expression matched
1600 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><FilesMatch <var>regex</var>> ... </FilesMatch></code></td></tr>
1601 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1602 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
1603 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1604 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1606 <p>The <code class="directive"><FilesMatch></code> directive
1607 limits the scope of the enclosed directives by filename, just as the
1608 <code class="directive"><a href="#files"><Files></a></code> directive
1609 does. However, it accepts a <a class="glossarylink" href="../glossary.html#regex" title="ver glosario">regular
1610 expression</a>. For example:</p>
1612 <div class="example"><p><code>
1613 <FilesMatch "\.(gif|jpe?g|png)$">
1616 <p>would match most common Internet graphics formats.</p>
1618 <h3>Consulte también</h3>
1620 <li><a href="../sections.html">How <Directory>, <Location>
1621 and <Files> sections work</a> for an explanation of how these
1622 different sections are combined when a request is received</li>
1625 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1626 <div class="directive-section"><h2><a name="ForceType" id="ForceType">ForceType</a> <a name="forcetype" id="forcetype">Directiva</a></h2>
1627 <table class="directive">
1628 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Forces all matching files to be served with the specified
1629 media type in the HTTP Content-Type header field</td></tr>
1630 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ForceType <var>media-type</var>|None</code></td></tr>
1631 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
1632 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
1633 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1634 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1635 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Moved to the core in Apache httpd 2.0</td></tr>
1637 <p>When placed into an <code>.htaccess</code> file or a
1638 <code class="directive"><a href="#directory"><Directory></a></code>, or
1639 <code class="directive"><a href="#location"><Location></a></code> or
1640 <code class="directive"><a href="#files"><Files></a></code>
1641 section, this directive forces all matching files to be served
1642 with the content type identification given by
1643 <var>media-type</var>. For example, if you had a directory full of
1644 GIF files, but did not want to label them all with <code>.gif</code>,
1645 you might want to use:</p>
1647 <div class="example"><p><code>
1651 <p>Note that this directive overrides other indirect media type
1652 associations defined in mime.types or via the
1653 <code class="directive"><a href="../mod/mod_mime.html#addtype">AddType</a></code>.</p>
1655 <p>You can also override more general
1656 <code class="directive">ForceType</code> settings
1657 by using the value of <code>None</code>:</p>
1659 <div class="example"><p><code>
1660 # force all files to be image/gif:<br />
1661 <Location /images><br />
1662 <span class="indent">
1663 ForceType image/gif<br />
1665 </Location><br />
1667 # but normal mime-type associations here:<br />
1668 <Location /images/mixed><br />
1669 <span class="indent">
1670 ForceType None<br />
1675 <p>This directive primarily overrides the content types generated for
1676 static files served out of the filesystem. For resources other than
1677 static files, where the generator of the response typically specifies
1678 a Content-Type, this directive has no effect.</p>
1682 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1683 <div class="directive-section"><h2><a name="GprofDir" id="GprofDir">GprofDir</a> <a name="gprofdir" id="gprofdir">Directiva</a></h2>
1684 <table class="directive">
1685 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Directory to write gmon.out profiling data to. </td></tr>
1686 <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>
1687 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
1688 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1689 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1691 <p>When the server has been compiled with gprof profiling support,
1692 <code class="directive">GprofDir</code> causes <code>gmon.out</code> files to
1693 be written to the specified directory when the process exits. If the
1694 argument ends with a percent symbol ('%'), subdirectories are created
1695 for each process id.</p>
1697 <p>This directive currently only works with the <code class="module"><a href="../mod/prefork.html">prefork</a></code>
1701 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1702 <div class="directive-section"><h2><a name="HostnameLookups" id="HostnameLookups">HostnameLookups</a> <a name="hostnamelookups" id="hostnamelookups">Directiva</a></h2>
1703 <table class="directive">
1704 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enables DNS lookups on client IP addresses</td></tr>
1705 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>HostnameLookups On|Off|Double</code></td></tr>
1706 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>HostnameLookups Off</code></td></tr>
1707 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
1708 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1709 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1711 <p>This directive enables DNS lookups so that host names can be
1712 logged (and passed to CGIs/SSIs in <code>REMOTE_HOST</code>).
1713 The value <code>Double</code> refers to doing double-reverse
1714 DNS lookup. That is, after a reverse lookup is performed, a forward
1715 lookup is then performed on that result. At least one of the IP
1716 addresses in the forward lookup must match the original
1717 address. (In "tcpwrappers" terminology this is called
1718 <code>PARANOID</code>.)</p>
1720 <p>Regardless of the setting, when <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code> is
1721 used for controlling access by hostname, a double reverse lookup
1722 will be performed. This is necessary for security. Note that the
1723 result of this double-reverse isn't generally available unless you
1724 set <code>HostnameLookups Double</code>. For example, if only
1725 <code>HostnameLookups On</code> and a request is made to an object
1726 that is protected by hostname restrictions, regardless of whether
1727 the double-reverse fails or not, CGIs will still be passed the
1728 single-reverse result in <code>REMOTE_HOST</code>.</p>
1730 <p>The default is <code>Off</code> in order to save the network
1731 traffic for those sites that don't truly need the reverse
1732 lookups done. It is also better for the end users because they
1733 don't have to suffer the extra latency that a lookup entails.
1734 Heavily loaded sites should leave this directive
1735 <code>Off</code>, since DNS lookups can take considerable
1736 amounts of time. The utility <code class="program"><a href="../programs/logresolve.html">logresolve</a></code>, compiled by
1737 default to the <code>bin</code> subdirectory of your installation
1738 directory, can be used to look up host names from logged IP addresses
1742 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1743 <div class="directive-section"><h2><a name="If" id="If"><If></a> <a name="if" id="if">Directiva</a></h2>
1744 <table class="directive">
1745 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply only if a condition is
1746 satisfied by a request at runtime</td></tr>
1747 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><If <var>expression</var>> ... </If></code></td></tr>
1748 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1749 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
1750 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1751 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1753 <p>The <code class="directive"><If></code> directive
1754 evaluates an expression at runtime, and applies the enclosed
1755 directives if and only if the expression evaluates to true.
1758 <div class="example"><p><code>
1759 <If "$req{Host} = ''">
1762 <p>would match HTTP/1.0 requests without a <var>Host:</var> header.</p>
1764 <p>You may compare the value of any variable in the request headers
1765 ($req), response headers ($resp) or environment ($env) in your
1768 <p>Apart from <code>=</code>, <code>If</code> can use the <code>IN</code>
1769 operator to compare if the expression is in a given range:</p>
1771 <div class="example"><p><code>
1772 <If %{REQUEST_METHOD} IN GET,HEAD,OPTIONS>
1776 <h3>Consulte también</h3>
1778 <li><a href="../expr.html">Expressions in Apache HTTP Server</a>,
1779 for a complete reference and more examples.</li>
1780 <li><a href="../sections.html">How <Directory>, <Location>,
1781 <Files> sections work</a> for an explanation of how these
1782 different sections are combined when a request is received.
1783 <code class="directive"><If></code> has the same precedence
1784 and usage as <code class="directive"><Files></code></li>
1787 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1788 <div class="directive-section"><h2><a name="IfDefine" id="IfDefine"><IfDefine></a> <a name="ifdefine" id="ifdefine">Directiva</a></h2>
1789 <table class="directive">
1790 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Encloses directives that will be processed only
1791 if a test is true at startup</td></tr>
1792 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><IfDefine [!]<var>parameter-name</var>> ...
1793 </IfDefine></code></td></tr>
1794 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1795 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
1796 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1797 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1799 <p>The <code><IfDefine <var>test</var>>...</IfDefine>
1800 </code> section is used to mark directives that are conditional. The
1801 directives within an <code class="directive"><IfDefine></code>
1802 section are only processed if the <var>test</var> is true. If <var>
1803 test</var> is false, everything between the start and end markers is
1806 <p>The <var>test</var> in the <code class="directive"><IfDefine></code> section directive can be one of two forms:</p>
1809 <li><var>parameter-name</var></li>
1811 <li><code>!</code><var>parameter-name</var></li>
1814 <p>In the former case, the directives between the start and end
1815 markers are only processed if the parameter named
1816 <var>parameter-name</var> is defined. The second format reverses
1817 the test, and only processes the directives if
1818 <var>parameter-name</var> is <strong>not</strong> defined.</p>
1820 <p>The <var>parameter-name</var> argument is a define as given on the
1821 <code class="program"><a href="../programs/httpd.html">httpd</a></code> command line via <code>-D<var>parameter</var>
1822 </code> at the time the server was started or by the <code class="directive"><a href="#define">Define</a></code> directive.</p>
1824 <p><code class="directive"><IfDefine></code> sections are
1825 nest-able, which can be used to implement simple
1826 multiple-parameter tests. Example:</p>
1828 <div class="example"><p><code>
1829 httpd -DReverseProxy -DUseCache -DMemCache ...<br />
1832 <IfDefine ReverseProxy><br />
1833 <span class="indent">
1834 LoadModule proxy_module modules/mod_proxy.so<br />
1835 LoadModule proxy_http_module modules/mod_proxy_http.so<br />
1836 <IfDefine UseCache><br />
1837 <span class="indent">
1838 LoadModule cache_module modules/mod_cache.so<br />
1839 <IfDefine MemCache><br />
1840 <span class="indent">
1841 LoadModule mem_cache_module modules/mod_mem_cache.so<br />
1843 </IfDefine><br />
1844 <IfDefine !MemCache><br />
1845 <span class="indent">
1846 LoadModule cache_disk_module modules/mod_cache_disk.so<br />
1856 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1857 <div class="directive-section"><h2><a name="IfModule" id="IfModule"><IfModule></a> <a name="ifmodule" id="ifmodule">Directiva</a></h2>
1858 <table class="directive">
1859 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Encloses directives that are processed conditional on the
1860 presence or absence of a specific module</td></tr>
1861 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><IfModule [!]<var>module-file</var>|<var>module-identifier</var>> ...
1862 </IfModule></code></td></tr>
1863 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1864 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
1865 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1866 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1867 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Module identifiers are available in version 2.1 and
1870 <p>The <code><IfModule <var>test</var>>...</IfModule></code>
1871 section is used to mark directives that are conditional on the presence of
1872 a specific module. The directives within an <code class="directive"><IfModule></code> section are only processed if the <var>test</var>
1873 is true. If <var>test</var> is false, everything between the start and
1874 end markers is ignored.</p>
1876 <p>The <var>test</var> in the <code class="directive"><IfModule></code> section directive can be one of two forms:</p>
1879 <li><var>module</var></li>
1881 <li>!<var>module</var></li>
1884 <p>In the former case, the directives between the start and end
1885 markers are only processed if the module named <var>module</var>
1886 is included in Apache httpd -- either compiled in or
1887 dynamically loaded using <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code>. The second format reverses the test,
1888 and only processes the directives if <var>module</var> is
1889 <strong>not</strong> included.</p>
1891 <p>The <var>module</var> argument can be either the module identifier or
1892 the file name of the module, at the time it was compiled. For example,
1893 <code>rewrite_module</code> is the identifier and
1894 <code>mod_rewrite.c</code> is the file name. If a module consists of
1895 several source files, use the name of the file containing the string
1896 <code>STANDARD20_MODULE_STUFF</code>.</p>
1898 <p><code class="directive"><IfModule></code> sections are
1899 nest-able, which can be used to implement simple multiple-module
1902 <div class="note">This section should only be used if you need to have one
1903 configuration file that works whether or not a specific module
1904 is available. In normal operation, directives need not be
1905 placed in <code class="directive"><IfModule></code>
1909 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1910 <div class="directive-section"><h2><a name="Include" id="Include">Include</a> <a name="include" id="include">Directiva</a></h2>
1911 <table class="directive">
1912 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Includes other configuration files from within
1913 the server configuration files</td></tr>
1914 <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>
1915 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
1916 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1917 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1918 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Wildcard matching available in 2.0.41 and later, directory
1919 wildcard matching available in 2.3.6 and later</td></tr>
1921 <p>This directive allows inclusion of other configuration files
1922 from within the server configuration files.</p>
1924 <p>Shell-style (<code>fnmatch()</code>) wildcard characters can be used
1925 in the filename or directory parts of the path to include several files
1926 at once, in alphabetical order. In addition, if
1927 <code class="directive">Include</code> points to a directory, rather than a file,
1928 Apache httpd will read all files in that directory and any subdirectory.
1929 However, including entire directories is not recommended, because it is
1930 easy to accidentally leave temporary files in a directory that can cause
1931 <code class="program"><a href="../programs/httpd.html">httpd</a></code> to fail. Instead, we encourage you to use the
1932 wildcard syntax shown below, to include files that match a particular
1933 pattern, such as *.conf, for example.</p>
1935 <p>When a wildcard is specified for a <strong>file</strong> component of
1936 the path, and no file matches the wildcard, the
1937 <code class="directive"><a href="#include">Include</a></code>
1938 directive will be <strong>silently ignored</strong>. When a wildcard is
1939 specified for a <strong>directory</strong> component of the path, and
1940 no directory matches the wildcard, the
1941 <code class="directive"><a href="#include">Include</a></code> directive will
1942 <strong>fail with an error</strong> saying the directory cannot be found.
1945 <p>For further control over the behaviour of the server when no files or
1946 directories match, prefix the path with the modifiers <var>optional</var>
1947 or <var>strict</var>. If <var>optional</var> is specified, any wildcard
1948 file or directory that does not match will be silently ignored. If
1949 <var>strict</var> is specified, any wildcard file or directory that does
1950 not match at least one file will cause server startup to fail.</p>
1952 <p>When a directory or file component of the path is
1953 specified exactly, and that directory or file does not exist,
1954 <code class="directive"><a href="#include">Include</a></code> directive will fail with an
1955 error saying the file or directory cannot be found.</p>
1957 <p>The file path specified may be an absolute path, or may be relative
1958 to the <code class="directive"><a href="#serverroot">ServerRoot</a></code> directory.</p>
1962 <div class="example"><p><code>
1963 Include /usr/local/apache2/conf/ssl.conf<br />
1964 Include /usr/local/apache2/conf/vhosts/*.conf
1967 <p>Or, providing paths relative to your <code class="directive"><a href="#serverroot">ServerRoot</a></code> directory:</p>
1969 <div class="example"><p><code>
1970 Include conf/ssl.conf<br />
1971 Include conf/vhosts/*.conf
1974 <p>Wildcards may be included in the directory or file portion of the
1975 path. In the following example, the server will fail to load if no
1976 directories match conf/vhosts/*, but will load successfully if no
1977 files match *.conf.</p>
1979 <div class="example"><p><code>
1980 Include conf/vhosts/*/vhost.conf<br />
1981 Include conf/vhosts/*/*.conf
1984 <p>In this example, the server will fail to load if either
1985 conf/vhosts/* matches no directories, or if *.conf matches no files:</p>
1987 <div class="example"><p><code>
1988 Include strict conf/vhosts/*/*.conf
1991 <p>In this example, the server load successfully if either conf/vhosts/*
1992 matches no directories, or if *.conf matches no files:</p>
1994 <div class="example"><p><code>
1995 Include optional conf/vhosts/*/*.conf
1999 <h3>Consulte también</h3>
2001 <li><code class="program"><a href="../programs/apachectl.html">apachectl</a></code></li>
2004 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2005 <div class="directive-section"><h2><a name="IncludeOptional" id="IncludeOptional">IncludeOptional</a> <a name="includeoptional" id="includeoptional">Directiva</a></h2>
2006 <table class="directive">
2007 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Includes other configuration files from within
2008 the server configuration files</td></tr>
2009 <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>
2010 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
2011 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2012 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2013 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in 2.3.6 and later</td></tr>
2014 </table><p>The documentation for this directive has
2015 not been translated yet. Please have a look at the English
2016 version.</p><h3>Consulte también</h3>
2018 <li><code class="directive"><a href="#include">Include</a></code></li>
2019 <li><code class="program"><a href="../programs/apachectl.html">apachectl</a></code></li>
2022 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2023 <div class="directive-section"><h2><a name="KeepAlive" id="KeepAlive">KeepAlive</a> <a name="keepalive" id="keepalive">Directiva</a></h2>
2024 <table class="directive">
2025 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enables HTTP persistent connections</td></tr>
2026 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>KeepAlive On|Off</code></td></tr>
2027 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>KeepAlive On</code></td></tr>
2028 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2029 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2030 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2032 <p>The Keep-Alive extension to HTTP/1.0 and the persistent
2033 connection feature of HTTP/1.1 provide long-lived HTTP sessions
2034 which allow multiple requests to be sent over the same TCP
2035 connection. In some cases this has been shown to result in an
2036 almost 50% speedup in latency times for HTML documents with
2037 many images. To enable Keep-Alive connections, set
2038 <code>KeepAlive On</code>.</p>
2040 <p>For HTTP/1.0 clients, Keep-Alive connections will only be
2041 used if they are specifically requested by a client. In
2042 addition, a Keep-Alive connection with an HTTP/1.0 client can
2043 only be used when the length of the content is known in
2044 advance. This implies that dynamic content such as CGI output,
2045 SSI pages, and server-generated directory listings will
2046 generally not use Keep-Alive connections to HTTP/1.0 clients.
2047 For HTTP/1.1 clients, persistent connections are the default
2048 unless otherwise specified. If the client requests it, chunked
2049 encoding will be used in order to send content of unknown
2050 length over persistent connections.</p>
2052 <p>When a client uses a Keep-Alive connection it will be counted
2053 as a single "request" for the <code class="directive"><a href="../mod/mpm_common.html#maxconnectionsperchild">MaxConnectionsPerChild</a></code> directive, regardless
2054 of how many requests are sent using the connection.</p>
2056 <h3>Consulte también</h3>
2058 <li><code class="directive"><a href="#maxkeepaliverequests">MaxKeepAliveRequests</a></code></li>
2061 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2062 <div class="directive-section"><h2><a name="KeepAliveTimeout" id="KeepAliveTimeout">KeepAliveTimeout</a> <a name="keepalivetimeout" id="keepalivetimeout">Directiva</a></h2>
2063 <table class="directive">
2064 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Amount of time the server will wait for subsequent
2065 requests on a persistent connection</td></tr>
2066 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>KeepAliveTimeout <var>num</var>[ms]</code></td></tr>
2067 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>KeepAliveTimeout 5</code></td></tr>
2068 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2069 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2070 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2071 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Specifying a value in milliseconds is available in
2072 Apache httpd 2.3.2 and later</td></tr>
2074 <p>The number of seconds Apache httpd will wait for a subsequent
2075 request before closing the connection. By adding a postfix of ms the
2076 timeout can be also set in milliseconds. Once a request has been
2077 received, the timeout value specified by the
2078 <code class="directive"><a href="#timeout">Timeout</a></code> directive applies.</p>
2080 <p>Setting <code class="directive">KeepAliveTimeout</code> to a high value
2081 may cause performance problems in heavily loaded servers. The
2082 higher the timeout, the more server processes will be kept
2083 occupied waiting on connections with idle clients.</p>
2085 <p>In a name-based virtual host context, the value of the first
2086 defined virtual host (the default host) in a set of <code class="directive"><a href="#namevirtualhost">NameVirtualHost</a></code> will be used.
2087 The other values will be ignored.</p>
2090 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2091 <div class="directive-section"><h2><a name="Limit" id="Limit"><Limit></a> <a name="limit" id="limit">Directiva</a></h2>
2092 <table class="directive">
2093 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Restrict enclosed access controls to only certain HTTP
2095 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><Limit <var>method</var> [<var>method</var>] ... > ...
2096 </Limit></code></td></tr>
2097 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
2098 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>AuthConfig, Limit</td></tr>
2099 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2100 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2102 <p>Access controls are normally effective for
2103 <strong>all</strong> access methods, and this is the usual
2104 desired behavior. <strong>In the general case, access control
2105 directives should not be placed within a
2106 <code class="directive"><Limit></code> section.</strong></p>
2108 <p>The purpose of the <code class="directive"><Limit></code>
2109 directive is to restrict the effect of the access controls to the
2110 nominated HTTP methods. For all other methods, the access
2111 restrictions that are enclosed in the <code class="directive"><Limit></code> bracket <strong>will have no
2112 effect</strong>. The following example applies the access control
2113 only to the methods <code>POST</code>, <code>PUT</code>, and
2114 <code>DELETE</code>, leaving all other methods unprotected:</p>
2116 <div class="example"><p><code>
2117 <Limit POST PUT DELETE><br />
2118 <span class="indent">
2119 Require valid-user<br />
2124 <p>The method names listed can be one or more of: <code>GET</code>,
2125 <code>POST</code>, <code>PUT</code>, <code>DELETE</code>,
2126 <code>CONNECT</code>, <code>OPTIONS</code>,
2127 <code>PATCH</code>, <code>PROPFIND</code>, <code>PROPPATCH</code>,
2128 <code>MKCOL</code>, <code>COPY</code>, <code>MOVE</code>,
2129 <code>LOCK</code>, and <code>UNLOCK</code>. <strong>The method name is
2130 case-sensitive.</strong> If <code>GET</code> is used it will also
2131 restrict <code>HEAD</code> requests. The <code>TRACE</code> method
2132 cannot be limited (see <code class="directive"><a href="#traceenable">TraceEnable</a></code>).</p>
2134 <div class="warning">A <code class="directive"><a href="#limitexcept"><LimitExcept></a></code> section should always be
2135 used in preference to a <code class="directive"><Limit></code>
2136 section when restricting access, since a <code class="directive"><a href="#limitexcept"><LimitExcept></a></code> section provides protection
2137 against arbitrary methods.</div>
2139 <p>The <code class="directive"><Limit></code> and
2140 <code class="directive"><a href="#limitexcept"><LimitExcept></a></code>
2141 directives may be nested. In this case, each successive level of
2142 <code class="directive"><Limit></code> or <code class="directive"><a href="#limitexcept"><LimitExcept></a></code> directives must
2143 further restrict the set of methods to which access controls apply.</p>
2145 <div class="warning">When using
2146 <code class="directive"><Limit></code> or
2147 <code class="directive"><LimitExcept></code> directives with
2148 the <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> directive,
2149 note that the first <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>
2150 to succeed authorizes the request, regardless of the presence of other
2151 <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> directives.</div>
2153 <p>For example, given the following configuration, all users will
2154 be authorized for <code>POST</code> requests, and the
2155 <code>Require group editors</code> directive will be ignored
2158 <div class="example"><p><code>
2159 <LimitExcept GET>
2160 <span class="indent">
2163 </LimitExcept><br />
2165 <span class="indent">
2166 Require group editors
2172 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2173 <div class="directive-section"><h2><a name="LimitExcept" id="LimitExcept"><LimitExcept></a> <a name="limitexcept" id="limitexcept">Directiva</a></h2>
2174 <table class="directive">
2175 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Restrict access controls to all HTTP methods
2176 except the named ones</td></tr>
2177 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><LimitExcept <var>method</var> [<var>method</var>] ... > ...
2178 </LimitExcept></code></td></tr>
2179 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
2180 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>AuthConfig, Limit</td></tr>
2181 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2182 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2184 <p><code class="directive"><LimitExcept></code> and
2185 <code></LimitExcept></code> are used to enclose
2186 a group of access control directives which will then apply to any
2187 HTTP access method <strong>not</strong> listed in the arguments;
2188 i.e., it is the opposite of a <code class="directive"><a href="#limit"><Limit></a></code> section and can be used to control
2189 both standard and nonstandard/unrecognized methods. See the
2190 documentation for <code class="directive"><a href="#limit"><Limit></a></code> for more details.</p>
2194 <div class="example"><p><code>
2195 <LimitExcept POST GET><br />
2196 <span class="indent">
2197 Require valid-user<br />
2199 </LimitExcept>
2204 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2205 <div class="directive-section"><h2><a name="LimitInternalRecursion" id="LimitInternalRecursion">LimitInternalRecursion</a> <a name="limitinternalrecursion" id="limitinternalrecursion">Directiva</a></h2>
2206 <table class="directive">
2207 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determine maximum number of internal redirects and nested
2208 subrequests</td></tr>
2209 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitInternalRecursion <var>number</var> [<var>number</var>]</code></td></tr>
2210 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitInternalRecursion 10</code></td></tr>
2211 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2212 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2213 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2214 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache httpd 2.0.47 and later</td></tr>
2216 <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
2217 redirects the original request to a CGI script. A subrequest is Apache httpd's
2218 mechanism to find out what would happen for some URI if it were requested.
2219 For example, <code class="module"><a href="../mod/mod_dir.html">mod_dir</a></code> uses subrequests to look for the
2220 files listed in the <code class="directive"><a href="../mod/mod_dir.html#directoryindex">DirectoryIndex</a></code>
2223 <p><code class="directive">LimitInternalRecursion</code> prevents the server
2224 from crashing when entering an infinite loop of internal redirects or
2225 subrequests. Such loops are usually caused by misconfigurations.</p>
2227 <p>The directive stores two different limits, which are evaluated on
2228 per-request basis. The first <var>number</var> is the maximum number of
2229 internal redirects, that may follow each other. The second <var>number</var>
2230 determines, how deep subrequests may be nested. If you specify only one
2231 <var>number</var>, it will be assigned to both limits.</p>
2233 <div class="example"><h3>Example</h3><p><code>
2234 LimitInternalRecursion 5
2238 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2239 <div class="directive-section"><h2><a name="LimitRequestBody" id="LimitRequestBody">LimitRequestBody</a> <a name="limitrequestbody" id="limitrequestbody">Directiva</a></h2>
2240 <table class="directive">
2241 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Restricts the total size of the HTTP request body sent
2242 from the client</td></tr>
2243 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitRequestBody <var>bytes</var></code></td></tr>
2244 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitRequestBody 0</code></td></tr>
2245 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
2246 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
2247 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2248 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2250 <p>This directive specifies the number of <var>bytes</var> from 0
2251 (meaning unlimited) to 2147483647 (2GB) that are allowed in a
2252 request body. See the note below for the limited applicability
2253 to proxy requests.</p>
2255 <p>The <code class="directive">LimitRequestBody</code> directive allows
2256 the user to set a limit on the allowed size of an HTTP request
2257 message body within the context in which the directive is given
2258 (server, per-directory, per-file or per-location). If the client
2259 request exceeds that limit, the server will return an error
2260 response instead of servicing the request. The size of a normal
2261 request message body will vary greatly depending on the nature of
2262 the resource and the methods allowed on that resource. CGI scripts
2263 typically use the message body for retrieving form information.
2264 Implementations of the <code>PUT</code> method will require
2265 a value at least as large as any representation that the server
2266 wishes to accept for that resource.</p>
2268 <p>This directive gives the server administrator greater
2269 control over abnormal client request behavior, which may be
2270 useful for avoiding some forms of denial-of-service
2273 <p>If, for example, you are permitting file upload to a particular
2274 location, and wish to limit the size of the uploaded file to 100K,
2275 you might use the following directive:</p>
2277 <div class="example"><p><code>
2278 LimitRequestBody 102400
2281 <div class="note"><p>For a full description of how this directive is interpreted by
2282 proxy requests, see the <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> documentation.</p>
2287 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2288 <div class="directive-section"><h2><a name="LimitRequestFields" id="LimitRequestFields">LimitRequestFields</a> <a name="limitrequestfields" id="limitrequestfields">Directiva</a></h2>
2289 <table class="directive">
2290 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the number of HTTP request header fields that
2291 will be accepted from the client</td></tr>
2292 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitRequestFields <var>number</var></code></td></tr>
2293 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitRequestFields 100</code></td></tr>
2294 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2295 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2296 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2298 <p><var>Number</var> is an integer from 0 (meaning unlimited) to
2299 32767. The default value is defined by the compile-time
2300 constant <code>DEFAULT_LIMIT_REQUEST_FIELDS</code> (100 as
2303 <p>The <code class="directive">LimitRequestFields</code> directive allows
2304 the server administrator to modify the limit on the number of
2305 request header fields allowed in an HTTP request. A server needs
2306 this value to be larger than the number of fields that a normal
2307 client request might include. The number of request header fields
2308 used by a client rarely exceeds 20, but this may vary among
2309 different client implementations, often depending upon the extent
2310 to which a user has configured their browser to support detailed
2311 content negotiation. Optional HTTP extensions are often expressed
2312 using request header fields.</p>
2314 <p>This directive gives the server administrator greater
2315 control over abnormal client request behavior, which may be
2316 useful for avoiding some forms of denial-of-service attacks.
2317 The value should be increased if normal clients see an error
2318 response from the server that indicates too many fields were
2319 sent in the request.</p>
2323 <div class="example"><p><code>
2324 LimitRequestFields 50
2327 <div class="warning"><h3>Warning</h3>
2328 <p> When name-based virtual hosting is used, the value for this
2329 directive is taken from the default (first-listed) virtual host for the
2330 <code class="directive">NameVirtualHost</code> the connection was mapped to.</p>
2335 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2336 <div class="directive-section"><h2><a name="LimitRequestFieldSize" id="LimitRequestFieldSize">LimitRequestFieldSize</a> <a name="limitrequestfieldsize" id="limitrequestfieldsize">Directiva</a></h2>
2337 <table class="directive">
2338 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the size of the HTTP request header allowed from the
2340 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitRequestFieldSize <var>bytes</var></code></td></tr>
2341 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitRequestFieldSize 8190</code></td></tr>
2342 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2343 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2344 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2346 <p>This directive specifies the number of <var>bytes</var>
2347 that will be allowed in an HTTP request header.</p>
2349 <p>The <code class="directive">LimitRequestFieldSize</code> directive
2350 allows the server administrator to reduce or increase the limit
2351 on the allowed size of an HTTP request header field. A server
2352 needs this value to be large enough to hold any one header field
2353 from a normal client request. The size of a normal request header
2354 field will vary greatly among different client implementations,
2355 often depending upon the extent to which a user has configured
2356 their browser to support detailed content negotiation. SPNEGO
2357 authentication headers can be up to 12392 bytes.</p>
2359 <p>This directive gives the server administrator greater
2360 control over abnormal client request behavior, which may be
2361 useful for avoiding some forms of denial-of-service attacks.</p>
2365 <div class="example"><p><code>
2366 LimitRequestFieldSize 4094
2369 <div class="note">Under normal conditions, the value should not be changed from
2372 <div class="warning"><h3>Warning</h3>
2373 <p> When name-based virtual hosting is used, the value for this
2374 directive is taken from the default (first-listed) virtual host for the
2375 <code class="directive">NameVirtualHost</code> the connection was mapped to.</p>
2380 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2381 <div class="directive-section"><h2><a name="LimitRequestLine" id="LimitRequestLine">LimitRequestLine</a> <a name="limitrequestline" id="limitrequestline">Directiva</a></h2>
2382 <table class="directive">
2383 <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
2384 from the client</td></tr>
2385 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitRequestLine <var>bytes</var></code></td></tr>
2386 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitRequestLine 8190</code></td></tr>
2387 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2388 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2389 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2391 <p>This directive sets the number of <var>bytes</var> that will be
2392 allowed on the HTTP request-line.</p>
2394 <p>The <code class="directive">LimitRequestLine</code> directive allows
2395 the server administrator to reduce or increase the limit on the allowed size
2396 of a client's HTTP request-line. Since the request-line consists of the
2397 HTTP method, URI, and protocol version, the
2398 <code class="directive">LimitRequestLine</code> directive places a
2399 restriction on the length of a request-URI allowed for a request
2400 on the server. A server needs this value to be large enough to
2401 hold any of its resource names, including any information that
2402 might be passed in the query part of a <code>GET</code> request.</p>
2404 <p>This directive gives the server administrator greater
2405 control over abnormal client request behavior, which may be
2406 useful for avoiding some forms of denial-of-service attacks.</p>
2410 <div class="example"><p><code>
2411 LimitRequestLine 4094
2414 <div class="note">Under normal conditions, the value should not be changed from
2417 <div class="warning"><h3>Warning</h3>
2418 <p> When name-based virtual hosting is used, the value for this
2419 directive is taken from the default (first-listed) virtual host for the
2420 <code class="directive">NameVirtualHost</code> the connection was mapped to.</p>
2425 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2426 <div class="directive-section"><h2><a name="LimitXMLRequestBody" id="LimitXMLRequestBody">LimitXMLRequestBody</a> <a name="limitxmlrequestbody" id="limitxmlrequestbody">Directiva</a></h2>
2427 <table class="directive">
2428 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the size of an XML-based request body</td></tr>
2429 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitXMLRequestBody <var>bytes</var></code></td></tr>
2430 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitXMLRequestBody 1000000</code></td></tr>
2431 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
2432 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
2433 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2434 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2436 <p>Limit (in bytes) on maximum size of an XML-based request
2437 body. A value of <code>0</code> will disable any checking.</p>
2441 <div class="example"><p><code>
2442 LimitXMLRequestBody 0
2447 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2448 <div class="directive-section"><h2><a name="Location" id="Location"><Location></a> <a name="location" id="location">Directiva</a></h2>
2449 <table class="directive">
2450 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Applies the enclosed directives only to matching
2452 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><Location
2453 <var>URL-path</var>|<var>URL</var>> ... </Location></code></td></tr>
2454 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2455 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2456 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2458 <p>The <code class="directive"><Location></code> directive
2459 limits the scope of the enclosed directives by URL. It is similar to the
2460 <code class="directive"><a href="#directory"><Directory></a></code>
2461 directive, and starts a subsection which is terminated with a
2462 <code></Location></code> directive. <code class="directive"><Location></code> sections are processed in the
2463 order they appear in the configuration file, after the <code class="directive"><a href="#directory"><Directory></a></code> sections and
2464 <code>.htaccess</code> files are read, and after the <code class="directive"><a href="#files"><Files></a></code> sections.</p>
2466 <p><code class="directive"><Location></code> sections operate
2467 completely outside the filesystem. This has several consequences.
2468 Most importantly, <code class="directive"><Location></code>
2469 directives should not be used to control access to filesystem
2470 locations. Since several different URLs may map to the same
2471 filesystem location, such access controls may by circumvented.</p>
2473 <p>The enclosed directives will be applied to the request if the path component
2474 of the URL meets <em>any</em> of the following criteria:
2477 <li>The specified location matches exactly the path component of the URL.
2479 <li>The specified location, which ends in a forward slash, is a prefix
2480 of the path component of the URL (treated as a context root).
2482 <li>The specified location, with the addition of a trailing slash, is a
2483 prefix of the path component of the URL (also treated as a context root).
2487 In the example below, where no trailing slash is used, requests to
2488 /private1, /private1/ and /private1/file.txt will have the enclosed
2489 directives applied, but /private1other would not.
2491 <div class="example"><p><code>
2492 <Location /private1>
2496 In the example below, where a trailing slash is used, requests to
2497 /private2/ and /private2/file.txt will have the enclosed
2498 directives applied, but /private2 and /private2other would not.
2500 <div class="example"><p><code>
2501 <Location /private2<em>/</em>>
2505 <div class="note"><h3>When to use <code class="directive"><Location></code></h3>
2507 <p>Use <code class="directive"><Location></code> to apply
2508 directives to content that lives outside the filesystem. For
2509 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
2510 <code><Location /></code>, which is an easy way to
2511 apply a configuration to the entire server.</p>
2514 <p>For all origin (non-proxy) requests, the URL to be matched is a
2515 URL-path of the form <code>/path/</code>. <em>No scheme, hostname,
2516 port, or query string may be included.</em> For proxy requests, the
2517 URL to be matched is of the form
2518 <code>scheme://servername/path</code>, and you must include the
2521 <p>The URL may use wildcards. In a wild-card string, <code>?</code> matches
2522 any single character, and <code>*</code> matches any sequences of
2523 characters. Neither wildcard character matches a / in the URL-path.</p>
2525 <p><a class="glossarylink" href="../glossary.html#regex" title="ver glosario">Regular expressions</a>
2526 can also be used, with the addition of the <code>~</code>
2527 character. For example:</p>
2529 <div class="example"><p><code>
2530 <Location ~ "/(extra|special)/data">
2533 <p>would match URLs that contained the substring <code>/extra/data</code>
2534 or <code>/special/data</code>. The directive <code class="directive"><a href="#locationmatch"><LocationMatch></a></code> behaves
2535 identical to the regex version of <code class="directive"><Location></code>, and is preferred, for the
2536 simple reason that <code>~</code> is hard to distinguish from
2537 <code>-</code> in many fonts.</p>
2539 <p>The <code class="directive"><Location></code>
2540 functionality is especially useful when combined with the
2541 <code class="directive"><a href="#sethandler">SetHandler</a></code>
2542 directive. For example, to enable status requests, but allow them
2543 only from browsers at <code>example.com</code>, you might use:</p>
2545 <div class="example"><p><code>
2546 <Location /status><br />
2547 <span class="indent">
2548 SetHandler server-status<br />
2549 Require host example.com<br />
2554 <div class="note"><h3>Note about / (slash)</h3>
2555 <p>The slash character has special meaning depending on where in a
2556 URL it appears. People may be used to its behavior in the filesystem
2557 where multiple adjacent slashes are frequently collapsed to a single
2558 slash (<em>i.e.</em>, <code>/home///foo</code> is the same as
2559 <code>/home/foo</code>). In URL-space this is not necessarily true.
2560 The <code class="directive"><a href="#locationmatch"><LocationMatch></a></code>
2561 directive and the regex version of <code class="directive"><Location></code> require you to explicitly specify multiple
2562 slashes if that is your intention.</p>
2564 <p>For example, <code><LocationMatch ^/abc></code> would match
2565 the request URL <code>/abc</code> but not the request URL <code>
2566 //abc</code>. The (non-regex) <code class="directive"><Location></code> directive behaves similarly when used for
2567 proxy requests. But when (non-regex) <code class="directive"><Location></code> is used for non-proxy requests it will
2568 implicitly match multiple slashes with a single slash. For example,
2569 if you specify <code><Location /abc/def></code> and the
2570 request is to <code>/abc//def</code> then it will match.</p>
2573 <h3>Consulte también</h3>
2575 <li><a href="../sections.html">How <Directory>, <Location>
2576 and <Files> sections work</a> for an explanation of how these
2577 different sections are combined when a request is received.</li>
2578 <li><code class="directive"><a href="#locationmatch">LocationMatch</a></code></li>
2581 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2582 <div class="directive-section"><h2><a name="LocationMatch" id="LocationMatch"><LocationMatch></a> <a name="locationmatch" id="locationmatch">Directiva</a></h2>
2583 <table class="directive">
2584 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Applies the enclosed directives only to regular-expression
2585 matching URLs</td></tr>
2586 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><LocationMatch
2587 <var>regex</var>> ... </LocationMatch></code></td></tr>
2588 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2589 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2590 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2592 <p>The <code class="directive"><LocationMatch></code> directive
2593 limits the scope of the enclosed directives by URL, in an identical manner
2594 to <code class="directive"><a href="#location"><Location></a></code>. However,
2595 it takes a <a class="glossarylink" href="../glossary.html#regex" title="ver glosario">regular expression</a>
2596 as an argument instead of a simple string. For example:</p>
2598 <div class="example"><p><code>
2599 <LocationMatch "/(extra|special)/data">
2602 <p>would match URLs that contained the substring <code>/extra/data</code>
2603 or <code>/special/data</code>.</p>
2605 <h3>Consulte también</h3>
2607 <li><a href="../sections.html">How <Directory>, <Location>
2608 and <Files> sections work</a> for an explanation of how these
2609 different sections are combined when a request is received</li>
2612 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2613 <div class="directive-section"><h2><a name="LogLevel" id="LogLevel">LogLevel</a> <a name="loglevel" id="loglevel">Directiva</a></h2>
2614 <table class="directive">
2615 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Controls the verbosity of the ErrorLog</td></tr>
2616 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LogLevel [<var>module</var>:]<var>level</var>
2617 [<var>module</var>:<var>level</var>] ...
2619 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LogLevel warn</code></td></tr>
2620 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
2621 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2622 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2623 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Per-module and per-directory configuration is available in
2624 Apache HTTP Server 2.3.6 and later</td></tr>
2626 <p><code class="directive">LogLevel</code> adjusts the verbosity of the
2627 messages recorded in the error logs (see <code class="directive"><a href="#errorlog">ErrorLog</a></code> directive). The following
2628 <var>level</var>s are available, in order of decreasing
2631 <table class="bordered">
2634 <th><strong>Level</strong> </th>
2636 <th><strong>Description</strong> </th>
2638 <th><strong>Example</strong> </th>
2642 <td><code>emerg</code> </td>
2644 <td>Emergencies - system is unusable.</td>
2646 <td>"Child cannot open lock file. Exiting"</td>
2650 <td><code>alert</code> </td>
2652 <td>Action must be taken immediately.</td>
2654 <td>"getpwuid: couldn't determine user name from uid"</td>
2658 <td><code>crit</code> </td>
2660 <td>Critical Conditions.</td>
2662 <td>"socket: Failed to get a socket, exiting child"</td>
2666 <td><code>error</code> </td>
2668 <td>Error conditions.</td>
2670 <td>"Premature end of script headers"</td>
2674 <td><code>warn</code> </td>
2676 <td>Warning conditions.</td>
2678 <td>"child process 1234 did not exit, sending another
2683 <td><code>notice</code> </td>
2685 <td>Normal but significant condition.</td>
2687 <td>"httpd: caught SIGBUS, attempting to dump core in
2692 <td><code>info</code> </td>
2694 <td>Informational.</td>
2696 <td>"Server seems busy, (you may need to increase
2697 StartServers, or Min/MaxSpareServers)..."</td>
2701 <td><code>debug</code> </td>
2703 <td>Debug-level messages</td>
2705 <td>"Opening config file ..."</td>
2708 <td><code>trace1</code> </td>
2710 <td>Trace messages</td>
2712 <td>"proxy: FTP: control connection complete"</td>
2715 <td><code>trace2</code> </td>
2717 <td>Trace messages</td>
2719 <td>"proxy: CONNECT: sending the CONNECT request to the remote proxy"</td>
2722 <td><code>trace3</code> </td>
2724 <td>Trace messages</td>
2726 <td>"openssl: Handshake: start"</td>
2729 <td><code>trace4</code> </td>
2731 <td>Trace messages</td>
2733 <td>"read from buffered SSL brigade, mode 0, 17 bytes"</td>
2736 <td><code>trace5</code> </td>
2738 <td>Trace messages</td>
2740 <td>"map lookup FAILED: map=rewritemap key=keyname"</td>
2743 <td><code>trace6</code> </td>
2745 <td>Trace messages</td>
2747 <td>"cache lookup FAILED, forcing new map lookup"</td>
2750 <td><code>trace7</code> </td>
2752 <td>Trace messages, dumping large amounts of data</td>
2754 <td>"| 0000: 02 23 44 30 13 40 ac 34 df 3d bf 9a 19 49 39 15 |"</td>
2757 <td><code>trace8</code> </td>
2759 <td>Trace messages, dumping large amounts of data</td>
2761 <td>"| 0000: 02 23 44 30 13 40 ac 34 df 3d bf 9a 19 49 39 15 |"</td>
2765 <p>When a particular level is specified, messages from all
2766 other levels of higher significance will be reported as well.
2767 <em>E.g.</em>, when <code>LogLevel info</code> is specified,
2768 then messages with log levels of <code>notice</code> and
2769 <code>warn</code> will also be posted.</p>
2771 <p>Using a level of at least <code>crit</code> is
2776 <div class="example"><p><code>
2780 <div class="note"><h3>Note</h3>
2781 <p>When logging to a regular file messages of the level
2782 <code>notice</code> cannot be suppressed and thus are always
2783 logged. However, this doesn't apply when logging is done
2784 using <code>syslog</code>.</p>
2787 <p>Specifying a level without a module name will reset the level
2788 for all modules to that level. Specifying a level with a module
2789 name will set the level for that module only. It is possible to
2790 use the module source file name, the module identifier, or the
2791 module identifier with the trailing <code>_module</code> omitted
2792 as module specification. This means the following three specifications
2795 <div class="example"><p><code>
2796 LogLevel info ssl:warn<br />
2797 LogLevel info mod_ssl.c:warn<br />
2798 LogLevel info ssl_module:warn<br />
2801 <p>It is also possible to change the level per directory:</p>
2803 <div class="example"><p><code>
2805 <Directory /usr/local/apache/htdocs/app><br />
2806 LogLevel debug<br />
2811 Per directory loglevel configuration only affects messages that are
2812 logged after the request has been parsed and that are associated with
2813 the request. Log messages which are associated with the connection or
2814 the server are not affected.
2818 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2819 <div class="directive-section"><h2><a name="LogLevelOverride" id="LogLevelOverride">LogLevelOverride</a> <a name="logleveloverride" id="logleveloverride">Directiva</a></h2>
2820 <table class="directive">
2821 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Override the verbosity of the ErrorLog for certain clients</td></tr>
2822 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LogLevel <var>ipaddress</var>[/<var>prefixlen</var>]
2823 [<var>module</var>:]<var>level</var> [<var>module</var>:<var>level</var>] ...
2825 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>unset</code></td></tr>
2826 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2827 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2828 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2829 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.5.0 and later</td></tr>
2830 </table><p>The documentation for this directive has
2831 not been translated yet. Please have a look at the English
2832 version.</p><h3>Consulte también</h3>
2834 <li><code class="directive"><a href="#loglevel">LogLevel</a></code></li>
2837 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2838 <div class="directive-section"><h2><a name="MaxKeepAliveRequests" id="MaxKeepAliveRequests">MaxKeepAliveRequests</a> <a name="maxkeepaliverequests" id="maxkeepaliverequests">Directiva</a></h2>
2839 <table class="directive">
2840 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Number of requests allowed on a persistent
2841 connection</td></tr>
2842 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>MaxKeepAliveRequests <var>number</var></code></td></tr>
2843 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>MaxKeepAliveRequests 100</code></td></tr>
2844 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2845 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2846 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2848 <p>The <code class="directive">MaxKeepAliveRequests</code> directive
2849 limits the number of requests allowed per connection when
2850 <code class="directive"><a href="#keepalive">KeepAlive</a></code> is on. If it is
2851 set to <code>0</code>, unlimited requests will be allowed. We
2852 recommend that this setting be kept to a high value for maximum
2853 server performance.</p>
2857 <div class="example"><p><code>
2858 MaxKeepAliveRequests 500
2862 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2863 <div class="directive-section"><h2><a name="MaxRangeOverlaps" id="MaxRangeOverlaps">MaxRangeOverlaps</a> <a name="maxrangeoverlaps" id="maxrangeoverlaps">Directiva</a></h2>
2864 <table class="directive">
2865 <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
2867 <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>
2868 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>MaxRangeOverlaps 20</code></td></tr>
2869 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
2870 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2871 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2872 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.3.15 and later</td></tr>
2873 </table><p>The documentation for this directive has
2874 not been translated yet. Please have a look at the English
2876 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2877 <div class="directive-section"><h2><a name="MaxRangeReversals" id="MaxRangeReversals">MaxRangeReversals</a> <a name="maxrangereversals" id="maxrangereversals">Directiva</a></h2>
2878 <table class="directive">
2879 <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
2881 <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>
2882 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>MaxRangeReversals 20</code></td></tr>
2883 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
2884 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2885 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2886 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.3.15 and later</td></tr>
2887 </table><p>The documentation for this directive has
2888 not been translated yet. Please have a look at the English
2890 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2891 <div class="directive-section"><h2><a name="MaxRanges" id="MaxRanges">MaxRanges</a> <a name="maxranges" id="maxranges">Directiva</a></h2>
2892 <table class="directive">
2893 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Number of ranges allowed before returning the complete
2895 <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>
2896 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>MaxRanges 200</code></td></tr>
2897 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
2898 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2899 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2900 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.3.15 and later</td></tr>
2901 </table><p>The documentation for this directive has
2902 not been translated yet. Please have a look at the English
2904 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2905 <div class="directive-section"><h2><a name="MergeTrailers" id="MergeTrailers">MergeTrailers</a> <a name="mergetrailers" id="mergetrailers">Directiva</a></h2>
2906 <table class="directive">
2907 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determines whether trailers are merged into headers</td></tr>
2908 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>MergeTrailers [on|off]</code></td></tr>
2909 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>MergeTrailers off</code></td></tr>
2910 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2911 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2912 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2913 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>2.4.11 and later</td></tr>
2914 </table><p>The documentation for this directive has
2915 not been translated yet. Please have a look at the English
2917 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2918 <div class="directive-section"><h2><a name="Mutex" id="Mutex">Mutex</a> <a name="mutex" id="mutex">Directiva</a></h2>
2919 <table class="directive">
2920 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures mutex mechanism and lock file directory for all
2921 or specified mutexes</td></tr>
2922 <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>
2923 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Mutex default</code></td></tr>
2924 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
2925 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2926 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2927 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.3.4 and later</td></tr>
2929 <p>The <code class="directive">Mutex</code> directive sets the mechanism,
2930 and optionally the lock file location, that httpd and modules use
2931 to serialize access to resources. Specify <code>default</code> as
2932 the first argument to change the settings for all mutexes; specify
2933 a mutex name (see table below) as the first argument to override
2934 defaults only for that mutex.</p>
2936 <p>The <code class="directive">Mutex</code> directive is typically used in
2937 the following exceptional situations:</p>
2940 <li>change the mutex mechanism when the default mechanism selected
2941 by <a class="glossarylink" href="../glossary.html#apr" title="ver glosario">APR</a> has a functional or performance
2944 <li>change the directory used by file-based mutexes when the
2945 default directory does not support locking</li>
2948 <div class="note"><h3>Supported modules</h3>
2949 <p>This directive only configures mutexes which have been registered
2950 with the core server using the <code>ap_mutex_register()</code> API.
2951 All modules bundled with httpd support the <code class="directive">Mutex</code>
2952 directive, but third-party modules may not. Consult the documentation
2953 of the third-party module, which must indicate the mutex name(s) which
2954 can be configured if this directive is supported.</p>
2957 <p>The following mutex <em>mechanisms</em> are available:</p>
2959 <li><code>default | yes</code>
2960 <p>This selects the default locking implementation, as determined by
2961 <a class="glossarylink" href="../glossary.html#apr" title="ver glosario">APR</a>. The default locking implementation can
2962 be displayed by running <code class="program"><a href="../programs/httpd.html">httpd</a></code> with the
2963 <code>-V</code> option.</p></li>
2965 <li><code>none | no</code>
2966 <p>This effectively disables the mutex, and is only allowed for a
2967 mutex if the module indicates that it is a valid choice. Consult the
2968 module documentation for more information.</p></li>
2970 <li><code>posixsem</code>
2971 <p>This is a mutex variant based on a Posix semaphore.</p>
2973 <div class="warning"><h3>Warning</h3>
2974 <p>The semaphore ownership is not recovered if a thread in the process
2975 holding the mutex segfaults, resulting in a hang of the web server.</p>
2979 <li><code>sysvsem</code>
2980 <p>This is a mutex variant based on a SystemV IPC semaphore.</p>
2982 <div class="warning"><h3>Warning</h3>
2983 <p>It is possible to "leak" SysV semaphores if processes crash
2984 before the semaphore is removed.</p>
2987 <div class="warning"><h3>Security</h3>
2988 <p>The semaphore API allows for a denial of service attack by any
2989 CGIs running under the same uid as the webserver (<em>i.e.</em>,
2990 all CGIs, unless you use something like <code class="program"><a href="../programs/suexec.html">suexec</a></code>
2991 or <code>cgiwrapper</code>).</p>
2995 <li><code>sem</code>
2996 <p>This selects the "best" available semaphore implementation, choosing
2997 between Posix and SystemV IPC semaphores, in that order.</p></li>
2999 <li><code>pthread</code>
3000 <p>This is a mutex variant based on cross-process Posix thread
3003 <div class="warning"><h3>Warning</h3>
3004 <p>On most systems, if a child process terminates abnormally while
3005 holding a mutex that uses this implementation, the server will deadlock
3006 and stop responding to requests. When this occurs, the server will
3007 require a manual restart to recover.</p>
3008 <p>Solaris is a notable exception as it provides a mechanism which
3009 usually allows the mutex to be recovered after a child process
3010 terminates abnormally while holding a mutex.</p>
3011 <p>If your system implements the
3012 <code>pthread_mutexattr_setrobust_np()</code> function, you may be able
3013 to use the <code>pthread</code> option safely.</p>
3017 <li><code>fcntl:/path/to/mutex</code>
3018 <p>This is a mutex variant where a physical (lock-)file and the
3019 <code>fcntl()</code> function are used as the mutex.</p>
3021 <div class="warning"><h3>Warning</h3>
3022 <p>When multiple mutexes based on this mechanism are used within
3023 multi-threaded, multi-process environments, deadlock errors (EDEADLK)
3024 can be reported for valid mutex operations if <code>fcntl()</code>
3025 is not thread-aware, such as on Solaris.</p>
3029 <li><code>flock:/path/to/mutex</code>
3030 <p>This is similar to the <code>fcntl:/path/to/mutex</code> method
3031 with the exception that the <code>flock()</code> function is used to
3032 provide file locking.</p></li>
3034 <li><code>file:/path/to/mutex</code>
3035 <p>This selects the "best" available file locking implementation,
3036 choosing between <code>fcntl</code> and <code>flock</code>, in that
3040 <p>Most mechanisms are only available on selected platforms, where the
3041 underlying platform and <a class="glossarylink" href="../glossary.html#apr" title="ver glosario">APR</a> support it. Mechanisms
3042 which aren't available on all platforms are <em>posixsem</em>,
3043 <em>sysvsem</em>, <em>sem</em>, <em>pthread</em>, <em>fcntl</em>,
3044 <em>flock</em>, and <em>file</em>.</p>
3046 <p>With the file-based mechanisms <em>fcntl</em> and <em>flock</em>,
3047 the path, if provided, is a directory where the lock file will be created.
3048 The default directory is httpd's run-time file directory relative to
3049 <code class="directive"><a href="#serverroot">ServerRoot</a></code>. Always use a local disk
3050 filesystem for <code>/path/to/mutex</code> and never a directory residing
3051 on a NFS- or AFS-filesystem. The basename of the file will be the mutex
3052 type, an optional instance string provided by the module, and unless the
3053 <code>OmitPID</code> keyword is specified, the process id of the httpd
3054 parent process will be appended to to make the file name unique, avoiding
3055 conflicts when multiple httpd instances share a lock file directory. For
3056 example, if the mutex name is <code>mpm-accept</code> and the lock file
3057 directory is <code>/var/httpd/locks</code>, the lock file name for the
3058 httpd instance with parent process id 12345 would be
3059 <code>/var/httpd/locks/mpm-accept.12345</code>.</p>
3061 <div class="warning"><h3>Security</h3>
3062 <p>It is best to <em>avoid</em> putting mutex files in a world-writable
3063 directory such as <code>/var/tmp</code> because someone could create
3064 a denial of service attack and prevent the server from starting by
3065 creating a lockfile with the same name as the one the server will try
3069 <p>The following table documents the names of mutexes used by httpd
3070 and bundled modules.</p>
3072 <table class="bordered"><tr class="header">
3075 <th>Protected resource</th>
3078 <td><code>mpm-accept</code></td>
3079 <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>
3080 <td>incoming connections, to avoid the thundering herd problem;
3081 for more information, refer to the
3082 <a href="../misc/perf-tuning.html">performance tuning</a>
3086 <td><code>authdigest-client</code></td>
3087 <td><code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code></td>
3088 <td>client list in shared memory</td>
3091 <td><code>authdigest-opaque</code></td>
3092 <td><code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code></td>
3093 <td>counter in shared memory</td>
3096 <td><code>ldap-cache</code></td>
3097 <td><code class="module"><a href="../mod/mod_ldap.html">mod_ldap</a></code></td>
3098 <td>LDAP result cache</td>
3101 <td><code>rewrite-map</code></td>
3102 <td><code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code></td>
3103 <td>communication with external mapping programs, to avoid
3104 intermixed I/O from multiple requests</td>
3107 <td><code>ssl-cache</code></td>
3108 <td><code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code></td>
3109 <td>SSL session cache</td>
3112 <td><code>ssl-stapling</code></td>
3113 <td><code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code></td>
3114 <td>OCSP stapling response cache</td>
3117 <td><code>watchdog-callback</code></td>
3118 <td><code class="module"><a href="../mod/mod_watchdog.html">mod_watchdog</a></code></td>
3119 <td>callback function of a particular client module</td>
3123 <p>The <code>OmitPID</code> keyword suppresses the addition of the httpd
3124 parent process id from the lock file name.</p>
3126 <p>In the following example, the mutex mechanism for the MPM accept
3127 mutex will be changed from the compiled-in default to <code>fcntl</code>,
3128 with the associated lock file created in directory
3129 <code>/var/httpd/locks</code>. The mutex mechanism for all other mutexes
3130 will be changed from the compiled-in default to <code>sysvsem</code>.</p>
3132 <div class="example"><p><code>
3133 Mutex default sysvsem<br />
3134 Mutex mpm-accept fcntl:/var/httpd/locks
3138 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3139 <div class="directive-section"><h2><a name="NameVirtualHost" id="NameVirtualHost">NameVirtualHost</a> <a name="namevirtualhost" id="namevirtualhost">Directiva</a></h2>
3140 <table class="directive">
3141 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Designates an IP address for name-virtual
3143 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>NameVirtualHost <var>addr</var>[:<var>port</var>]</code></td></tr>
3144 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
3145 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3146 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3149 <p>A single <code class="directive">NameVirtualHost</code> directive
3150 identifies a set of identical virtual hosts on which the server will
3151 further select from on the basis of the <em>hostname</em>
3152 requested by the client. The <code class="directive">NameVirtualHost</code>
3153 directive is a required directive if you want to configure
3154 <a href="../vhosts/">name-based virtual hosts</a>.</p>
3156 <p>This directive, and the corresponding <code class="directive">VirtualHost</code>,
3157 <em>must</em> be qualified with a port number if the server supports both HTTP
3158 and HTTPS connections.</p>
3160 <p>Although <var>addr</var> can be a hostname, it is recommended
3161 that you always use an IP address or a wildcard. A wildcard
3162 NameVirtualHost matches only virtualhosts that also have a literal wildcard
3163 as their argument.</p>
3165 <p>In cases where a firewall or other proxy receives the requests and
3166 forwards them on a different IP address to the server, you must specify the
3167 IP address of the physical interface on the machine which will be
3168 servicing the requests. </p>
3170 <p> In the example below, requests received on interface 192.0.2.1 and port 80
3171 will only select among the first two virtual hosts. Requests received on
3172 port 80 on any other interface will only select among the third and fourth
3173 virtual hosts. In the common case where the interface isn't important
3174 to the mapping, only the "*:80" NameVirtualHost and VirtualHost directives
3177 <div class="example"><p><code>
3178 NameVirtualHost 192.0.2.1:80<br />
3179 NameVirtualHost *:80<br /><br />
3181 <VirtualHost 192.0.2.1:80><br />
3182 ServerName namebased-a.example.com<br />
3183 </VirtualHost><br />
3185 <VirtualHost 192.0.2.1:80><br />
3186 Servername namebased-b.example.com<br />
3187 </VirtualHost><br />
3189 <VirtualHost *:80><br />
3190 ServerName namebased-c.example.com <br />
3191 </VirtualHost><br />
3193 <VirtualHost *:80><br />
3194 ServerName namebased-d.example.com <br />
3195 </VirtualHost><br />
3200 <p>If no matching virtual host is found, then the first listed
3201 virtual host that matches the IP address and port will be used.</p>
3204 <p>IPv6 addresses must be enclosed in square brackets, as shown
3205 in the following example:</p>
3207 <div class="example"><p><code>
3208 NameVirtualHost [2001:db8::a00:20ff:fea7:ccea]:8080
3211 <div class="note"><h3>Argument to <code class="directive"><VirtualHost></code>
3213 <p>Note that the argument to the <code class="directive"><VirtualHost></code> directive must
3214 exactly match the argument to the <code class="directive">NameVirtualHost</code> directive.</p>
3216 <div class="example"><p><code>
3217 NameVirtualHost 192.0.2.2:80<br />
3218 <VirtualHost 192.0.2.2:80><br />
3220 </VirtualHost><br />
3224 <h3>Consulte también</h3>
3226 <li><a href="../vhosts/">Virtual Hosts
3227 documentation</a></li>
3230 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3231 <div class="directive-section"><h2><a name="Options" id="Options">Options</a> <a name="options" id="options">Directiva</a></h2>
3232 <table class="directive">
3233 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures what features are available in a particular
3235 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Options
3236 [+|-]<var>option</var> [[+|-]<var>option</var>] ...</code></td></tr>
3237 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Options All</code></td></tr>
3238 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3239 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>Options</td></tr>
3240 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3241 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3243 <p>The <code class="directive">Options</code> directive controls which
3244 server features are available in a particular directory.</p>
3246 <p><var>option</var> can be set to <code>None</code>, in which
3247 case none of the extra features are enabled, or one or more of
3251 <dt><code>All</code></dt>
3253 <dd>All options except for <code>MultiViews</code>. This is the default
3256 <dt><code>ExecCGI</code></dt>
3259 Execution of CGI scripts using <code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code>
3262 <dt><code>FollowSymLinks</code></dt>
3266 The server will follow symbolic links in this directory.
3268 <p>Even though the server follows the symlink it does <em>not</em>
3269 change the pathname used to match against <code class="directive"><a href="#directory"><Directory></a></code> sections.</p>
3270 <p>Note also, that this option <strong>gets ignored</strong> if set
3271 inside a <code class="directive"><a href="#location"><Location></a></code>
3273 <p>Omitting this option should not be considered a security restriction,
3274 since symlink testing is subject to race conditions that make it
3278 <dt><code>Includes</code></dt>
3281 Server-side includes provided by <code class="module"><a href="../mod/mod_include.html">mod_include</a></code>
3284 <dt><code>IncludesNOEXEC</code></dt>
3288 Server-side includes are permitted, but the <code>#exec
3289 cmd</code> and <code>#exec cgi</code> are disabled. It is still
3290 possible to <code>#include virtual</code> CGI scripts from
3291 <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code>ed
3294 <dt><code>Indexes</code></dt>
3297 If a URL which maps to a directory is requested, and there
3298 is no <code class="directive"><a href="../mod/mod_dir.html#directoryindex">DirectoryIndex</a></code>
3299 (<em>e.g.</em>, <code>index.html</code>) in that directory, then
3300 <code class="module"><a href="../mod/mod_autoindex.html">mod_autoindex</a></code> will return a formatted listing
3301 of the directory.</dd>
3303 <dt><code>MultiViews</code></dt>
3306 <a href="../content-negotiation.html">Content negotiated</a>
3307 "MultiViews" are allowed using
3308 <code class="module"><a href="../mod/mod_negotiation.html">mod_negotiation</a></code>.
3309 <div class="note"><h3>Note</h3> <p>This option gets ignored if set
3310 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>
3311 needs real resources to compare against and evaluate from.</p></div>
3314 <dt><code>SymLinksIfOwnerMatch</code></dt>
3316 <dd>The server will only follow symbolic links for which the
3317 target file or directory is owned by the same user id as the
3320 <div class="note"><h3>Note</h3> <p>This option gets ignored if
3321 set inside a <code class="directive"><a href="#location"><Location></a></code> section.</p>
3322 <p>This option should not be considered a security restriction,
3323 since symlink testing is subject to race conditions that make it
3324 circumventable.</p></div>
3328 <p>Normally, if multiple <code class="directive">Options</code> could
3329 apply to a directory, then the most specific one is used and
3330 others are ignored; the options are not merged. (See <a href="../sections.html#mergin">how sections are merged</a>.)
3331 However if <em>all</em> the options on the
3332 <code class="directive">Options</code> directive are preceded by a
3333 <code>+</code> or <code>-</code> symbol, the options are
3334 merged. Any options preceded by a <code>+</code> are added to the
3335 options currently in force, and any options preceded by a
3336 <code>-</code> are removed from the options currently in
3339 <div class="warning"><h3>Warning</h3>
3340 <p>Mixing <code class="directive">Options</code> with a <code>+</code> or
3341 <code>-</code> with those without is not valid syntax, and is likely
3342 to cause unexpected results.</p>
3345 <p>For example, without any <code>+</code> and <code>-</code> symbols:</p>
3347 <div class="example"><p><code>
3348 <Directory /web/docs><br />
3349 <span class="indent">
3350 Options Indexes FollowSymLinks<br />
3352 </Directory><br />
3354 <Directory /web/docs/spec><br />
3355 <span class="indent">
3356 Options Includes<br />
3361 <p>then only <code>Includes</code> will be set for the
3362 <code>/web/docs/spec</code> directory. However if the second
3363 <code class="directive">Options</code> directive uses the <code>+</code> and
3364 <code>-</code> symbols:</p>
3366 <div class="example"><p><code>
3367 <Directory /web/docs><br />
3368 <span class="indent">
3369 Options Indexes FollowSymLinks<br />
3371 </Directory><br />
3373 <Directory /web/docs/spec><br />
3374 <span class="indent">
3375 Options +Includes -Indexes<br />
3380 <p>then the options <code>FollowSymLinks</code> and
3381 <code>Includes</code> are set for the <code>/web/docs/spec</code>
3384 <div class="note"><h3>Note</h3>
3385 <p>Using <code>-IncludesNOEXEC</code> or
3386 <code>-Includes</code> disables server-side includes completely
3387 regardless of the previous setting.</p>
3390 <p>The default in the absence of any other settings is
3391 <code>All</code>.</p>
3394 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3395 <div class="directive-section"><h2><a name="Protocol" id="Protocol">Protocol</a> <a name="protocol" id="protocol">Directiva</a></h2>
3396 <table class="directive">
3397 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Protocol for a listening socket</td></tr>
3398 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Protocol <var>protocol</var></code></td></tr>
3399 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
3400 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3401 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3402 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache 2.1.5 and later.
3403 On Windows from Apache 2.3.3 and later.</td></tr>
3405 <p>This directive specifies the protocol used for a specific listening socket.
3406 The protocol is used to determine which module should handle a request, and
3407 to apply protocol specific optimizations with the <code class="directive">AcceptFilter</code>
3410 <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>
3412 <p>For example, if you are running <code>https</code> on a non-standard port, specify the protocol explicitly:</p>
3414 <div class="example"><p><code>
3418 <p>You can also specify the protocol using the <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> directive.</p>
3420 <h3>Consulte también</h3>
3422 <li><code class="directive">AcceptFilter</code></li>
3423 <li><code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code></li>
3426 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3427 <div class="directive-section"><h2><a name="Protocols" id="Protocols">Protocols</a> <a name="protocols" id="protocols">Directiva</a></h2>
3428 <table class="directive">
3429 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Protocols available for a server/virtual host</td></tr>
3430 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Protocols <var>protocol</var> ...</code></td></tr>
3431 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Protocols http/1.1</code></td></tr>
3432 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
3433 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3434 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3435 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Only available from Apache 2.4.17 and later.</td></tr>
3436 </table><p>The documentation for this directive has
3437 not been translated yet. Please have a look at the English
3438 version.</p><h3>Consulte también</h3>
3440 <li><code class="directive"><a href="#protocolshonororder">ProtocolsHonorOrder</a></code></li>
3443 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3444 <div class="directive-section"><h2><a name="ProtocolsHonorOrder" id="ProtocolsHonorOrder">ProtocolsHonorOrder</a> <a name="protocolshonororder" id="protocolshonororder">Directiva</a></h2>
3445 <table class="directive">
3446 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determines if order of Protocols determines precedence during negotiation</td></tr>
3447 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ProtocolsHonorOrder On|Off</code></td></tr>
3448 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ProtocolsHonorOrder On</code></td></tr>
3449 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
3450 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3451 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3452 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Only available from Apache 2.4.17 and later.</td></tr>
3453 </table><p>The documentation for this directive has
3454 not been translated yet. Please have a look at the English
3455 version.</p><h3>Consulte también</h3>
3457 <li><code class="directive"><a href="#protocols">Protocols</a></code></li>
3460 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3461 <div class="directive-section"><h2><a name="QualifyRedirectURL" id="QualifyRedirectURL">QualifyRedirectURL</a> <a name="qualifyredirecturl" id="qualifyredirecturl">Directiva</a></h2>
3462 <table class="directive">
3463 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Controls whether the REDIRECT_URL environment variable is
3464 fully qualified</td></tr>
3465 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>QualifyRedirectURL ON|OFF</code></td></tr>
3466 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>QualifyRedirectURL OFF</code></td></tr>
3467 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
3468 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
3469 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3470 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3471 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Directive supported in 2.4.18 and later. 2.4.17 acted
3472 as if 'QualifyRedirectURL ON' was configured.</td></tr>
3473 </table><p>The documentation for this directive has
3474 not been translated yet. Please have a look at the English
3476 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3477 <div class="directive-section"><h2><a name="RegisterHttpMethod" id="RegisterHttpMethod">RegisterHttpMethod</a> <a name="registerhttpmethod" id="registerhttpmethod">Directiva</a></h2>
3478 <table class="directive">
3479 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Register non-standard HTTP methods</td></tr>
3480 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>RegisterHttpMethod <var>method</var> [<var>method</var> [...]]</code></td></tr>
3481 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
3482 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3483 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</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="RLimitCPU" id="RLimitCPU">RLimitCPU</a> <a name="rlimitcpu" id="rlimitcpu">Directiva</a></h2>
3489 <table class="directive">
3490 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the CPU consumption of processes launched
3491 by Apache httpd children</td></tr>
3492 <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>
3493 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Unset; uses operating system defaults</code></td></tr>
3494 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3495 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
3496 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3497 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3499 <p>Takes 1 or 2 parameters. The first parameter sets the soft
3500 resource limit for all processes and the second parameter sets
3501 the maximum resource limit. Either parameter can be a number,
3502 or <code>max</code> to indicate to the server that the limit should
3503 be set to the maximum allowed by the operating system
3504 configuration. Raising the maximum resource limit requires that
3505 the server is running as <code>root</code>, or in the initial startup
3508 <p>This applies to processes forked off from Apache httpd children
3509 servicing requests, not the Apache httpd children themselves. This
3510 includes CGI scripts and SSI exec commands, but not any
3511 processes forked off from the Apache httpd parent such as piped
3514 <p>CPU resource limits are expressed in seconds per
3517 <h3>Consulte también</h3>
3519 <li><code class="directive"><a href="#rlimitmem">RLimitMEM</a></code></li>
3520 <li><code class="directive"><a href="#rlimitnproc">RLimitNPROC</a></code></li>
3523 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3524 <div class="directive-section"><h2><a name="RLimitMEM" id="RLimitMEM">RLimitMEM</a> <a name="rlimitmem" id="rlimitmem">Directiva</a></h2>
3525 <table class="directive">
3526 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the memory consumption of processes launched
3527 by Apache httpd children</td></tr>
3528 <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>
3529 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Unset; uses operating system defaults</code></td></tr>
3530 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3531 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
3532 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3533 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3535 <p>Takes 1 or 2 parameters. The first parameter sets the soft
3536 resource limit for all processes and the second parameter sets
3537 the maximum resource limit. Either parameter can be a number,
3538 or <code>max</code> to indicate to the server that the limit should
3539 be set to the maximum allowed by the operating system
3540 configuration. Raising the maximum resource limit requires that
3541 the server is running as <code>root</code>, or in the initial startup
3544 <p>This applies to processes forked off from Apache httpd children
3545 servicing requests, not the Apache httpd children themselves. This
3546 includes CGI scripts and SSI exec commands, but not any
3547 processes forked off from the Apache httpd parent such as piped
3550 <p>Memory resource limits are expressed in bytes per
3553 <h3>Consulte también</h3>
3555 <li><code class="directive"><a href="#rlimitcpu">RLimitCPU</a></code></li>
3556 <li><code class="directive"><a href="#rlimitnproc">RLimitNPROC</a></code></li>
3559 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3560 <div class="directive-section"><h2><a name="RLimitNPROC" id="RLimitNPROC">RLimitNPROC</a> <a name="rlimitnproc" id="rlimitnproc">Directiva</a></h2>
3561 <table class="directive">
3562 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the number of processes that can be launched by
3563 processes launched by Apache httpd children</td></tr>
3564 <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>
3565 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Unset; uses operating system defaults</code></td></tr>
3566 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3567 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
3568 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3569 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3571 <p>Takes 1 or 2 parameters. The first parameter sets the soft
3572 resource limit for all processes and the second parameter sets
3573 the maximum resource limit. Either parameter can be a number,
3574 or <code>max</code> to indicate to the server that the limit
3575 should be set to the maximum allowed by the operating system
3576 configuration. Raising the maximum resource limit requires that
3577 the server is running as <code>root</code>, or in the initial startup
3580 <p>This applies to processes forked off from Apache httpd children
3581 servicing requests, not the Apache httpd children themselves. This
3582 includes CGI scripts and SSI exec commands, but not any
3583 processes forked off from the Apache httpd parent such as piped
3586 <p>Process limits control the number of processes per user.</p>
3588 <div class="note"><h3>Note</h3>
3589 <p>If CGI processes are <strong>not</strong> running
3590 under user ids other than the web server user id, this directive
3591 will limit the number of processes that the server itself can
3592 create. Evidence of this situation will be indicated by
3593 <strong><code>cannot fork</code></strong> messages in the
3594 <code>error_log</code>.</p>
3597 <h3>Consulte también</h3>
3599 <li><code class="directive"><a href="#rlimitmem">RLimitMEM</a></code></li>
3600 <li><code class="directive"><a href="#rlimitcpu">RLimitCPU</a></code></li>
3603 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3604 <div class="directive-section"><h2><a name="ScriptInterpreterSource" id="ScriptInterpreterSource">ScriptInterpreterSource</a> <a name="scriptinterpretersource" id="scriptinterpretersource">Directiva</a></h2>
3605 <table class="directive">
3606 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Technique for locating the interpreter for CGI
3608 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ScriptInterpreterSource Registry|Registry-Strict|Script</code></td></tr>
3609 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ScriptInterpreterSource Script</code></td></tr>
3610 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3611 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
3612 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3613 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3614 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Win32 only;
3615 option <code>Registry-Strict</code> is available in Apache HTTP Server 2.0 and
3618 <p>This directive is used to control how Apache httpd finds the
3619 interpreter used to run CGI scripts. The default setting is
3620 <code>Script</code>. This causes Apache httpd to use the interpreter pointed to
3621 by the shebang line (first line, starting with <code>#!</code>) in the
3622 script. On Win32 systems this line usually looks like:</p>
3624 <div class="example"><p><code>
3625 #!C:/Perl/bin/perl.exe
3628 <p>or, if <code>perl</code> is in the <code>PATH</code>, simply:</p>
3630 <div class="example"><p><code>
3634 <p>Setting <code>ScriptInterpreterSource Registry</code> will
3635 cause the Windows Registry tree <code>HKEY_CLASSES_ROOT</code> to be
3636 searched using the script file extension (e.g., <code>.pl</code>) as a
3637 search key. The command defined by the registry subkey
3638 <code>Shell\ExecCGI\Command</code> or, if it does not exist, by the subkey
3639 <code>Shell\Open\Command</code> is used to open the script file. If the
3640 registry keys cannot be found, Apache httpd falls back to the behavior of the
3641 <code>Script</code> option.</p>
3643 <div class="warning"><h3>Security</h3>
3644 <p>Be careful when using <code>ScriptInterpreterSource
3645 Registry</code> with <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code>'ed directories, because
3646 Apache httpd will try to execute <strong>every</strong> file within this
3647 directory. The <code>Registry</code> setting may cause undesired
3648 program calls on files which are typically not executed. For
3649 example, the default open command on <code>.htm</code> files on
3650 most Windows systems will execute Microsoft Internet Explorer, so
3651 any HTTP request for an <code>.htm</code> file existing within the
3652 script directory would start the browser in the background on the
3653 server. This is a good way to crash your system within a minute or
3657 <p>The option <code>Registry-Strict</code> which is new in Apache HTTP Server
3658 2.0 does the same thing as <code>Registry</code> but uses only the
3659 subkey <code>Shell\ExecCGI\Command</code>. The
3660 <code>ExecCGI</code> key is not a common one. It must be
3661 configured manually in the windows registry and hence prevents
3662 accidental program calls on your system.</p>
3665 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3666 <div class="directive-section"><h2><a name="SeeRequestTail" id="SeeRequestTail">SeeRequestTail</a> <a name="seerequesttail" id="seerequesttail">Directiva</a></h2>
3667 <table class="directive">
3668 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determine if mod_status displays the first 63 characters
3669 of a request or the last 63, assuming the request itself is greater than
3671 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>SeeRequestTail On|Off</code></td></tr>
3672 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>SeeRequestTail Off</code></td></tr>
3673 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
3674 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3675 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3676 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache httpd 2.2.7 and later.</td></tr>
3678 <p>mod_status with <code>ExtendedStatus On</code>
3679 displays the actual request being handled.
3680 For historical purposes, only 63 characters of the request
3681 are actually stored for display purposes. This directive
3682 controls whether the 1st 63 characters are stored (the previous
3683 behavior and the default) or if the last 63 characters are. This
3684 is only applicable, of course, if the length of the request is
3685 64 characters or greater.</p>
3687 <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:
3690 <table class="bordered">
3692 <th>Off (default)</th>
3693 <td>GET /disk1/storage/apache/htdocs/images/imagestore1/food/apples</td>
3697 <td>orage/apache/htdocs/images/imagestore1/food/apples.jpg HTTP/1.1</td>
3703 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3704 <div class="directive-section"><h2><a name="ServerAdmin" id="ServerAdmin">ServerAdmin</a> <a name="serveradmin" id="serveradmin">Directiva</a></h2>
3705 <table class="directive">
3706 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Email address that the server includes in error
3707 messages sent to the client</td></tr>
3708 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ServerAdmin <var>email-address</var>|<var>URL</var></code></td></tr>
3709 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
3710 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3711 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3713 <p>The <code class="directive">ServerAdmin</code> sets the contact address
3714 that the server includes in any error messages it returns to the
3715 client. If the <code>httpd</code> doesn't recognize the supplied argument
3717 assumes, that it's an <var>email-address</var> and prepends it with
3718 <code>mailto:</code> in hyperlink targets. However, it's recommended to
3719 actually use an email address, since there are a lot of CGI scripts that
3720 make that assumption. If you want to use an URL, it should point to another
3721 server under your control. Otherwise users may not be able to contact you in
3724 <p>It may be worth setting up a dedicated address for this, e.g.</p>
3726 <div class="example"><p><code>
3727 ServerAdmin www-admin@foo.example.com
3729 <p>as users do not always mention that they are talking about the
3733 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3734 <div class="directive-section"><h2><a name="ServerAlias" id="ServerAlias">ServerAlias</a> <a name="serveralias" id="serveralias">Directiva</a></h2>
3735 <table class="directive">
3736 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Alternate names for a host used when matching requests
3737 to name-virtual hosts</td></tr>
3738 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ServerAlias <var>hostname</var> [<var>hostname</var>] ...</code></td></tr>
3739 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>virtual host</td></tr>
3740 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3741 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3743 <p>The <code class="directive">ServerAlias</code> directive sets the
3744 alternate names for a host, for use with <a href="../vhosts/name-based.html">name-based virtual hosts</a>. The
3745 <code class="directive">ServerAlias</code> may include wildcards, if appropriate.</p>
3747 <div class="example"><p><code>
3748 <VirtualHost *:80><br />
3749 ServerName server.domain.com<br />
3750 ServerAlias server server2.domain.com server2<br />
3751 ServerAlias *.example.com<br />
3752 UseCanonicalName Off<br />
3754 </VirtualHost>
3757 <h3>Consulte también</h3>
3759 <li><code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code></li>
3760 <li><a href="../vhosts/">Apache HTTP Server Virtual Host documentation</a></li>
3763 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3764 <div class="directive-section"><h2><a name="ServerName" id="ServerName">ServerName</a> <a name="servername" id="servername">Directiva</a></h2>
3765 <table class="directive">
3766 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Hostname and port that the server uses to identify
3768 <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>
3769 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
3770 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3771 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3773 <p>The <code class="directive">ServerName</code> directive sets the
3774 request scheme, hostname and
3775 port that the server uses to identify itself. This is used when
3776 creating redirection URLs.</p>
3778 <p>Additionally, <code class="directive">ServerName</code> is used (possibly
3779 in conjunction with <code class="directive">ServerAlias</code>) to uniquely
3780 identify a virtual host, when using <a href="../vhosts/name-based.html">name-based virtual hosts</a>.</p>
3782 <p>For example, if the name of the
3783 machine hosting the web server is <code>simple.example.com</code>,
3784 but the machine also has the DNS alias <code>www.example.com</code>
3785 and you wish the web server to be so identified, the following
3786 directive should be used:</p>
3788 <div class="example"><p><code>
3789 ServerName www.example.com:80
3792 <p>The <code class="directive">ServerName</code> directive
3793 may appear anywhere within the definition of a server. However,
3794 each appearance overrides the previous appearance (within that
3797 <p>If no <code class="directive">ServerName</code> is specified, then the
3798 server attempts to deduce the hostname by performing a reverse
3799 lookup on the IP address. If no port is specified in the
3800 <code class="directive">ServerName</code>, then the server will use the
3801 port from the incoming request. For optimal reliability and
3802 predictability, you should specify an explicit hostname and port
3803 using the <code class="directive">ServerName</code> directive.</p>
3805 <p>If you are using <a href="../vhosts/name-based.html">name-based virtual hosts</a>,
3806 the <code class="directive">ServerName</code> inside a
3807 <code class="directive"><a href="#virtualhost"><VirtualHost></a></code>
3808 section specifies what hostname must appear in the request's
3809 <code>Host:</code> header to match this virtual host.</p>
3811 <p>Sometimes, the server runs behind a device that processes SSL,
3812 such as a reverse proxy, load balancer or SSL offload
3813 appliance. When this is the case, specify the
3814 <code>https://</code> scheme and the port number to which the
3815 clients connect in the <code class="directive">ServerName</code> directive
3816 to make sure that the server generates the correct
3817 self-referential URLs.
3820 <p>See the description of the
3821 <code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code> and
3822 <code class="directive"><a href="#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></code> directives for
3823 settings which determine whether self-referential URLs (e.g., by the
3824 <code class="module"><a href="../mod/mod_dir.html">mod_dir</a></code> module) will refer to the
3825 specified port, or to the port number given in the client's request.
3828 <div class="warning">
3829 <p>Failure to set <code class="directive">ServerName</code> to a name that
3830 your server can resolve to an IP address will result in a startup
3831 warning. <code>httpd</code> will then use whatever hostname it can
3832 determine, using the system's <code>hostname</code> command. This
3833 will almost never be the hostname you actually want.</p>
3834 <div class="example"><p><code>
3835 httpd: Could not reliably determine the server's fully qualified domain name, using rocinante.local for ServerName
3840 <h3>Consulte también</h3>
3842 <li><a href="../dns-caveats.html">Issues Regarding DNS and
3843 Apache HTTP Server</a></li>
3844 <li><a href="../vhosts/">Apache HTTP Server virtual host
3845 documentation</a></li>
3846 <li><code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code></li>
3847 <li><code class="directive"><a href="#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></code></li>
3848 <li><code class="directive"><a href="#namevirtualhost">NameVirtualHost</a></code></li>
3849 <li><code class="directive"><a href="#serveralias">ServerAlias</a></code></li>
3852 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3853 <div class="directive-section"><h2><a name="ServerPath" id="ServerPath">ServerPath</a> <a name="serverpath" id="serverpath">Directiva</a></h2>
3854 <table class="directive">
3855 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Legacy URL pathname for a name-based virtual host that
3856 is accessed by an incompatible browser</td></tr>
3857 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ServerPath <var>URL-path</var></code></td></tr>
3858 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>virtual host</td></tr>
3859 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3860 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3862 <p>The <code class="directive">ServerPath</code> directive sets the legacy
3863 URL pathname for a host, for use with <a href="../vhosts/">name-based virtual hosts</a>.</p>
3865 <h3>Consulte también</h3>
3867 <li><a href="../vhosts/">Apache HTTP Server Virtual Host documentation</a></li>
3870 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3871 <div class="directive-section"><h2><a name="ServerRoot" id="ServerRoot">ServerRoot</a> <a name="serverroot" id="serverroot">Directiva</a></h2>
3872 <table class="directive">
3873 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Base directory for the server installation</td></tr>
3874 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ServerRoot <var>directory-path</var></code></td></tr>
3875 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ServerRoot /usr/local/apache</code></td></tr>
3876 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
3877 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3878 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3880 <p>The <code class="directive">ServerRoot</code> directive sets the
3881 directory in which the server lives. Typically it will contain the
3882 subdirectories <code>conf/</code> and <code>logs/</code>. Relative
3883 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
3884 relative to this directory.</p>
3886 <div class="example"><h3>Example</h3><p><code>
3887 ServerRoot /home/httpd
3891 <h3>Consulte también</h3>
3893 <li><a href="../invoking.html">the <code>-d</code>
3894 option to <code>httpd</code></a></li>
3895 <li><a href="../misc/security_tips.html#serverroot">the
3896 security tips</a> for information on how to properly set
3897 permissions on the <code class="directive">ServerRoot</code></li>
3900 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3901 <div class="directive-section"><h2><a name="ServerSignature" id="ServerSignature">ServerSignature</a> <a name="serversignature" id="serversignature">Directiva</a></h2>
3902 <table class="directive">
3903 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures the footer on server-generated documents</td></tr>
3904 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ServerSignature On|Off|EMail</code></td></tr>
3905 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ServerSignature Off</code></td></tr>
3906 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3907 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
3908 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3909 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3911 <p>The <code class="directive">ServerSignature</code> directive allows the
3912 configuration of a trailing footer line under server-generated
3913 documents (error messages, <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> ftp directory
3914 listings, <code class="module"><a href="../mod/mod_info.html">mod_info</a></code> output, ...). The reason why you
3915 would want to enable such a footer line is that in a chain of proxies,
3916 the user often has no possibility to tell which of the chained servers
3917 actually produced a returned error message.</p>
3919 <p>The <code>Off</code>
3920 setting, which is the default, suppresses the footer line (and is
3921 therefore compatible with the behavior of Apache-1.2 and
3922 below). The <code>On</code> setting simply adds a line with the
3923 server version number and <code class="directive"><a href="#servername">ServerName</a></code> of the serving virtual host,
3924 and the <code>EMail</code> setting additionally creates a
3925 "mailto:" reference to the <code class="directive"><a href="#serveradmin">ServerAdmin</a></code> of the referenced
3928 <p>After version 2.0.44, the details of the server version number
3929 presented are controlled by the <code class="directive"><a href="#servertokens">ServerTokens</a></code> directive.</p>
3931 <h3>Consulte también</h3>
3933 <li><code class="directive"><a href="#servertokens">ServerTokens</a></code></li>
3936 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3937 <div class="directive-section"><h2><a name="ServerTokens" id="ServerTokens">ServerTokens</a> <a name="servertokens" id="servertokens">Directiva</a></h2>
3938 <table class="directive">
3939 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures the <code>Server</code> HTTP response
3941 <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>
3942 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ServerTokens Full</code></td></tr>
3943 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
3944 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3945 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3947 <p>This directive controls whether <code>Server</code> response
3948 header field which is sent back to clients includes a
3949 description of the generic OS-type of the server as well as
3950 information about compiled-in modules.</p>
3953 <dt><code>ServerTokens Full</code> (or not specified)</dt>
3955 <dd>Server sends (<em>e.g.</em>): <code>Server: Apache/2.4.1
3956 (Unix) PHP/4.2.2 MyMod/1.2</code></dd>
3958 <dt><code>ServerTokens Prod[uctOnly]</code></dt>
3960 <dd>Server sends (<em>e.g.</em>): <code>Server:
3963 <dt><code>ServerTokens Major</code></dt>
3965 <dd>Server sends (<em>e.g.</em>): <code>Server:
3966 Apache/2</code></dd>
3968 <dt><code>ServerTokens Minor</code></dt>
3970 <dd>Server sends (<em>e.g.</em>): <code>Server:
3971 Apache/2.4</code></dd>
3973 <dt><code>ServerTokens Min[imal]</code></dt>
3975 <dd>Server sends (<em>e.g.</em>): <code>Server:
3976 Apache/2.4.1</code></dd>
3978 <dt><code>ServerTokens OS</code></dt>
3980 <dd>Server sends (<em>e.g.</em>): <code>Server: Apache/2.4.1
3985 <p>This setting applies to the entire server, and cannot be
3986 enabled or disabled on a virtualhost-by-virtualhost basis.</p>
3988 <p>After version 2.0.44, this directive also controls the
3989 information presented by the <code class="directive"><a href="#serversignature">ServerSignature</a></code> directive.</p>
3991 <div class="note">Setting <code class="directive">ServerTokens</code> to less than
3992 <code>minimal</code> is not recommended because it makes it more
3993 difficult to debug interoperational problems. Also note that
3994 disabling the Server: header does nothing at all to make your
3995 server more secure; the idea of "security through obscurity"
3996 is a myth and leads to a false sense of safety.</div>
3999 <h3>Consulte también</h3>
4001 <li><code class="directive"><a href="#serversignature">ServerSignature</a></code></li>
4004 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4005 <div class="directive-section"><h2><a name="SetHandler" id="SetHandler">SetHandler</a> <a name="sethandler" id="sethandler">Directiva</a></h2>
4006 <table class="directive">
4007 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Forces all matching files to be processed by a
4009 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>SetHandler <var>handler-name</var>|None</code></td></tr>
4010 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
4011 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
4012 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4013 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4014 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Moved into the core in Apache httpd 2.0</td></tr>
4016 <p>When placed into an <code>.htaccess</code> file or a
4017 <code class="directive"><a href="#directory"><Directory></a></code> or
4018 <code class="directive"><a href="#location"><Location></a></code>
4019 section, this directive forces all matching files to be parsed
4020 through the <a href="../handler.html">handler</a> given by
4021 <var>handler-name</var>. For example, if you had a directory you
4022 wanted to be parsed entirely as imagemap rule files, regardless
4023 of extension, you might put the following into an
4024 <code>.htaccess</code> file in that directory:</p>
4026 <div class="example"><p><code>
4027 SetHandler imap-file
4030 <p>Another example: if you wanted to have the server display a
4031 status report whenever a URL of
4032 <code>http://servername/status</code> was called, you might put
4033 the following into <code>httpd.conf</code>:</p>
4035 <div class="example"><p><code>
4036 <Location /status><br />
4037 <span class="indent">
4038 SetHandler server-status<br />
4043 <p>You can override an earlier defined <code class="directive">SetHandler</code>
4044 directive by using the value <code>None</code>.</p>
4045 <p><strong>Note:</strong> because SetHandler overrides default handlers,
4046 normal behaviour such as handling of URLs ending in a slash (/) as
4047 directories or index files is suppressed.</p>
4049 <h3>Consulte también</h3>
4051 <li><code class="directive"><a href="../mod/mod_mime.html#addhandler">AddHandler</a></code></li>
4054 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4055 <div class="directive-section"><h2><a name="SetInputFilter" id="SetInputFilter">SetInputFilter</a> <a name="setinputfilter" id="setinputfilter">Directiva</a></h2>
4056 <table class="directive">
4057 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Sets the filters that will process client requests and POST
4059 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>SetInputFilter <var>filter</var>[;<var>filter</var>...]</code></td></tr>
4060 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
4061 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
4062 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4063 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4065 <p>The <code class="directive">SetInputFilter</code> directive sets the
4066 filter or filters which will process client requests and POST
4067 input when they are received by the server. This is in addition to
4068 any filters defined elsewhere, including the
4069 <code class="directive"><a href="../mod/mod_mime.html#addinputfilter">AddInputFilter</a></code>
4072 <p>If more than one filter is specified, they must be separated
4073 by semicolons in the order in which they should process the
4076 <h3>Consulte también</h3>
4078 <li><a href="../filter.html">Filters</a> documentation</li>
4081 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4082 <div class="directive-section"><h2><a name="SetOutputFilter" id="SetOutputFilter">SetOutputFilter</a> <a name="setoutputfilter" id="setoutputfilter">Directiva</a></h2>
4083 <table class="directive">
4084 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Sets the filters that will process responses from the
4086 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>SetOutputFilter <var>filter</var>[;<var>filter</var>...]</code></td></tr>
4087 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
4088 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
4089 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4090 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4092 <p>The <code class="directive">SetOutputFilter</code> directive sets the filters
4093 which will process responses from the server before they are
4094 sent to the client. This is in addition to any filters defined
4095 elsewhere, including the
4096 <code class="directive"><a href="../mod/mod_mime.html#addoutputfilter">AddOutputFilter</a></code>
4099 <p>For example, the following configuration will process all files
4100 in the <code>/www/data/</code> directory for server-side
4103 <div class="example"><p><code>
4104 <Directory /www/data/><br />
4105 <span class="indent">
4106 SetOutputFilter INCLUDES<br />
4111 <p>If more than one filter is specified, they must be separated
4112 by semicolons in the order in which they should process the
4115 <h3>Consulte también</h3>
4117 <li><a href="../filter.html">Filters</a> documentation</li>
4120 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4121 <div class="directive-section"><h2><a name="TimeOut" id="TimeOut">TimeOut</a> <a name="timeout" id="timeout">Directiva</a></h2>
4122 <table class="directive">
4123 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Amount of time the server will wait for
4124 certain events before failing a request</td></tr>
4125 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>TimeOut <var>seconds</var></code></td></tr>
4126 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>TimeOut 60</code></td></tr>
4127 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
4128 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4129 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4131 <p>The <code class="directive">TimeOut</code> directive defines the length
4132 of time Apache httpd will wait for I/O in various circumstances:</p>
4135 <li>When reading data from the client, the length of time to
4136 wait for a TCP packet to arrive if the read buffer is
4139 <li>When writing data to the client, the length of time to wait
4140 for an acknowledgement of a packet if the send buffer is
4143 <li>In <code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code>, the length of time to wait for
4144 output from a CGI script.</li>
4146 <li>In <code class="module"><a href="../mod/mod_ext_filter.html">mod_ext_filter</a></code>, the length of time to
4147 wait for output from a filtering process.</li>
4149 <li>In <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>, the default timeout value if
4150 <code class="directive"><a href="../mod/mod_proxy.html#proxytimeout">ProxyTimeout</a></code> is not
4156 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4157 <div class="directive-section"><h2><a name="TraceEnable" id="TraceEnable">TraceEnable</a> <a name="traceenable" id="traceenable">Directiva</a></h2>
4158 <table class="directive">
4159 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determines the behaviour on <code>TRACE</code> requests</td></tr>
4160 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>TraceEnable <var>[on|off|extended]</var></code></td></tr>
4161 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>TraceEnable on</code></td></tr>
4162 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
4163 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4164 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4165 <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>
4167 <p>This directive overrides the behavior of <code>TRACE</code> for both
4168 the core server and <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>. The default
4169 <code>TraceEnable on</code> permits <code>TRACE</code> requests per
4170 RFC 2616, which disallows any request body to accompany the request.
4171 <code>TraceEnable off</code> causes the core server and
4172 <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> to return a <code>405</code> (Method not
4173 allowed) error to the client.</p>
4175 <p>Finally, for testing and diagnostic purposes only, request
4176 bodies may be allowed using the non-compliant <code>TraceEnable
4177 extended</code> directive. The core (as an origin server) will
4178 restrict the request body to 64k (plus 8k for chunk headers if
4179 <code>Transfer-Encoding: chunked</code> is used). The core will
4180 reflect the full headers and all chunk headers with the response
4181 body. As a proxy server, the request body is not restricted to 64k.</p>
4184 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4185 <div class="directive-section"><h2><a name="UnDefine" id="UnDefine">UnDefine</a> <a name="undefine" id="undefine">Directiva</a></h2>
4186 <table class="directive">
4187 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Undefine the existence of a variable</td></tr>
4188 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>UnDefine <var>parameter-name</var></code></td></tr>
4189 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
4190 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4191 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4193 <p>Undoes the effect of a <code class="directive"><a href="#define">Define</a></code> or
4194 of passing a <code>-D</code> argument to <code class="program"><a href="../programs/httpd.html">httpd</a></code>.</p>
4195 <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
4196 <code>-D</code> arguments in any startup scripts.</p>
4199 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4200 <div class="directive-section"><h2><a name="UseCanonicalName" id="UseCanonicalName">UseCanonicalName</a> <a name="usecanonicalname" id="usecanonicalname">Directiva</a></h2>
4201 <table class="directive">
4202 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures how the server determines its own name and
4204 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>UseCanonicalName On|Off|DNS</code></td></tr>
4205 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>UseCanonicalName Off</code></td></tr>
4206 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
4207 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4208 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4210 <p>In many situations Apache httpd must construct a <em>self-referential</em>
4211 URL -- that is, a URL that refers back to the same server. With
4212 <code>UseCanonicalName On</code> Apache httpd will use the hostname and port
4213 specified in the <code class="directive"><a href="#servername">ServerName</a></code>
4214 directive to construct the canonical name for the server. This name
4215 is used in all self-referential URLs, and for the values of
4216 <code>SERVER_NAME</code> and <code>SERVER_PORT</code> in CGIs.</p>
4218 <p>With <code>UseCanonicalName Off</code> Apache httpd will form
4219 self-referential URLs using the hostname and port supplied by
4220 the client if any are supplied (otherwise it will use the
4221 canonical name, as defined above). These values are the same
4222 that are used to implement <a href="../vhosts/name-based.html">name-based virtual hosts</a>,
4223 and are available with the same clients. The CGI variables
4224 <code>SERVER_NAME</code> and <code>SERVER_PORT</code> will be
4225 constructed from the client supplied values as well.</p>
4227 <p>An example where this may be useful is on an intranet server
4228 where you have users connecting to the machine using short
4229 names such as <code>www</code>. You'll notice that if the users
4230 type a shortname, and a URL which is a directory, such as
4231 <code>http://www/splat</code>, <em>without the trailing
4232 slash</em> then Apache httpd will redirect them to
4233 <code>http://www.domain.com/splat/</code>. If you have
4234 authentication enabled, this will cause the user to have to
4235 authenticate twice (once for <code>www</code> and once again
4236 for <code>www.domain.com</code> -- see <a href="http://httpd.apache.org/docs/misc/FAQ.html#prompted-twice">the
4237 FAQ on this subject for more information</a>). But if
4238 <code class="directive">UseCanonicalName</code> is set <code>Off</code>, then
4239 Apache httpd will redirect to <code>http://www/splat/</code>.</p>
4241 <p>There is a third option, <code>UseCanonicalName DNS</code>,
4242 which is intended for use with mass IP-based virtual hosting to
4243 support ancient clients that do not provide a
4244 <code>Host:</code> header. With this option Apache httpd does a
4245 reverse DNS lookup on the server IP address that the client
4246 connected to in order to work out self-referential URLs.</p>
4248 <div class="warning"><h3>Warning</h3>
4249 <p>If CGIs make assumptions about the values of <code>SERVER_NAME</code>
4250 they may be broken by this option. The client is essentially free
4251 to give whatever value they want as a hostname. But if the CGI is
4252 only using <code>SERVER_NAME</code> to construct self-referential URLs
4253 then it should be just fine.</p>
4256 <h3>Consulte también</h3>
4258 <li><code class="directive"><a href="#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></code></li>
4259 <li><code class="directive"><a href="#servername">ServerName</a></code></li>
4260 <li><code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code></li>
4263 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4264 <div class="directive-section"><h2><a name="UseCanonicalPhysicalPort" id="UseCanonicalPhysicalPort">UseCanonicalPhysicalPort</a> <a name="usecanonicalphysicalport" id="usecanonicalphysicalport">Directiva</a></h2>
4265 <table class="directive">
4266 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures how the server determines its own name and
4268 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>UseCanonicalPhysicalPort On|Off</code></td></tr>
4269 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>UseCanonicalPhysicalPort Off</code></td></tr>
4270 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
4271 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4272 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4274 <p>In many situations Apache httpd must construct a <em>self-referential</em>
4275 URL -- that is, a URL that refers back to the same server. With
4276 <code>UseCanonicalPhysicalPort On</code> Apache httpd will, when
4277 constructing the canonical port for the server to honor
4278 the <code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code> directive,
4279 provide the actual physical port number being used by this request
4280 as a potential port. With <code>UseCanonicalPhysicalPort Off</code>
4281 Apache httpd will not ever use the actual physical port number, instead
4282 relying on all configured information to construct a valid port number.</p>
4284 <div class="note"><h3>Note</h3>
4285 <p>The ordering of when the physical port is used is as follows:<br /><br />
4286 <code>UseCanonicalName On</code></p>
4288 <li>Port provided in <code>Servername</code></li>
4289 <li>Physical port</li>
4290 <li>Default port</li>
4292 <code>UseCanonicalName Off | DNS</code>
4294 <li>Parsed port from <code>Host:</code> header</li>
4295 <li>Physical port</li>
4296 <li>Port provided in <code>Servername</code></li>
4297 <li>Default port</li>
4300 <p>With <code>UseCanonicalPhysicalPort Off</code>, the
4301 physical ports are removed from the ordering.</p>
4305 <h3>Consulte también</h3>
4307 <li><code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code></li>
4308 <li><code class="directive"><a href="#servername">ServerName</a></code></li>
4309 <li><code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code></li>
4312 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4313 <div class="directive-section"><h2><a name="VirtualHost" id="VirtualHost"><VirtualHost></a> <a name="virtualhost" id="virtualhost">Directiva</a></h2>
4314 <table class="directive">
4315 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply only to a specific
4316 hostname or IP address</td></tr>
4317 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><VirtualHost
4318 <var>addr</var>[:<var>port</var>] [<var>addr</var>[:<var>port</var>]]
4319 ...> ... </VirtualHost></code></td></tr>
4320 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
4321 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4322 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4324 <p><code class="directive"><VirtualHost></code> and
4325 <code></VirtualHost></code> are used to enclose a group of
4326 directives that will apply only to a particular virtual host. Any
4327 directive that is allowed in a virtual host context may be
4328 used. When the server receives a request for a document on a
4329 particular virtual host, it uses the configuration directives
4330 enclosed in the <code class="directive"><VirtualHost></code>
4331 section. <var>Addr</var> can be:</p>
4334 <li>The IP address of the virtual host;</li>
4336 <li>A fully qualified domain name for the IP address of the
4337 virtual host (not recommended);</li>
4339 <li>The character <code>*</code>, which is used only in combination with
4340 <code>NameVirtualHost *</code> to match all IP addresses; or</li>
4342 <li>The string <code>_default_</code>, which is used only
4343 with IP virtual hosting to catch unmatched IP addresses.</li>
4346 <div class="example"><h3>Example</h3><p><code>
4347 <VirtualHost 10.1.2.3><br />
4348 <span class="indent">
4349 ServerAdmin webmaster@host.example.com<br />
4350 DocumentRoot /www/docs/host.example.com<br />
4351 ServerName host.example.com<br />
4352 ErrorLog logs/host.example.com-error_log<br />
4353 TransferLog logs/host.example.com-access_log<br />
4355 </VirtualHost>
4359 <p>IPv6 addresses must be specified in square brackets because
4360 the optional port number could not be determined otherwise. An
4361 IPv6 example is shown below:</p>
4363 <div class="example"><p><code>
4364 <VirtualHost [2001:db8::a00:20ff:fea7:ccea]><br />
4365 <span class="indent">
4366 ServerAdmin webmaster@host.example.com<br />
4367 DocumentRoot /www/docs/host.example.com<br />
4368 ServerName host.example.com<br />
4369 ErrorLog logs/host.example.com-error_log<br />
4370 TransferLog logs/host.example.com-access_log<br />
4372 </VirtualHost>
4375 <p>Each Virtual Host must correspond to a different IP address,
4376 different port number or a different host name for the server,
4377 in the former case the server machine must be configured to
4378 accept IP packets for multiple addresses. (If the machine does
4379 not have multiple network interfaces, then this can be
4380 accomplished with the <code>ifconfig alias</code> command -- if
4381 your OS supports it).</p>
4383 <div class="note"><h3>Note</h3>
4384 <p>The use of <code class="directive"><VirtualHost></code> does
4385 <strong>not</strong> affect what addresses Apache httpd listens on. You
4386 may need to ensure that Apache httpd is listening on the correct addresses
4387 using <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>.</p>
4390 <p>When using IP-based virtual hosting, the special name
4391 <code>_default_</code> can be specified in
4392 which case this virtual host will match any IP address that is
4393 not explicitly listed in another virtual host. In the absence
4394 of any <code>_default_</code> virtual host the "main" server config,
4395 consisting of all those definitions outside any VirtualHost
4396 section, is used when no IP-match occurs.</p>
4398 <p>You can specify a <code>:port</code> to change the port that is
4399 matched. If unspecified then it defaults to the same port as the
4400 most recent <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>
4401 statement of the main server. You may also specify <code>:*</code>
4402 to match all ports on that address. (This is recommended when used
4403 with <code>_default_</code>.)</p>
4405 <p>A <code class="directive"><a href="#servername">ServerName</a></code> should be
4406 specified inside each <code class="directive"><VirtualHost></code> block. If it is absent, the
4407 <code class="directive"><a href="#servername">ServerName</a></code> from the "main"
4408 server configuration will be inherited.</p>
4410 <p>If no matching virtual host is found, then the first listed
4411 virtual host that matches the IP address will be used. As a
4412 consequence, the first listed virtual host is the default virtual
4415 <div class="warning"><h3>Security</h3>
4416 <p>See the <a href="../misc/security_tips.html">security tips</a>
4417 document for details on why your security could be compromised if the
4418 directory where log files are stored is writable by anyone other
4419 than the user that starts the server.</p>
4422 <h3>Consulte también</h3>
4424 <li><a href="../vhosts/">Apache HTTP Server Virtual Host documentation</a></li>
4425 <li><a href="../dns-caveats.html">Issues Regarding DNS and
4426 Apache HTTP Server</a></li>
4427 <li><a href="../bind.html">Setting
4428 which addresses and ports Apache HTTP Server uses</a></li>
4429 <li><a href="../sections.html">How <Directory>, <Location>
4430 and <Files> sections work</a> for an explanation of how these
4431 different sections are combined when a request is received</li>
4434 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4435 <div class="directive-section"><h2><a name="Warning" id="Warning">Warning</a> <a name="warning" id="warning">Directiva</a></h2>
4436 <table class="directive">
4437 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Warn from configuration parsing with a custom message</td></tr>
4438 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Warning <var>message</var></code></td></tr>
4439 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
4440 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4441 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4442 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>2.5 and later</td></tr>
4443 </table><p>The documentation for this directive has
4444 not been translated yet. Please have a look at the English
4447 <div class="bottomlang">
4448 <p><span>Idiomas disponibles: </span><a href="../de/mod/core.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> |
4449 <a href="../en/mod/core.html" hreflang="en" rel="alternate" title="English"> en </a> |
4450 <a href="../es/mod/core.html" title="Español"> es </a> |
4451 <a href="../fr/mod/core.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
4452 <a href="../ja/mod/core.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
4453 <a href="../tr/mod/core.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p>
4454 </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>
4455 <script type="text/javascript"><!--//--><![CDATA[//><!--
4456 var comments_shortname = 'httpd';
4457 var comments_identifier = 'http://httpd.apache.org/docs/trunk/mod/core.html';
4459 if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
4460 d.write('<div id="comments_thread"><\/div>');
4461 var s = d.createElement('script');
4462 s.type = 'text/javascript';
4464 s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
4465 (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
4468 d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
4470 })(window, document);
4471 //--><!]]></script></div><div id="footer">
4472 <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>
4473 <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