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.gif" /></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="#contentdigest">ContentDigest</a></li>
56 <li><img alt="" src="../images/down.gif" /> <a href="#defaultruntimedir">DefaultRuntimeDir</a></li>
57 <li><img alt="" src="../images/down.gif" /> <a href="#defaulttype">DefaultType</a></li>
58 <li><img alt="" src="../images/down.gif" /> <a href="#define">Define</a></li>
59 <li><img alt="" src="../images/down.gif" /> <a href="#directory"><Directory></a></li>
60 <li><img alt="" src="../images/down.gif" /> <a href="#directorymatch"><DirectoryMatch></a></li>
61 <li><img alt="" src="../images/down.gif" /> <a href="#documentroot">DocumentRoot</a></li>
62 <li><img alt="" src="../images/down.gif" /> <a href="#else"><Else></a></li>
63 <li><img alt="" src="../images/down.gif" /> <a href="#elseif"><ElseIf></a></li>
64 <li><img alt="" src="../images/down.gif" /> <a href="#enablemmap">EnableMMAP</a></li>
65 <li><img alt="" src="../images/down.gif" /> <a href="#enablesendfile">EnableSendfile</a></li>
66 <li><img alt="" src="../images/down.gif" /> <a href="#error">Error</a></li>
67 <li><img alt="" src="../images/down.gif" /> <a href="#errordocument">ErrorDocument</a></li>
68 <li><img alt="" src="../images/down.gif" /> <a href="#errorlog">ErrorLog</a></li>
69 <li><img alt="" src="../images/down.gif" /> <a href="#errorlogformat">ErrorLogFormat</a></li>
70 <li><img alt="" src="../images/down.gif" /> <a href="#extendedstatus">ExtendedStatus</a></li>
71 <li><img alt="" src="../images/down.gif" /> <a href="#fileetag">FileETag</a></li>
72 <li><img alt="" src="../images/down.gif" /> <a href="#files"><Files></a></li>
73 <li><img alt="" src="../images/down.gif" /> <a href="#filesmatch"><FilesMatch></a></li>
74 <li><img alt="" src="../images/down.gif" /> <a href="#forcetype">ForceType</a></li>
75 <li><img alt="" src="../images/down.gif" /> <a href="#gprofdir">GprofDir</a></li>
76 <li><img alt="" src="../images/down.gif" /> <a href="#hostnamelookups">HostnameLookups</a></li>
77 <li><img alt="" src="../images/down.gif" /> <a href="#if"><If></a></li>
78 <li><img alt="" src="../images/down.gif" /> <a href="#ifdefine"><IfDefine></a></li>
79 <li><img alt="" src="../images/down.gif" /> <a href="#ifmodule"><IfModule></a></li>
80 <li><img alt="" src="../images/down.gif" /> <a href="#include">Include</a></li>
81 <li><img alt="" src="../images/down.gif" /> <a href="#includeoptional">IncludeOptional</a></li>
82 <li><img alt="" src="../images/down.gif" /> <a href="#keepalive">KeepAlive</a></li>
83 <li><img alt="" src="../images/down.gif" /> <a href="#keepalivetimeout">KeepAliveTimeout</a></li>
84 <li><img alt="" src="../images/down.gif" /> <a href="#limit"><Limit></a></li>
85 <li><img alt="" src="../images/down.gif" /> <a href="#limitexcept"><LimitExcept></a></li>
86 <li><img alt="" src="../images/down.gif" /> <a href="#limitinternalrecursion">LimitInternalRecursion</a></li>
87 <li><img alt="" src="../images/down.gif" /> <a href="#limitrequestbody">LimitRequestBody</a></li>
88 <li><img alt="" src="../images/down.gif" /> <a href="#limitrequestfields">LimitRequestFields</a></li>
89 <li><img alt="" src="../images/down.gif" /> <a href="#limitrequestfieldsize">LimitRequestFieldSize</a></li>
90 <li><img alt="" src="../images/down.gif" /> <a href="#limitrequestline">LimitRequestLine</a></li>
91 <li><img alt="" src="../images/down.gif" /> <a href="#limitxmlrequestbody">LimitXMLRequestBody</a></li>
92 <li><img alt="" src="../images/down.gif" /> <a href="#location"><Location></a></li>
93 <li><img alt="" src="../images/down.gif" /> <a href="#locationmatch"><LocationMatch></a></li>
94 <li><img alt="" src="../images/down.gif" /> <a href="#loglevel">LogLevel</a></li>
95 <li><img alt="" src="../images/down.gif" /> <a href="#logleveloverride">LogLevelOverride</a></li>
96 <li><img alt="" src="../images/down.gif" /> <a href="#maxkeepaliverequests">MaxKeepAliveRequests</a></li>
97 <li><img alt="" src="../images/down.gif" /> <a href="#maxrangeoverlaps">MaxRangeOverlaps</a></li>
98 <li><img alt="" src="../images/down.gif" /> <a href="#maxrangereversals">MaxRangeReversals</a></li>
99 <li><img alt="" src="../images/down.gif" /> <a href="#maxranges">MaxRanges</a></li>
100 <li><img alt="" src="../images/down.gif" /> <a href="#mergetrailers">MergeTrailers</a></li>
101 <li><img alt="" src="../images/down.gif" /> <a href="#mutex">Mutex</a></li>
102 <li><img alt="" src="../images/down.gif" /> <a href="#namevirtualhost">NameVirtualHost</a></li>
103 <li><img alt="" src="../images/down.gif" /> <a href="#options">Options</a></li>
104 <li><img alt="" src="../images/down.gif" /> <a href="#protocol">Protocol</a></li>
105 <li><img alt="" src="../images/down.gif" /> <a href="#protocols">Protocols</a></li>
106 <li><img alt="" src="../images/down.gif" /> <a href="#protocolshonororder">ProtocolsHonorOrder</a></li>
107 <li><img alt="" src="../images/down.gif" /> <a href="#qualifyredirecturl">QualifyRedirectURL</a></li>
108 <li><img alt="" src="../images/down.gif" /> <a href="#registerhttpmethod">RegisterHttpMethod</a></li>
109 <li><img alt="" src="../images/down.gif" /> <a href="#rlimitcpu">RLimitCPU</a></li>
110 <li><img alt="" src="../images/down.gif" /> <a href="#rlimitmem">RLimitMEM</a></li>
111 <li><img alt="" src="../images/down.gif" /> <a href="#rlimitnproc">RLimitNPROC</a></li>
112 <li><img alt="" src="../images/down.gif" /> <a href="#scriptinterpretersource">ScriptInterpreterSource</a></li>
113 <li><img alt="" src="../images/down.gif" /> <a href="#seerequesttail">SeeRequestTail</a></li>
114 <li><img alt="" src="../images/down.gif" /> <a href="#serveradmin">ServerAdmin</a></li>
115 <li><img alt="" src="../images/down.gif" /> <a href="#serveralias">ServerAlias</a></li>
116 <li><img alt="" src="../images/down.gif" /> <a href="#servername">ServerName</a></li>
117 <li><img alt="" src="../images/down.gif" /> <a href="#serverpath">ServerPath</a></li>
118 <li><img alt="" src="../images/down.gif" /> <a href="#serverroot">ServerRoot</a></li>
119 <li><img alt="" src="../images/down.gif" /> <a href="#serversignature">ServerSignature</a></li>
120 <li><img alt="" src="../images/down.gif" /> <a href="#servertokens">ServerTokens</a></li>
121 <li><img alt="" src="../images/down.gif" /> <a href="#sethandler">SetHandler</a></li>
122 <li><img alt="" src="../images/down.gif" /> <a href="#setinputfilter">SetInputFilter</a></li>
123 <li><img alt="" src="../images/down.gif" /> <a href="#setoutputfilter">SetOutputFilter</a></li>
124 <li><img alt="" src="../images/down.gif" /> <a href="#timeout">TimeOut</a></li>
125 <li><img alt="" src="../images/down.gif" /> <a href="#traceenable">TraceEnable</a></li>
126 <li><img alt="" src="../images/down.gif" /> <a href="#undefine">UnDefine</a></li>
127 <li><img alt="" src="../images/down.gif" /> <a href="#usecanonicalname">UseCanonicalName</a></li>
128 <li><img alt="" src="../images/down.gif" /> <a href="#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></li>
129 <li><img alt="" src="../images/down.gif" /> <a href="#virtualhost"><VirtualHost></a></li>
130 <li><img alt="" src="../images/down.gif" /> <a href="#warning">Warning</a></li>
132 <ul class="seealso"><li><a href="#comments_section">Comentarios</a></li></ul></div>
134 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
135 <div class="directive-section"><h2><a name="AcceptFilter" id="AcceptFilter">AcceptFilter</a> <a name="acceptfilter" id="acceptfilter">Directiva</a></h2>
136 <table class="directive">
137 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configura mejoras para un Protocolo de Escucha de Sockets</td></tr>
138 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AcceptFilter <var>protocol</var> <var>accept_filter</var></code></td></tr>
139 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
140 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
141 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
142 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Disponible en Apache httpd 2.1.5 y posteriores.
143 En Windows desde Apache httpd 2.3.3 y posteriores.</td></tr>
145 <p>Esta directiva hace posible mejoras específicas a nivel de sistema operativo
146 y a través del tipo de Protocolo para un socket que escucha.
147 La premisa básica es que el kernel no envíe un socket al servidor
148 hasta que o bien los datos se hayan recibido o bien se haya almacenado
149 en el buffer una Respuesta HTTP completa.
150 Actualmente sólo están soportados
151 <a href="http://www.freebsd.org/cgi/man.cgi?query=accept_filter&sektion=9">
152 Accept Filters</a> sobre FreeBSD, <code>TCP_DEFER_ACCEPT</code> sobre Linux,
153 y AcceptEx() sobre Windows.</p>
155 <p>El uso de <code>none</code> para un argumento desactiva cualquier filtro
156 aceptado para ese protocolo. Esto es útil para protocolos que requieren que un
157 servidor envíe datos primeros, tales como <code>ftp:</code> o <code>nntp</code>:</p>
158 <div class="example"><p><code>AcceptFilter nntp none</code></p></div>
160 <p>Los nombres de protocolo por defecto son <code>https</code> para el puerto 443
161 y <code>http</code> para todos los demás puertos. Para especificar que se está
162 utilizando otro protocolo con un puerto escuchando, añade el argumento <var>protocol</var>
163 a la directiva <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>.</p>
165 <p>Sobre FreeBDS los valores por defecto:</p>
166 <div class="example"><p><code>
167 AcceptFilter http httpready <br />
168 AcceptFilter https dataready
171 <p>El filtro <code>httpready</code> almacena en el buffer peticiones HTTP completas
172 a nivel de kernel. Una vez que la petición es recibida, el kernel la envía al servidor.
173 Consulta la página man de
174 <a href="http://www.freebsd.org/cgi/man.cgi?query=accf_http&sektion=9">
175 accf_http(9)</a> para más detalles. Puesto que las peticiones HTTPS
176 están encriptadas, sólo se utiliza el filtro
177 <a href="http://www.freebsd.org/cgi/man.cgi?query=accf_data&sektion=9">accf_data(9)</a>.</p>
179 <p>Sobre Linux los valores por defecto son:</p>
180 <div class="example"><p><code>
181 AcceptFilter http data <br />
182 AcceptFilter https data
185 <p>En Linux, <code>TCP_DEFER_ACCEPT</code> no soporta el buffering en peticiones http.
186 Cualquier valor además de <code>none</code> habilitará
187 <code>TCP_DEFER_ACCEPT</code> en ese socket. Para más detalles
188 ver la página man de Linux
189 <a href="http://homepages.cwi.nl/~aeb/linux/man2html/man7/tcp.7.html">
192 <p>Sobre Windows los valores por defecto son:</p>
193 <div class="example"><p><code>
194 AcceptFilter http data <br />
195 AcceptFilter https data
198 <p>Sobre Windows mpm_winnt interpreta el argumento AcceptFilter para conmutar la API
199 AcceptEx(), y no soporta el buffering sobre el protocolo http. Hay dos valores
200 que utilizan la API Windows AcceptEx() y que recuperan sockets de red
201 entre conexciones. <code>data</code> espera hasta que los datos han sido
202 transmitidos como se comentaba anteriormente, y el buffer inicial de datos y las
203 direcciones de red son recuperadas a partir de una única llamada AcceptEx().
204 <code>connect</code> utiliza la API AcceptEx() API, y recupera también
205 las direcciones de red, pero a diferencia de <code>none</code>
206 la opción <code>connect</code> no espera a la transmisión inicial de los datos.</p>
208 <p>Sobre Windows, <code>none</code> prefiere accept() antes que AcceptEx()
209 y no recuperará sockets entre las conexiones. Lo que es útil para los adaptadores de
210 red con un soporte precario de drivers, así como para algunos proveedores de red
211 tales como drivers vpn, o filtros de spam, de virus o de spyware.</p>
214 <h3>Consulte también</h3>
216 <li><code class="directive">Protocol</code></li>
219 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
220 <div class="directive-section"><h2><a name="AcceptPathInfo" id="AcceptPathInfo">AcceptPathInfo</a> <a name="acceptpathinfo" id="acceptpathinfo">Directiva</a></h2>
221 <table class="directive">
222 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Los recursos aceptan información sobre su ruta</td></tr>
223 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AcceptPathInfo On|Off|Default</code></td></tr>
224 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AcceptPathInfo Default</code></td></tr>
225 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
226 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
227 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
228 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
229 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Disponible en Apache httpd 2.0.30 y posteriores</td></tr>
232 <p>Esta directiva controla si las peticiones que contienen información sobre la ruta
233 que sigue un fichero que existe (o un fichero que no existe pero en un directorio que
234 sí existe) serán aceptadas o denegadas. La información de ruta puede estar disponible
235 para los scripts en la variable de entorno <code>PATH_INFO</code>.</p>
237 <p>Por ejemplo, asumamos que la ubicación <code>/test/</code> apunta a
238 un directorio que contiene únicamente el fichero
239 <code>here.html</code>. Entonces, las peticiones tanto para
240 <code>/test/here.html/more</code> como para
241 <code>/test/nothere.html/more</code> recogen
242 <code>/more</code> como <code>PATH_INFO</code>.</p>
244 <p>Los tres posibles argumentos para la directiva
245 <code class="directive">AcceptPathInfo</code> son los siguientes:</p>
247 <dt><code>Off</code></dt><dd>Una petición sólo será aceptada si
248 se corresponde con una ruta literal que existe. Por lo tanto, una petición
249 con una información de ruta después del nombre de fichero tal como
250 <code>/test/here.html/more</code> en el ejemplo anterior devolverá
251 un error 404 NOT FOUND.</dd>
253 <dt><code>On</code></dt><dd>Una petición será aceptada si una
254 ruta principal de acceso se corresponde con un fichero que existe. El ejemplo
255 anterior <code>/test/here.html/more</code> será aceptado si
256 <code>/test/here.html</code> corresponde a un fichero válido.</dd>
258 <dt><code>Default</code></dt><dd>La gestión de las peticiones
259 con información de ruta está determinada por el <a href="../handler.html">controlador</a> responsable de la petición.
260 El controlador principal para para ficheros normales rechaza por defecto
261 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
262 <code>PATH_INFO</code> por defecto.</dd>
265 <p>El objetivo principal de la directiva <code>AcceptPathInfo</code>
266 es permitirte sobreescribir la opción del controlador
267 de aceptar or rechazar <code>PATH_INFO</code>. Este tipo de sobreescritura se necesita,
268 por ejemplo, cuando utilizas un <a href="../filter.html">filtro</a>, tal como
269 <a href="mod_include.html">INCLUDES</a>, para generar contenido
270 basado en <code>PATH_INFO</code>. El controlador principal normalmente rechazaría
271 la petición, de modo que puedes utilizar la siguiente configuración para habilitarla
274 <div class="example"><p><code>
275 <Files "mypaths.shtml"><br />
276 <span class="indent">
277 Options +Includes<br />
278 SetOutputFilter INCLUDES<br />
279 AcceptPathInfo On<br />
286 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
287 <div class="directive-section"><h2><a name="AccessFileName" id="AccessFileName">AccessFileName</a> <a name="accessfilename" id="accessfilename">Directiva</a></h2>
288 <table class="directive">
289 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Nombre del fichero distribuido de configuración</td></tr>
290 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AccessFileName <var>filename</var> [<var>filename</var>] ...</code></td></tr>
291 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AccessFileName .htaccess</code></td></tr>
292 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
293 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
294 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
296 <p>Mientras que procesa una petición el servidor busca
297 el primer fichero de configuración existente dentro de un listado de nombres en
298 cada directorio de la ruta del documento, si los ficheros distribuidos
299 de configuración están <a href="#allowoverride">habilitados para ese
300 directorio</a>. Por ejemplo:</p>
302 <div class="example"><p><code>
306 <p>antes de servir el documento
307 <code>/usr/local/web/index.html</code>, el servidor leerá
308 <code>/.acl</code>, <code>/usr/.acl</code>,
309 <code>/usr/local/.acl</code> and <code>/usr/local/web/.acl</code>
310 para las directivas, salvo que estén deshabilitadas with</p>
312 <div class="example"><p><code>
313 <Directory /><br />
314 <span class="indent">
315 AllowOverride None<br />
320 <h3>Consulte también</h3>
322 <li><code class="directive"><a href="#allowoverride">AllowOverride</a></code></li>
323 <li><a href="../configuring.html">Configuration Files</a></li>
324 <li><a href="../howto/htaccess.html">.htaccess Files</a></li>
327 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
328 <div class="directive-section"><h2><a name="AddDefaultCharset" id="AddDefaultCharset">AddDefaultCharset</a> <a name="adddefaultcharset" id="adddefaultcharset">Directiva</a></h2>
329 <table class="directive">
330 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Default charset parameter to be added when a response
331 content-type is <code>text/plain</code> or <code>text/html</code></td></tr>
332 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AddDefaultCharset On|Off|<var>charset</var></code></td></tr>
333 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AddDefaultCharset Off</code></td></tr>
334 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
335 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
336 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
337 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
339 <p>This directive specifies a default value for the media type
340 charset parameter (the name of a character encoding) to be added
341 to a response if and only if the response's content-type is either
342 <code>text/plain</code> or <code>text/html</code>. This should override
343 any charset specified in the body of the response via a <code>META</code>
344 element, though the exact behavior is often dependent on the user's client
345 configuration. A setting of <code>AddDefaultCharset Off</code>
346 disables this functionality. <code>AddDefaultCharset On</code> enables
347 a default charset of <code>iso-8859-1</code>. Any other value is assumed
348 to be the <var>charset</var> to be used, which should be one of the
349 <a href="http://www.iana.org/assignments/character-sets">IANA registered
350 charset values</a> for use in Internet media types (MIME types).
353 <div class="example"><p><code>
354 AddDefaultCharset utf-8
357 <p><code class="directive">AddDefaultCharset</code> should only be used when all
358 of the text resources to which it applies are known to be in that
359 character encoding and it is too inconvenient to label their charset
360 individually. One such example is to add the charset parameter
361 to resources containing generated content, such as legacy CGI
362 scripts, that might be vulnerable to cross-site scripting attacks
363 due to user-provided data being included in the output. Note, however,
364 that a better solution is to just fix (or delete) those scripts, since
365 setting a default charset does not protect users that have enabled
366 the "auto-detect character encoding" feature on their browser.</p>
368 <h3>Consulte también</h3>
370 <li><code class="directive"><a href="../mod/mod_mime.html#addcharset">AddCharset</a></code></li>
373 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
374 <div class="directive-section"><h2><a name="AllowEncodedSlashes" id="AllowEncodedSlashes">AllowEncodedSlashes</a> <a name="allowencodedslashes" id="allowencodedslashes">Directiva</a></h2>
375 <table class="directive">
376 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determines whether encoded path separators in URLs are allowed to
377 be passed through</td></tr>
378 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AllowEncodedSlashes On|Off</code></td></tr>
379 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AllowEncodedSlashes Off</code></td></tr>
380 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
381 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
382 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
383 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache httpd 2.0.46 and later</td></tr>
385 <p>The <code class="directive">AllowEncodedSlashes</code> directive allows URLs
386 which contain encoded path separators (<code>%2F</code> for <code>/</code>
387 and additionally <code>%5C</code> for <code>\</code> on according systems)
388 to be used. Normally such URLs are refused with a 404 (Not found) error.</p>
390 <p>Turning <code class="directive">AllowEncodedSlashes</code> <code>On</code> is
391 mostly useful when used in conjunction with <code>PATH_INFO</code>.</p>
393 <div class="note"><h3>Note</h3>
394 <p>Allowing encoded slashes does <em>not</em> imply <em>decoding</em>.
395 Occurrences of <code>%2F</code> or <code>%5C</code> (<em>only</em> on
396 according systems) will be left as such in the otherwise decoded URL
400 <h3>Consulte también</h3>
402 <li><code class="directive"><a href="#acceptpathinfo">AcceptPathInfo</a></code></li>
405 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
406 <div class="directive-section"><h2><a name="AllowOverride" id="AllowOverride">AllowOverride</a> <a name="allowoverride" id="allowoverride">Directiva</a></h2>
407 <table class="directive">
408 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Types of directives that are allowed in
409 <code>.htaccess</code> files</td></tr>
410 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AllowOverride All|None|<var>directive-type</var>
411 [<var>directive-type</var>] ...</code></td></tr>
412 <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>
413 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory</td></tr>
414 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
415 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
417 <p>When the server finds an <code>.htaccess</code> file (as
418 specified by <code class="directive"><a href="#accessfilename">AccessFileName</a></code>)
419 it needs to know which directives declared in that file can override
420 earlier configuration directives.</p>
422 <div class="note"><h3>Only available in <Directory> sections</h3>
423 <code class="directive">AllowOverride</code> is valid only in
424 <code class="directive"><a href="#directory"><Directory></a></code>
425 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
426 <code class="directive"><a href="#files"><Files></a></code> sections.
429 <p>When this directive is set to <code>None</code>, then
430 <a href="#accessfilename">.htaccess</a> files are completely ignored.
431 In this case, the server will not even attempt to read
432 <code>.htaccess</code> files in the filesystem.</p>
434 <p>When this directive is set to <code>All</code>, then any
435 directive which has the .htaccess <a href="directive-dict.html#Context">Context</a> is allowed in
436 <code>.htaccess</code> files.</p>
438 <p>The <var>directive-type</var> can be one of the following
439 groupings of directives.</p>
446 Allow use of the authorization directives (<code class="directive"><a href="../mod/mod_authn_dbm.html#authdbmgroupfile">AuthDBMGroupFile</a></code>,
447 <code class="directive"><a href="../mod/mod_authn_dbm.html#authdbmuserfile">AuthDBMUserFile</a></code>,
448 <code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code>,
449 <code class="directive"><a href="../mod/mod_authn_core.html#authname">AuthName</a></code>,
450 <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>
455 Allow use of the directives controlling document types
456 (<code class="directive"><a href="#errordocument">ErrorDocument</a></code>,
457 <code class="directive"><a href="#forcetype">ForceType</a></code>,
458 <code class="directive"><a href="../mod/mod_negotiation.html#languagepriority">LanguagePriority</a></code>,
459 <code class="directive"><a href="#sethandler">SetHandler</a></code>,
460 <code class="directive"><a href="#setinputfilter">SetInputFilter</a></code>,
461 <code class="directive"><a href="#setoutputfilter">SetOutputFilter</a></code>, and
462 <code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code> Add* and Remove* directives),
463 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>),
464 <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
465 <code class="directive"><a href="../mod/mod_actions.html#action">Action</a></code> from
466 <code class="module"><a href="../mod/mod_actions.html">mod_actions</a></code>.
472 Allow use of the directives controlling directory indexing
473 (<code class="directive"><a href="../mod/mod_autoindex.html#adddescription">AddDescription</a></code>,
474 <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>,
475 <code class="directive"><a href="../mod/mod_autoindex.html#addiconbytype">AddIconByType</a></code>,
476 <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>,
482 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>
484 <dt>Options[=<var>Option</var>,...]</dt>
487 Allow use of the directives controlling specific directory
488 features (<code class="directive"><a href="#options">Options</a></code> and
489 <code class="directive"><a href="../mod/mod_include.html#xbithack">XBitHack</a></code>).
490 An equal sign may be given followed by a comma (but no spaces)
491 separated lists of options that may be set using the <code class="directive"><a href="#options">Options</a></code> command.</dd>
496 <div class="example"><p><code>
497 AllowOverride AuthConfig Indexes
500 <p>In the example above all directives that are neither in the group
501 <code>AuthConfig</code> nor <code>Indexes</code> cause an internal
504 <div class="note"><p>For security and performance reasons, do not set
505 <code>AllowOverride</code> to anything other than <code>None</code>
506 in your <code><Directory /></code> block. Instead, find (or
507 create) the <code><Directory></code> block that refers to the
508 directory where you're actually planning to place a
509 <code>.htaccess</code> file.</p>
512 <h3>Consulte también</h3>
514 <li><code class="directive"><a href="#accessfilename">AccessFileName</a></code></li>
515 <li><a href="../configuring.html">Configuration Files</a></li>
516 <li><a href="../howto/htaccess.html">.htaccess Files</a></li>
519 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
520 <div class="directive-section"><h2><a name="AllowOverrideList" id="AllowOverrideList">AllowOverrideList</a> <a name="allowoverridelist" id="allowoverridelist">Directiva</a></h2>
521 <table class="directive">
522 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Individual directives that are allowed in
523 <code>.htaccess</code> files</td></tr>
524 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AllowOverrideList None|<var>directive</var>
525 [<var>directive-type</var>] ...</code></td></tr>
526 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AllowOverrideList None</code></td></tr>
527 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory</td></tr>
528 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
529 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
530 </table><p>The documentation for this directive has
531 not been translated yet. Please have a look at the English
532 version.</p><h3>Consulte también</h3>
534 <li><code class="directive"><a href="#accessfilename">AccessFileName</a></code></li>
535 <li><code class="directive"><a href="#allowoverride">AllowOverride</a></code></li>
536 <li><a href="../configuring.html">Configuration Files</a></li>
537 <li><a href="../howto/htaccess.html">.htaccess Files</a></li>
540 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
541 <div class="directive-section"><h2><a name="AsyncFilter" id="AsyncFilter">AsyncFilter</a> <a name="asyncfilter" id="asyncfilter">Directiva</a></h2>
542 <table class="directive">
543 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Set the minimum filter type eligible for asynchronous handling</td></tr>
544 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>AsyncFilter request|connection|network</code></td></tr>
545 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>AsyncFilter request</code></td></tr>
546 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
547 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
548 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
549 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Only available from Apache 2.5.0 and later.</td></tr>
550 </table><p>The documentation for this directive has
551 not been translated yet. Please have a look at the English
553 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
554 <div class="directive-section"><h2><a name="CGIMapExtension" id="CGIMapExtension">CGIMapExtension</a> <a name="cgimapextension" id="cgimapextension">Directiva</a></h2>
555 <table class="directive">
556 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Technique for locating the interpreter for CGI
558 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>CGIMapExtension <var>cgi-path</var> <var>.extension</var></code></td></tr>
559 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
560 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
561 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
562 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
563 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>NetWare only</td></tr>
565 <p>This directive is used to control how Apache httpd finds the
566 interpreter used to run CGI scripts. For example, setting
567 <code>CGIMapExtension sys:\foo.nlm .foo</code> will
568 cause all CGI script files with a <code>.foo</code> extension to
569 be passed to the FOO interpreter.</p>
572 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
573 <div class="directive-section"><h2><a name="CGIPassAuth" id="CGIPassAuth">CGIPassAuth</a> <a name="cgipassauth" id="cgipassauth">Directiva</a></h2>
574 <table class="directive">
575 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enables passing HTTP authorization headers to scripts as CGI
577 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>CGIPassAuth On|Off</code></td></tr>
578 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>CGIPassAuth Off</code></td></tr>
579 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
580 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>AuthConfig</td></tr>
581 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
582 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
583 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.4.13 and later</td></tr>
584 </table><p>The documentation for this directive has
585 not been translated yet. Please have a look at the English
587 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
588 <div class="directive-section"><h2><a name="ContentDigest" id="ContentDigest">ContentDigest</a> <a name="contentdigest" id="contentdigest">Directiva</a></h2>
589 <table class="directive">
590 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enables the generation of <code>Content-MD5</code> HTTP Response
592 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ContentDigest On|Off</code></td></tr>
593 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ContentDigest Off</code></td></tr>
594 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
595 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>Options</td></tr>
596 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
597 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
599 <p>This directive enables the generation of
600 <code>Content-MD5</code> headers as defined in RFC1864
601 respectively RFC2616.</p>
603 <p>MD5 is an algorithm for computing a "message digest"
604 (sometimes called "fingerprint") of arbitrary-length data, with
605 a high degree of confidence that any alterations in the data
606 will be reflected in alterations in the message digest.</p>
608 <p>The <code>Content-MD5</code> header provides an end-to-end
609 message integrity check (MIC) of the entity-body. A proxy or
610 client may check this header for detecting accidental
611 modification of the entity-body in transit. Example header:</p>
613 <div class="example"><p><code>
614 Content-MD5: AuLb7Dp1rqtRtxz2m9kRpA==
617 <p>Note that this can cause performance problems on your server
618 since the message digest is computed on every request (the
619 values are not cached).</p>
621 <p><code>Content-MD5</code> is only sent for documents served
622 by the <code class="module"><a href="../mod/core.html">core</a></code>, and not by any module. For example,
623 SSI documents, output from CGI scripts, and byte range responses
624 do not have this header.</p>
627 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
628 <div class="directive-section"><h2><a name="DefaultRuntimeDir" id="DefaultRuntimeDir">DefaultRuntimeDir</a> <a name="defaultruntimedir" id="defaultruntimedir">Directiva</a></h2>
629 <table class="directive">
630 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Base directory for the server run-time files</td></tr>
631 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>DefaultRuntimeDir <var>directory-path</var></code></td></tr>
632 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>DefaultRuntimeDir DEFAULT_REL_RUNTIMEDIR (logs/)</code></td></tr>
633 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
634 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
635 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
636 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache 2.4.2 and later</td></tr>
637 </table><p>The documentation for this directive has
638 not been translated yet. Please have a look at the English
639 version.</p><h3>Consulte también</h3>
641 <li><a href="../misc/security_tips.html#serverroot">the
642 security tips</a> for information on how to properly set
643 permissions on the <code class="directive">ServerRoot</code></li>
646 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
647 <div class="directive-section"><h2><a name="DefaultType" id="DefaultType">DefaultType</a> <a name="defaulttype" id="defaulttype">Directiva</a></h2>
648 <table class="directive">
649 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>This directive has no effect other than to emit warnings
650 if the value is not <code>none</code>. In prior versions, DefaultType
651 would specify a default media type to assign to response content for
652 which no other media type configuration could be found.
654 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>DefaultType <var>media-type|none</var></code></td></tr>
655 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>DefaultType none</code></td></tr>
656 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
657 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
658 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
659 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
660 <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>
662 <p>This directive has been disabled. For backwards compatibility
663 of configuration files, it may be specified with the value
664 <code>none</code>, meaning no default media type. For example:</p>
666 <div class="example"><p><code>
670 <p><code>DefaultType None</code> is only available in
671 httpd-2.2.7 and later.</p>
673 <p>Use the mime.types configuration file and the
674 <code class="directive"><a href="../mod/mod_mime.html#addtype">AddType</a></code> to configure media
675 type assignments via file extensions, or the
676 <code class="directive"><a href="#forcetype">ForceType</a></code> directive to configure
677 the media type for specific resources. Otherwise, the server will
678 send the response without a Content-Type header field and the
679 recipient may attempt to guess the media type.</p>
682 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
683 <div class="directive-section"><h2><a name="Define" id="Define">Define</a> <a name="define" id="define">Directiva</a></h2>
684 <table class="directive">
685 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Define the existence of a variable</td></tr>
686 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Define <var>parameter-name</var></code></td></tr>
687 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
688 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
689 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
691 <p>Equivalent to passing the <code>-D</code> argument to <code class="program"><a href="../programs/httpd.html">httpd</a></code>.</p>
692 <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
693 <code>-D</code> arguments in any startup scripts.</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="Directory" id="Directory"><Directory></a> <a name="directory" id="directory">Directiva</a></h2>
698 <table class="directive">
699 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enclose a group of directives that apply only to the
700 named file-system directory, sub-directories, and their contents.</td></tr>
701 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><Directory <var>directory-path</var>>
702 ... </Directory></code></td></tr>
703 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
704 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
705 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
707 <p><code class="directive"><Directory></code> and
708 <code></Directory></code> are used to enclose a group of
709 directives that will apply only to the named directory,
710 sub-directories of that directory, and the files within the respective
711 directories. Any directive that is allowed
712 in a directory context may be used. <var>Directory-path</var> is
713 either the full path to a directory, or a wild-card string using
714 Unix shell-style matching. In a wild-card string, <code>?</code> matches
715 any single character, and <code>*</code> matches any sequences of
716 characters. You may also use <code>[]</code> character ranges. None
717 of the wildcards match a `/' character, so <code><Directory
718 /*/public_html></code> will not match
719 <code>/home/user/public_html</code>, but <code><Directory
720 /home/*/public_html></code> will match. Example:</p>
722 <div class="example"><p><code>
723 <Directory /usr/local/httpd/htdocs><br />
724 <span class="indent">
725 Options Indexes FollowSymLinks<br />
731 <p>Be careful with the <var>directory-path</var> arguments:
732 They have to literally match the filesystem path which Apache httpd uses
733 to access the files. Directives applied to a particular
734 <code><Directory></code> will not apply to files accessed from
735 that same directory via a different path, such as via different symbolic
739 <p><a class="glossarylink" href="../glossary.html#regex" title="ver glosario">Regular
740 expressions</a> can also be used, with the addition of the
741 <code>~</code> character. For example:</p>
743 <div class="example"><p><code>
744 <Directory ~ "^/www/.*/[0-9]{3}">
747 <p>would match directories in <code>/www/</code> that consisted of
750 <p>If multiple (non-regular expression) <code class="directive"><Directory></code> sections
751 match the directory (or one of its parents) containing a document,
752 then the directives are applied in the order of shortest match
753 first, interspersed with the directives from the <a href="#accessfilename">.htaccess</a> files. For example,
756 <div class="example"><p><code>
757 <Directory /><br />
758 <span class="indent">
759 AllowOverride None<br />
761 </Directory><br />
763 <Directory /home/><br />
764 <span class="indent">
765 AllowOverride FileInfo<br />
770 <p>for access to the document <code>/home/web/dir/doc.html</code>
774 <li>Apply directive <code>AllowOverride None</code>
775 (disabling <code>.htaccess</code> files).</li>
777 <li>Apply directive <code>AllowOverride FileInfo</code> (for
778 directory <code>/home</code>).</li>
780 <li>Apply any <code>FileInfo</code> directives in
781 <code>/home/.htaccess</code>, <code>/home/web/.htaccess</code> and
782 <code>/home/web/dir/.htaccess</code> in that order.</li>
785 <p>Regular expressions are not considered until after all of the
786 normal sections have been applied. Then all of the regular
787 expressions are tested in the order they appeared in the
788 configuration file. For example, with</p>
790 <div class="example"><p><code>
791 <Directory ~ abc$><br />
792 <span class="indent">
793 # ... directives here ...<br />
798 <p>the regular expression section won't be considered until after
799 all normal <code class="directive"><Directory></code>s and
800 <code>.htaccess</code> files have been applied. Then the regular
801 expression will match on <code>/home/abc/public_html/abc</code> and
802 the corresponding <code class="directive"><Directory></code> will
805 <p><strong>Note that the default access for
806 <code><Directory /></code> is <code>Allow from All</code>.
807 This means that Apache httpd will serve any file mapped from an URL. It is
808 recommended that you change this with a block such
811 <div class="example"><p><code>
812 <Directory /><br />
813 <span class="indent">
814 Order Deny,Allow<br />
820 <p><strong>and then override this for directories you
821 <em>want</em> accessible. See the <a href="../misc/security_tips.html">Security Tips</a> page for more
822 details.</strong></p>
824 <p>The directory sections occur in the <code>httpd.conf</code> file.
825 <code class="directive"><Directory></code> directives
826 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>
828 <h3>Consulte también</h3>
830 <li><a href="../sections.html">How <Directory>,
831 <Location> and <Files> sections work</a> for an
832 explanation of how these different sections are combined when a
833 request is received</li>
836 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
837 <div class="directive-section"><h2><a name="DirectoryMatch" id="DirectoryMatch"><DirectoryMatch></a> <a name="directorymatch" id="directorymatch">Directiva</a></h2>
838 <table class="directive">
839 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enclose directives that apply to
840 the contents of file-system directories matching a regular expression.</td></tr>
841 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><DirectoryMatch <var>regex</var>>
842 ... </DirectoryMatch></code></td></tr>
843 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
844 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
845 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
847 <p><code class="directive"><DirectoryMatch></code> and
848 <code></DirectoryMatch></code> are used to enclose a group
849 of directives which will apply only to the named directory (and the files within),
850 the same as <code class="directive"><a href="#directory"><Directory></a></code>.
851 However, it takes as an argument a
852 <a class="glossarylink" href="../glossary.html#regex" title="ver glosario">regular expression</a>. For example:</p>
854 <div class="example"><p><code>
855 <DirectoryMatch "^/www/(.+/)?[0-9]{3}">
858 <p>would match directories in <code>/www/</code> that consisted of three
861 <div class="note"><h3>Compatability</h3>
862 Prior to 2.3.9, this directive implicitly applied to sub-directories
863 (like <code class="directive"><a href="#directory"><Directory></a></code>) and
864 could not match the end of line symbol ($). In 2.3.9 and later,
865 only directories that match the expression are affected by the enclosed
869 <div class="note"><h3>Trailing Slash</h3>
870 This directive applies to requests for directories that may or may
871 not end in a trailing slash, so expressions that are anchored to the
872 end of line ($) must be written with care.
875 <h3>Consulte también</h3>
877 <li><code class="directive"><a href="#directory"><Directory></a></code> for
878 a description of how regular expressions are mixed in with normal
879 <code class="directive"><Directory></code>s</li>
880 <li><a href="../sections.html">How <Directory>, <Location> and
881 <Files> sections work</a> for an explanation of how these different
882 sections are combined when a request is received</li>
885 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
886 <div class="directive-section"><h2><a name="DocumentRoot" id="DocumentRoot">DocumentRoot</a> <a name="documentroot" id="documentroot">Directiva</a></h2>
887 <table class="directive">
888 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Directory that forms the main document tree visible
889 from the web</td></tr>
890 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>DocumentRoot <var>directory-path</var></code></td></tr>
891 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>DocumentRoot /usr/local/apache/htdocs</code></td></tr>
892 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
893 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
894 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
896 <p>This directive sets the directory from which <code class="program"><a href="../programs/httpd.html">httpd</a></code>
897 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
898 path from the requested URL to the document root to make the
899 path to the document. Example:</p>
901 <div class="example"><p><code>
902 DocumentRoot /usr/web
906 <code>http://www.my.host.com/index.html</code> refers to
907 <code>/usr/web/index.html</code>. If the <var>directory-path</var> is
908 not absolute then it is assumed to be relative to the <code class="directive"><a href="#serverroot">ServerRoot</a></code>.</p>
910 <p>The <code class="directive">DocumentRoot</code> should be specified without
911 a trailing slash.</p>
913 <h3>Consulte también</h3>
915 <li><a href="../urlmapping.html#documentroot">Mapping URLs to Filesystem
919 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
920 <div class="directive-section"><h2><a name="Else" id="Else"><Else></a> <a name="else" id="else">Directiva</a></h2>
921 <table class="directive">
922 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply only if the condition of a
923 previous <code class="directive"><a href="#if"><If></a></code> or
924 <code class="directive"><a href="#elseif"><ElseIf></a></code> section is not
925 satisfied by a request at runtime</td></tr>
926 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><Else> ... </Else></code></td></tr>
927 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
928 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
929 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
930 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
931 </table><p>The documentation for this directive has
932 not been translated yet. Please have a look at the English
933 version.</p><h3>Consulte también</h3>
935 <li><code class="directive"><a href="#if"><If></a></code></li>
936 <li><code class="directive"><a href="#elseif"><ElseIf></a></code></li>
937 <li><a href="../sections.html">How <Directory>, <Location>,
938 <Files> sections work</a> for an explanation of how these
939 different sections are combined when a request is received.
940 <code class="directive"><If></code>,
941 <code class="directive"><ElseIf></code>, and
942 <code class="directive"><Else></code> are applied last.</li>
945 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
946 <div class="directive-section"><h2><a name="ElseIf" id="ElseIf"><ElseIf></a> <a name="elseif" id="elseif">Directiva</a></h2>
947 <table class="directive">
948 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply only if a condition is satisfied
949 by a request at runtime while the condition of a previous
950 <code class="directive"><a href="#if"><If></a></code> or
951 <code class="directive"><ElseIf></code> section is not
953 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><ElseIf <var>expression</var>> ... </ElseIf></code></td></tr>
954 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
955 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
956 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
957 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
958 </table><p>The documentation for this directive has
959 not been translated yet. Please have a look at the English
960 version.</p><h3>Consulte también</h3>
962 <li><a href="../expr.html">Expressions in Apache HTTP Server</a>,
963 for a complete reference and more examples.</li>
964 <li><code class="directive"><a href="#if"><If></a></code></li>
965 <li><code class="directive"><a href="#else"><Else></a></code></li>
966 <li><a href="../sections.html">How <Directory>, <Location>,
967 <Files> sections work</a> for an explanation of how these
968 different sections are combined when a request is received.
969 <code class="directive"><If></code>,
970 <code class="directive"><ElseIf></code>, and
971 <code class="directive"><Else></code> are applied last.</li>
974 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
975 <div class="directive-section"><h2><a name="EnableMMAP" id="EnableMMAP">EnableMMAP</a> <a name="enablemmap" id="enablemmap">Directiva</a></h2>
976 <table class="directive">
977 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Use memory-mapping to read files during delivery</td></tr>
978 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>EnableMMAP On|Off</code></td></tr>
979 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>EnableMMAP On</code></td></tr>
980 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
981 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
982 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
983 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
985 <p>This directive controls whether the <code class="program"><a href="../programs/httpd.html">httpd</a></code> may use
986 memory-mapping if it needs to read the contents of a file during
987 delivery. By default, when the handling of a request requires
988 access to the data within a file -- for example, when delivering a
989 server-parsed file using <code class="module"><a href="../mod/mod_include.html">mod_include</a></code> -- Apache httpd
990 memory-maps the file if the OS supports it.</p>
992 <p>This memory-mapping sometimes yields a performance improvement.
993 But in some environments, it is better to disable the memory-mapping
994 to prevent operational problems:</p>
997 <li>On some multiprocessor systems, memory-mapping can reduce the
998 performance of the <code class="program"><a href="../programs/httpd.html">httpd</a></code>.</li>
999 <li>Deleting or truncating a file while <code class="program"><a href="../programs/httpd.html">httpd</a></code>
1000 has it memory-mapped can cause <code class="program"><a href="../programs/httpd.html">httpd</a></code> to
1001 crash with a segmentation fault.
1005 <p>For server configurations that are vulnerable to these problems,
1006 you should disable memory-mapping of delivered files by specifying:</p>
1008 <div class="example"><p><code>
1012 <p>For NFS mounted files, this feature may be disabled explicitly for
1013 the offending files by specifying:</p>
1015 <div class="example"><p><code>
1016 <Directory "/path-to-nfs-files">
1017 <span class="indent">
1024 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1025 <div class="directive-section"><h2><a name="EnableSendfile" id="EnableSendfile">EnableSendfile</a> <a name="enablesendfile" id="enablesendfile">Directiva</a></h2>
1026 <table class="directive">
1027 <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>
1028 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>EnableSendfile On|Off</code></td></tr>
1029 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>EnableSendfile Off</code></td></tr>
1030 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1031 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
1032 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1033 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1034 <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
1035 version 2.3.9.</td></tr>
1037 <p>This directive controls whether <code class="program"><a href="../programs/httpd.html">httpd</a></code> may use the
1038 sendfile support from the kernel to transmit file contents to the client.
1039 By default, when the handling of a request requires no access
1040 to the data within a file -- for example, when delivering a
1041 static file -- Apache httpd uses sendfile to deliver the file contents
1042 without ever reading the file if the OS supports it.</p>
1044 <p>This sendfile mechanism avoids separate read and send operations,
1045 and buffer allocations. But on some platforms or within some
1046 filesystems, it is better to disable this feature to avoid
1047 operational problems:</p>
1050 <li>Some platforms may have broken sendfile support that the build
1051 system did not detect, especially if the binaries were built on
1052 another box and moved to such a machine with broken sendfile
1054 <li>On Linux the use of sendfile triggers TCP-checksum
1055 offloading bugs on certain networking cards when using IPv6.</li>
1056 <li>On Linux on Itanium, sendfile may be unable to handle files
1057 over 2GB in size.</li>
1058 <li>With a network-mounted <code class="directive"><a href="#documentroot">DocumentRoot</a></code> (e.g., NFS, SMB, CIFS, FUSE),
1059 the kernel may be unable to serve the network file through
1063 <p>For server configurations that are not vulnerable to these problems,
1064 you may enable this feature by specifying:</p>
1066 <div class="example"><p><code>
1070 <p>For network mounted files, this feature may be disabled explicitly
1071 for the offending files by specifying:</p>
1073 <div class="example"><p><code>
1074 <Directory "/path-to-nfs-files">
1075 <span class="indent">
1080 <p>Please note that the per-directory and .htaccess configuration
1081 of <code class="directive">EnableSendfile</code> is not supported by
1082 <code class="module"><a href="../mod/mod_cache_disk.html">mod_cache_disk</a></code>.
1083 Only global definition of <code class="directive">EnableSendfile</code>
1084 is taken into account by the module.
1088 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1089 <div class="directive-section"><h2><a name="Error" id="Error">Error</a> <a name="error" id="error">Directiva</a></h2>
1090 <table class="directive">
1091 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Abort configuration parsing with a custom error message</td></tr>
1092 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Error <var>message</var></code></td></tr>
1093 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1094 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1095 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1096 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>2.3.9 and later</td></tr>
1098 <p>If an error can be detected within the configuration, this
1099 directive can be used to generate a custom error message, and halt
1100 configuration parsing. The typical use is for reporting required
1101 modules which are missing from the configuration.</p>
1103 <div class="example"><h3>Example</h3><p><code>
1104 # ensure that mod_include is loaded<br />
1105 <IfModule !include_module><br />
1106 Error mod_include is required by mod_foo. Load it with LoadModule.<br />
1107 </IfModule><br />
1109 # ensure that exactly one of SSL,NOSSL is defined<br />
1110 <IfDefine SSL><br />
1111 <IfDefine NOSSL><br />
1112 Error Both SSL and NOSSL are defined. Define only one of them.<br />
1113 </IfDefine><br />
1114 </IfDefine><br />
1115 <IfDefine !SSL><br />
1116 <IfDefine !NOSSL><br />
1117 Error Either SSL or NOSSL must be defined.<br />
1118 </IfDefine><br />
1119 </IfDefine><br />
1124 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1125 <div class="directive-section"><h2><a name="ErrorDocument" id="ErrorDocument">ErrorDocument</a> <a name="errordocument" id="errordocument">Directiva</a></h2>
1126 <table class="directive">
1127 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>What the server will return to the client
1128 in case of an error</td></tr>
1129 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ErrorDocument <var>error-code</var> <var>document</var></code></td></tr>
1130 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1131 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
1132 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1133 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1135 <p>In the event of a problem or error, Apache httpd can be configured
1136 to do one of four things,</p>
1139 <li>output a simple hardcoded error message</li>
1141 <li>output a customized message</li>
1143 <li>redirect to a local <var>URL-path</var> to handle the
1146 <li>redirect to an external <var>URL</var> to handle the
1150 <p>The first option is the default, while options 2-4 are
1151 configured using the <code class="directive">ErrorDocument</code>
1152 directive, which is followed by the HTTP response code and a URL
1153 or a message. Apache httpd will sometimes offer additional information
1154 regarding the problem/error.</p>
1156 <p>URLs can begin with a slash (/) for local web-paths (relative
1157 to the <code class="directive"><a href="#documentroot">DocumentRoot</a></code>), or be a
1158 full URL which the client can resolve. Alternatively, a message
1159 can be provided to be displayed by the browser. Examples:</p>
1161 <div class="example"><p><code>
1162 ErrorDocument 500 http://foo.example.com/cgi-bin/tester<br />
1163 ErrorDocument 404 /cgi-bin/bad_urls.pl<br />
1164 ErrorDocument 401 /subscription_info.html<br />
1165 ErrorDocument 403 "Sorry can't allow you access today"
1168 <p>Additionally, the special value <code>default</code> can be used
1169 to specify Apache httpd's simple hardcoded message. While not required
1170 under normal circumstances, <code>default</code> will restore
1171 Apache httpd's simple hardcoded message for configurations that would
1172 otherwise inherit an existing <code class="directive">ErrorDocument</code>.</p>
1174 <div class="example"><p><code>
1175 ErrorDocument 404 /cgi-bin/bad_urls.pl<br /><br />
1176 <Directory /web/docs><br />
1177 <span class="indent">
1178 ErrorDocument 404 default<br />
1183 <p>Note that when you specify an <code class="directive">ErrorDocument</code>
1184 that points to a remote URL (ie. anything with a method such as
1185 <code>http</code> in front of it), Apache HTTP Server will send a redirect to the
1186 client to tell it where to find the document, even if the
1187 document ends up being on the same server. This has several
1188 implications, the most important being that the client will not
1189 receive the original error status code, but instead will
1190 receive a redirect status code. This in turn can confuse web
1191 robots and other clients which try to determine if a URL is
1192 valid using the status code. In addition, if you use a remote
1193 URL in an <code>ErrorDocument 401</code>, the client will not
1194 know to prompt the user for a password since it will not
1195 receive the 401 status code. Therefore, <strong>if you use an
1196 <code>ErrorDocument 401</code> directive then it must refer to a local
1197 document.</strong></p>
1199 <p>Microsoft Internet Explorer (MSIE) will by default ignore
1200 server-generated error messages when they are "too small" and substitute
1201 its own "friendly" error messages. The size threshold varies depending on
1202 the type of error, but in general, if you make your error document
1203 greater than 512 bytes, then MSIE will show the server-generated
1204 error rather than masking it. More information is available in
1205 Microsoft Knowledge Base article <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294807">Q294807</a>.</p>
1207 <p>Although most error messages can be overriden, there are certain
1208 circumstances where the internal messages are used regardless of the
1209 setting of <code class="directive"><a href="#errordocument">ErrorDocument</a></code>. In
1210 particular, if a malformed request is detected, normal request processing
1211 will be immediately halted and the internal error message returned.
1212 This is necessary to guard against security problems caused by
1215 <p>If you are using mod_proxy, you may wish to enable
1216 <code class="directive"><a href="../mod/mod_proxy.html#proxyerroroverride">ProxyErrorOverride</a></code> so that you can provide
1217 custom error messages on behalf of your Origin servers. If you don't enable ProxyErrorOverride,
1218 Apache httpd will not generate custom error documents for proxied content.</p>
1220 <h3>Consulte también</h3>
1222 <li><a href="../custom-error.html">documentation of
1223 customizable responses</a></li>
1226 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1227 <div class="directive-section"><h2><a name="ErrorLog" id="ErrorLog">ErrorLog</a> <a name="errorlog" id="errorlog">Directiva</a></h2>
1228 <table class="directive">
1229 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Location where the server will log errors</td></tr>
1230 <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>
1231 <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>
1232 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
1233 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1234 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1236 <p>The <code class="directive">ErrorLog</code> directive sets the name of
1237 the file to which the server will log any errors it encounters. If
1238 the <var>file-path</var> is not absolute then it is assumed to be
1239 relative to the <code class="directive"><a href="#serverroot">ServerRoot</a></code>.</p>
1241 <div class="example"><h3>Example</h3><p><code>
1242 ErrorLog /var/log/httpd/error_log
1245 <p>If the <var>file-path</var>
1246 begins with a pipe character "<code>|</code>" then it is assumed to be a
1247 command to spawn to handle the error log.</p>
1249 <div class="example"><h3>Example</h3><p><code>
1250 ErrorLog "|/usr/local/bin/httpd_errors"
1253 <p>See the notes on <a href="../logs.html#piped">piped logs</a> for
1254 more information.</p>
1256 <p>Using <code>syslog</code> instead of a filename enables logging
1257 via syslogd(8) if the system supports it. The default is to use
1258 syslog facility <code>local7</code>, but you can override this by
1259 using the <code>syslog:<var>facility</var></code> syntax where
1260 <var>facility</var> can be one of the names usually documented in
1261 syslog(1). The facility is effectively global, and if it is changed
1262 in individual virtual hosts, the final facility specified affects the
1265 <div class="example"><h3>Example</h3><p><code>
1266 ErrorLog syslog:user
1269 <p>SECURITY: See the <a href="../misc/security_tips.html#serverroot">security tips</a>
1270 document for details on why your security could be compromised
1271 if the directory where log files are stored is writable by
1272 anyone other than the user that starts the server.</p>
1273 <div class="warning"><h3>Note</h3>
1274 <p>When entering a file path on non-Unix platforms, care should be taken
1275 to make sure that only forward slashed are used even though the platform
1276 may allow the use of back slashes. In general it is a good idea to always
1277 use forward slashes throughout the configuration files.</p>
1280 <h3>Consulte también</h3>
1282 <li><code class="directive"><a href="#loglevel">LogLevel</a></code></li>
1283 <li><a href="../logs.html">Apache HTTP Server Log Files</a></li>
1286 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1287 <div class="directive-section"><h2><a name="ErrorLogFormat" id="ErrorLogFormat">ErrorLogFormat</a> <a name="errorlogformat" id="errorlogformat">Directiva</a></h2>
1288 <table class="directive">
1289 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Format specification for error log entries</td></tr>
1290 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code> ErrorLog [connection|request] <var>format</var></code></td></tr>
1291 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
1292 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1293 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1294 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache httpd 2.3.9 and later</td></tr>
1296 <p><code class="directive">ErrorLogFormat</code> allows to specify what
1297 supplementary information is logged in the error log in addition to the
1298 actual log message.</p>
1300 <div class="example"><h3>Simple example</h3><p><code>
1301 ErrorLogFormat "[%t] [%l] [pid %P] %F: %E: [client %a] %M"
1304 <p>Specifying <code>connection</code> or <code>request</code> as first
1305 paramter allows to specify additional formats, causing additional
1306 information to be logged when the first message is logged for a specific
1307 connection or request, respectivly. This additional information is only
1308 logged once per connection/request. If a connection or request is processed
1309 without causing any log message, the additional information is not logged
1312 <p>It can happen that some format string items do not produce output. For
1313 example, the Referer header is only present if the log message is
1314 associated to a request and the log message happens at a time when the
1315 Referer header has already been read from the client. If no output is
1316 produced, the default behaviour is to delete everything from the preceeding
1317 space character to the next space character. This means the log line is
1318 implicitly divided into fields on non-whitespace to whitespace transitions.
1319 If a format string item does not produce output, the whole field is
1320 ommitted. For example, if the remote address <code>%a</code> in the log
1321 format <code>[%t] [%l] [%a] %M </code> is not available, the surrounding
1322 brackets are not logged either. Space characters can be escaped with a
1323 backslash to prevent them from delimiting a field. The combination '% '
1324 (percent space) is a zero-witdh field delimiter that does not produce any
1327 <p>The above behaviour can be changed by adding modifiers to the format
1328 string item. A <code>-</code> (minus) modifier causes a minus to be logged if the
1329 respective item does not produce any output. In once-per-connection/request
1330 formats, it is also possible to use the <code>+</code> (plus) modifier. If an
1331 item with the plus modifier does not produce any output, the whole line is
1334 <p>A number as modifier can be used to assign a log severity level to a
1335 format item. The item will only be logged if the severity of the log
1336 message is not higher than the specified log severity level. The number can
1337 range from 1 (alert) over 4 (warn) and 7 (debug) to 15 (trace8).</p>
1339 <p>Some format string items accept additional parameters in braces.</p>
1341 <table class="bordered"><tr class="header"><th>Format String</th> <th>Description</th></tr>
1342 <tr><td><code>%%</code></td>
1343 <td>The percent sign</td></tr>
1344 <tr class="odd"><td><code>%...a</code></td>
1345 <td>Remote IP-address and port</td></tr>
1346 <tr><td><code>%...A</code></td>
1347 <td>Local IP-address and port</td></tr>
1348 <tr class="odd"><td><code>%...{name}e</code></td>
1349 <td>Request environment variable <code>name</code></td></tr>
1350 <tr><td><code>%...E</code></td>
1351 <td>APR/OS error status code and string</td></tr>
1352 <tr class="odd"><td><code>%...F</code></td>
1353 <td>Source file name and line number of the log call</td></tr>
1354 <tr><td><code>%...{name}i</code></td>
1355 <td>Request header <code>name</code></td></tr>
1356 <tr class="odd"><td><code>%...k</code></td>
1357 <td>Number of keep-alive requests on this connection</td></tr>
1358 <tr><td><code>%...l</code></td>
1359 <td>Loglevel of the message</td></tr>
1360 <tr class="odd"><td><code>%...L</code></td>
1361 <td>Log ID of the request</td></tr>
1362 <tr><td><code>%...{c}L</code></td>
1363 <td>Log ID of the connection</td></tr>
1364 <tr class="odd"><td><code>%...{C}L</code></td>
1365 <td>Log ID of the connection if used in connection scope, empty otherwise</td></tr>
1366 <tr><td><code>%...m</code></td>
1367 <td>Name of the module logging the message</td></tr>
1368 <tr class="odd"><td><code>%M</code></td>
1369 <td>The actual log message</td></tr>
1370 <tr><td><code>%...{name}n</code></td>
1371 <td>Request note <code>name</code></td></tr>
1372 <tr class="odd"><td><code>%...P</code></td>
1373 <td>Process ID of current process</td></tr>
1374 <tr><td><code>%...T</code></td>
1375 <td>Thread ID of current thread</td></tr>
1376 <tr class="odd"><td><code>%...t</code></td>
1377 <td>The current time</td></tr>
1378 <tr><td><code>%...{u}t</code></td>
1379 <td>The current time including micro-seconds</td></tr>
1380 <tr class="odd"><td><code>%...{cu}t</code></td>
1381 <td>The current time in compact ISO 8601 format, including
1382 micro-seconds</td></tr>
1383 <tr><td><code>%...v</code></td>
1384 <td>The canonical <code class="directive"><a href="#servername">ServerName</a></code>
1385 of the current server.</td></tr>
1386 <tr class="odd"><td><code>%...V</code></td>
1387 <td>The server name of the server serving the request according to the
1388 <code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code>
1390 <tr><td><code>\ </code> (backslash space)</td>
1391 <td>Non-field delimiting space</td></tr>
1392 <tr class="odd"><td><code>% </code> (percent space)</td>
1393 <td>Field delimiter (no output)</td></tr>
1396 <p>The log ID format <code>%L</code> produces a unique id for a connection
1397 or request. This can be used to correlate which log lines belong to the
1398 same connection or request, which request happens on which connection.
1399 A <code>%L</code> format string is also available in
1400 <code class="module"><a href="../mod/mod_log_config.html">mod_log_config</a></code>, to allow to correlate access log entries
1401 with error log lines. If <code class="module"><a href="../mod/mod_unique_id.html">mod_unique_id</a></code> is loaded, its
1402 unique id will be used as log ID for requests.</p>
1404 <div class="example"><h3>Example (somewhat similar to default format)</h3><p><code>
1405 ErrorLogFormat "[%{u}t] [%-m:%l] [pid %P] %7F: %E: [client\ %a]
1406 %M% ,\ referer\ %{Referer}i"
1409 <div class="example"><h3>Example (similar to the 2.2.x format)</h3><p><code>
1410 ErrorLogFormat "[%t] [%l] %7F: %E: [client\ %a]
1411 %M% ,\ referer\ %{Referer}i"
1414 <div class="example"><h3>Advanced example with request/connection log IDs</h3><p><code>
1415 ErrorLogFormat "[%{uc}t] [%-m:%-l] [R:%L] [C:%{C}L] %7F: %E: %M"<br />
1416 ErrorLogFormat request "[%{uc}t] [R:%L] Request %k on C:%{c}L pid:%P tid:%T"<br />
1417 ErrorLogFormat request "[%{uc}t] [R:%L] UA:'%+{User-Agent}i'"<br />
1418 ErrorLogFormat request "[%{uc}t] [R:%L] Referer:'%+{Referer}i'"<br />
1419 ErrorLogFormat connection "[%{uc}t] [C:%{c}L] local\ %a remote\ %A"<br />
1423 <h3>Consulte también</h3>
1425 <li><code class="directive"><a href="#errorlog">ErrorLog</a></code></li>
1426 <li><code class="directive"><a href="#loglevel">LogLevel</a></code></li>
1427 <li><a href="../logs.html">Apache HTTP Server Log Files</a></li>
1430 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1431 <div class="directive-section"><h2><a name="ExtendedStatus" id="ExtendedStatus">ExtendedStatus</a> <a name="extendedstatus" id="extendedstatus">Directiva</a></h2>
1432 <table class="directive">
1433 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Keep track of extended status information for each
1435 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ExtendedStatus On|Off</code></td></tr>
1436 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ExtendedStatus Off[*]</code></td></tr>
1437 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
1438 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1439 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1441 <p>This option tracks additional data per worker about the
1442 currently executing request, and a utilization summary; you
1443 can see these variables during runtime by configuring
1444 <code class="module"><a href="../mod/mod_status.html">mod_status</a></code>. Note that other modules may
1445 rely on this scoreboard.</p>
1447 <p>This setting applies to the entire server, and cannot be
1448 enabled or disabled on a virtualhost-by-virtualhost basis.
1449 The collection of extended status information can slow down
1450 the server. Also note that this setting cannot be changed
1451 during a graceful restart.</p>
1454 <p>Note that loading <code class="module"><a href="../mod/mod_status.html">mod_status</a></code> will change
1455 the default behavior to ExtendedStatus On, while other
1456 third party modules may do the same. Such modules rely on
1457 collecting detailed information about the state of all workers.
1458 The default is changed by <code class="module"><a href="../mod/mod_status.html">mod_status</a></code> beginning
1459 with version 2.3.6; the previous default was always Off.</p>
1464 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1465 <div class="directive-section"><h2><a name="FileETag" id="FileETag">FileETag</a> <a name="fileetag" id="fileetag">Directiva</a></h2>
1466 <table class="directive">
1467 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>File attributes used to create the ETag
1468 HTTP response header for static files</td></tr>
1469 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>FileETag <var>component</var> ...</code></td></tr>
1470 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>FileETag INode MTime Size</code></td></tr>
1471 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1472 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
1473 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1474 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1477 The <code class="directive">FileETag</code> directive configures the file
1478 attributes that are used to create the <code>ETag</code> (entity
1479 tag) response header field when the document is based on a static file.
1480 (The <code>ETag</code> value is used in cache management to save
1481 network bandwidth.) The
1482 <code class="directive">FileETag</code> directive allows you to choose
1483 which of these -- if any -- should be used. The recognized keywords are:
1487 <dt><strong>INode</strong></dt>
1488 <dd>The file's i-node number will be included in the calculation</dd>
1489 <dt><strong>MTime</strong></dt>
1490 <dd>The date and time the file was last modified will be included</dd>
1491 <dt><strong>Size</strong></dt>
1492 <dd>The number of bytes in the file will be included</dd>
1493 <dt><strong>All</strong></dt>
1494 <dd>All available fields will be used. This is equivalent to:
1495 <div class="example"><p><code>FileETag INode MTime Size</code></p></div></dd>
1496 <dt><strong>None</strong></dt>
1497 <dd>If a document is file-based, no <code>ETag</code> field will be
1498 included in the response</dd>
1501 <p>The <code>INode</code>, <code>MTime</code>, and <code>Size</code>
1502 keywords may be prefixed with either <code>+</code> or <code>-</code>,
1503 which allow changes to be made to the default setting inherited
1504 from a broader scope. Any keyword appearing without such a prefix
1505 immediately and completely cancels the inherited setting.</p>
1507 <p>If a directory's configuration includes
1508 <code>FileETag INode MTime Size</code>, and a
1509 subdirectory's includes <code>FileETag -INode</code>,
1510 the setting for that subdirectory (which will be inherited by
1511 any sub-subdirectories that don't override it) will be equivalent to
1512 <code>FileETag MTime Size</code>.</p>
1513 <div class="warning"><h3>Warning</h3>
1514 Do not change the default for directories or locations that have WebDAV
1515 enabled and use <code class="module"><a href="../mod/mod_dav_fs.html">mod_dav_fs</a></code> as a storage provider.
1516 <code class="module"><a href="../mod/mod_dav_fs.html">mod_dav_fs</a></code> uses <code>INode MTime Size</code>
1517 as a fixed format for <code>ETag</code> comparisons on conditional requests.
1518 These conditional requests will break if the <code>ETag</code> format is
1519 changed via <code class="directive">FileETag</code>.
1521 <div class="note"><h3>Server Side Includes</h3>
1522 An ETag is not generated for responses parsed by <code class="module"><a href="../mod/mod_include.html">mod_include</a></code>,
1523 since the response entity can change without a change of the INode, MTime, or Size
1524 of the static file with embedded SSI directives.
1529 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1530 <div class="directive-section"><h2><a name="Files" id="Files"><Files></a> <a name="files" id="files">Directiva</a></h2>
1531 <table class="directive">
1532 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply to matched
1534 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><Files <var>filename</var>> ... </Files></code></td></tr>
1535 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1536 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
1537 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1538 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1540 <p>The <code class="directive"><Files></code> directive
1541 limits the scope of the enclosed directives by filename. It is comparable
1542 to the <code class="directive"><a href="#directory"><Directory></a></code>
1543 and <code class="directive"><a href="#location"><Location></a></code>
1544 directives. It should be matched with a <code></Files></code>
1545 directive. The directives given within this section will be applied to
1546 any object with a basename (last component of filename) matching the
1547 specified filename. <code class="directive"><Files></code>
1548 sections are processed in the order they appear in the
1549 configuration file, after the <code class="directive"><a href="#directory"><Directory></a></code> sections and
1550 <code>.htaccess</code> files are read, but before <code class="directive"><a href="#location"><Location></a></code> sections. Note
1551 that <code class="directive"><Files></code> can be nested
1552 inside <code class="directive"><a href="#directory"><Directory></a></code> sections to restrict the
1553 portion of the filesystem they apply to.</p>
1555 <p>The <var>filename</var> argument should include a filename, or
1556 a wild-card string, where <code>?</code> matches any single character,
1557 and <code>*</code> matches any sequences of characters.
1558 <a class="glossarylink" href="../glossary.html#regex" title="ver glosario">Regular expressions</a>
1559 can also be used, with the addition of the
1560 <code>~</code> character. For example:</p>
1562 <div class="example"><p><code>
1563 <Files ~ "\.(gif|jpe?g|png)$">
1566 <p>would match most common Internet graphics formats. <code class="directive"><a href="#filesmatch"><FilesMatch></a></code> is preferred,
1569 <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
1570 <code>.htaccess</code> files. This allows users to control access to
1571 their own files, at a file-by-file level.</p>
1574 <h3>Consulte también</h3>
1576 <li><a href="../sections.html">How <Directory>, <Location>
1577 and <Files> sections work</a> for an explanation of how these
1578 different sections are combined when a request is received</li>
1581 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1582 <div class="directive-section"><h2><a name="FilesMatch" id="FilesMatch"><FilesMatch></a> <a name="filesmatch" id="filesmatch">Directiva</a></h2>
1583 <table class="directive">
1584 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply to regular-expression matched
1586 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><FilesMatch <var>regex</var>> ... </FilesMatch></code></td></tr>
1587 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1588 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
1589 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1590 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1592 <p>The <code class="directive"><FilesMatch></code> directive
1593 limits the scope of the enclosed directives by filename, just as the
1594 <code class="directive"><a href="#files"><Files></a></code> directive
1595 does. However, it accepts a <a class="glossarylink" href="../glossary.html#regex" title="ver glosario">regular
1596 expression</a>. For example:</p>
1598 <div class="example"><p><code>
1599 <FilesMatch "\.(gif|jpe?g|png)$">
1602 <p>would match most common Internet graphics formats.</p>
1604 <h3>Consulte también</h3>
1606 <li><a href="../sections.html">How <Directory>, <Location>
1607 and <Files> sections work</a> for an explanation of how these
1608 different sections are combined when a request is received</li>
1611 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1612 <div class="directive-section"><h2><a name="ForceType" id="ForceType">ForceType</a> <a name="forcetype" id="forcetype">Directiva</a></h2>
1613 <table class="directive">
1614 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Forces all matching files to be served with the specified
1615 media type in the HTTP Content-Type header field</td></tr>
1616 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ForceType <var>media-type</var>|None</code></td></tr>
1617 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
1618 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
1619 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1620 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1621 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Moved to the core in Apache httpd 2.0</td></tr>
1623 <p>When placed into an <code>.htaccess</code> file or a
1624 <code class="directive"><a href="#directory"><Directory></a></code>, or
1625 <code class="directive"><a href="#location"><Location></a></code> or
1626 <code class="directive"><a href="#files"><Files></a></code>
1627 section, this directive forces all matching files to be served
1628 with the content type identification given by
1629 <var>media-type</var>. For example, if you had a directory full of
1630 GIF files, but did not want to label them all with <code>.gif</code>,
1631 you might want to use:</p>
1633 <div class="example"><p><code>
1637 <p>Note that this directive overrides other indirect media type
1638 associations defined in mime.types or via the
1639 <code class="directive"><a href="../mod/mod_mime.html#addtype">AddType</a></code>.</p>
1641 <p>You can also override more general
1642 <code class="directive">ForceType</code> settings
1643 by using the value of <code>None</code>:</p>
1645 <div class="example"><p><code>
1646 # force all files to be image/gif:<br />
1647 <Location /images><br />
1648 <span class="indent">
1649 ForceType image/gif<br />
1651 </Location><br />
1653 # but normal mime-type associations here:<br />
1654 <Location /images/mixed><br />
1655 <span class="indent">
1656 ForceType None<br />
1661 <p>This directive primarily overrides the content types generated for
1662 static files served out of the filesystem. For resources other than
1663 static files, where the generator of the response typically specifies
1664 a Content-Type, this directive has no effect.</p>
1668 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1669 <div class="directive-section"><h2><a name="GprofDir" id="GprofDir">GprofDir</a> <a name="gprofdir" id="gprofdir">Directiva</a></h2>
1670 <table class="directive">
1671 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Directory to write gmon.out profiling data to. </td></tr>
1672 <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>
1673 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
1674 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1675 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1677 <p>When the server has been compiled with gprof profiling support,
1678 <code class="directive">GprofDir</code> causes <code>gmon.out</code> files to
1679 be written to the specified directory when the process exits. If the
1680 argument ends with a percent symbol ('%'), subdirectories are created
1681 for each process id.</p>
1683 <p>This directive currently only works with the <code class="module"><a href="../mod/prefork.html">prefork</a></code>
1687 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1688 <div class="directive-section"><h2><a name="HostnameLookups" id="HostnameLookups">HostnameLookups</a> <a name="hostnamelookups" id="hostnamelookups">Directiva</a></h2>
1689 <table class="directive">
1690 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enables DNS lookups on client IP addresses</td></tr>
1691 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>HostnameLookups On|Off|Double</code></td></tr>
1692 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>HostnameLookups Off</code></td></tr>
1693 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
1694 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1695 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1697 <p>This directive enables DNS lookups so that host names can be
1698 logged (and passed to CGIs/SSIs in <code>REMOTE_HOST</code>).
1699 The value <code>Double</code> refers to doing double-reverse
1700 DNS lookup. That is, after a reverse lookup is performed, a forward
1701 lookup is then performed on that result. At least one of the IP
1702 addresses in the forward lookup must match the original
1703 address. (In "tcpwrappers" terminology this is called
1704 <code>PARANOID</code>.)</p>
1706 <p>Regardless of the setting, when <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code> is
1707 used for controlling access by hostname, a double reverse lookup
1708 will be performed. This is necessary for security. Note that the
1709 result of this double-reverse isn't generally available unless you
1710 set <code>HostnameLookups Double</code>. For example, if only
1711 <code>HostnameLookups On</code> and a request is made to an object
1712 that is protected by hostname restrictions, regardless of whether
1713 the double-reverse fails or not, CGIs will still be passed the
1714 single-reverse result in <code>REMOTE_HOST</code>.</p>
1716 <p>The default is <code>Off</code> in order to save the network
1717 traffic for those sites that don't truly need the reverse
1718 lookups done. It is also better for the end users because they
1719 don't have to suffer the extra latency that a lookup entails.
1720 Heavily loaded sites should leave this directive
1721 <code>Off</code>, since DNS lookups can take considerable
1722 amounts of time. The utility <code class="program"><a href="../programs/logresolve.html">logresolve</a></code>, compiled by
1723 default to the <code>bin</code> subdirectory of your installation
1724 directory, can be used to look up host names from logged IP addresses
1728 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1729 <div class="directive-section"><h2><a name="If" id="If"><If></a> <a name="if" id="if">Directiva</a></h2>
1730 <table class="directive">
1731 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply only if a condition is
1732 satisfied by a request at runtime</td></tr>
1733 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><If <var>expression</var>> ... </If></code></td></tr>
1734 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1735 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
1736 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1737 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1739 <p>The <code class="directive"><If></code> directive
1740 evaluates an expression at runtime, and applies the enclosed
1741 directives if and only if the expression evaluates to true.
1744 <div class="example"><p><code>
1745 <If "$req{Host} = ''">
1748 <p>would match HTTP/1.0 requests without a <var>Host:</var> header.</p>
1750 <p>You may compare the value of any variable in the request headers
1751 ($req), response headers ($resp) or environment ($env) in your
1754 <p>Apart from <code>=</code>, <code>If</code> can use the <code>IN</code>
1755 operator to compare if the expression is in a given range:</p>
1757 <div class="example"><p><code>
1758 <If %{REQUEST_METHOD} IN GET,HEAD,OPTIONS>
1762 <h3>Consulte también</h3>
1764 <li><a href="../expr.html">Expressions in Apache HTTP Server</a>,
1765 for a complete reference and more examples.</li>
1766 <li><a href="../sections.html">How <Directory>, <Location>,
1767 <Files> sections work</a> for an explanation of how these
1768 different sections are combined when a request is received.
1769 <code class="directive"><If></code> has the same precedence
1770 and usage as <code class="directive"><Files></code></li>
1773 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1774 <div class="directive-section"><h2><a name="IfDefine" id="IfDefine"><IfDefine></a> <a name="ifdefine" id="ifdefine">Directiva</a></h2>
1775 <table class="directive">
1776 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Encloses directives that will be processed only
1777 if a test is true at startup</td></tr>
1778 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><IfDefine [!]<var>parameter-name</var>> ...
1779 </IfDefine></code></td></tr>
1780 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1781 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
1782 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1783 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1785 <p>The <code><IfDefine <var>test</var>>...</IfDefine>
1786 </code> section is used to mark directives that are conditional. The
1787 directives within an <code class="directive"><IfDefine></code>
1788 section are only processed if the <var>test</var> is true. If <var>
1789 test</var> is false, everything between the start and end markers is
1792 <p>The <var>test</var> in the <code class="directive"><IfDefine></code> section directive can be one of two forms:</p>
1795 <li><var>parameter-name</var></li>
1797 <li><code>!</code><var>parameter-name</var></li>
1800 <p>In the former case, the directives between the start and end
1801 markers are only processed if the parameter named
1802 <var>parameter-name</var> is defined. The second format reverses
1803 the test, and only processes the directives if
1804 <var>parameter-name</var> is <strong>not</strong> defined.</p>
1806 <p>The <var>parameter-name</var> argument is a define as given on the
1807 <code class="program"><a href="../programs/httpd.html">httpd</a></code> command line via <code>-D<var>parameter</var>
1808 </code> at the time the server was started or by the <code class="directive"><a href="#define">Define</a></code> directive.</p>
1810 <p><code class="directive"><IfDefine></code> sections are
1811 nest-able, which can be used to implement simple
1812 multiple-parameter tests. Example:</p>
1814 <div class="example"><p><code>
1815 httpd -DReverseProxy -DUseCache -DMemCache ...<br />
1818 <IfDefine ReverseProxy><br />
1819 <span class="indent">
1820 LoadModule proxy_module modules/mod_proxy.so<br />
1821 LoadModule proxy_http_module modules/mod_proxy_http.so<br />
1822 <IfDefine UseCache><br />
1823 <span class="indent">
1824 LoadModule cache_module modules/mod_cache.so<br />
1825 <IfDefine MemCache><br />
1826 <span class="indent">
1827 LoadModule mem_cache_module modules/mod_mem_cache.so<br />
1829 </IfDefine><br />
1830 <IfDefine !MemCache><br />
1831 <span class="indent">
1832 LoadModule cache_disk_module modules/mod_cache_disk.so<br />
1842 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1843 <div class="directive-section"><h2><a name="IfModule" id="IfModule"><IfModule></a> <a name="ifmodule" id="ifmodule">Directiva</a></h2>
1844 <table class="directive">
1845 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Encloses directives that are processed conditional on the
1846 presence or absence of a specific module</td></tr>
1847 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><IfModule [!]<var>module-file</var>|<var>module-identifier</var>> ...
1848 </IfModule></code></td></tr>
1849 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
1850 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
1851 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1852 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1853 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Module identifiers are available in version 2.1 and
1856 <p>The <code><IfModule <var>test</var>>...</IfModule></code>
1857 section is used to mark directives that are conditional on the presence of
1858 a specific module. The directives within an <code class="directive"><IfModule></code> section are only processed if the <var>test</var>
1859 is true. If <var>test</var> is false, everything between the start and
1860 end markers is ignored.</p>
1862 <p>The <var>test</var> in the <code class="directive"><IfModule></code> section directive can be one of two forms:</p>
1865 <li><var>module</var></li>
1867 <li>!<var>module</var></li>
1870 <p>In the former case, the directives between the start and end
1871 markers are only processed if the module named <var>module</var>
1872 is included in Apache httpd -- either compiled in or
1873 dynamically loaded using <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code>. The second format reverses the test,
1874 and only processes the directives if <var>module</var> is
1875 <strong>not</strong> included.</p>
1877 <p>The <var>module</var> argument can be either the module identifier or
1878 the file name of the module, at the time it was compiled. For example,
1879 <code>rewrite_module</code> is the identifier and
1880 <code>mod_rewrite.c</code> is the file name. If a module consists of
1881 several source files, use the name of the file containing the string
1882 <code>STANDARD20_MODULE_STUFF</code>.</p>
1884 <p><code class="directive"><IfModule></code> sections are
1885 nest-able, which can be used to implement simple multiple-module
1888 <div class="note">This section should only be used if you need to have one
1889 configuration file that works whether or not a specific module
1890 is available. In normal operation, directives need not be
1891 placed in <code class="directive"><IfModule></code>
1895 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1896 <div class="directive-section"><h2><a name="Include" id="Include">Include</a> <a name="include" id="include">Directiva</a></h2>
1897 <table class="directive">
1898 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Includes other configuration files from within
1899 the server configuration files</td></tr>
1900 <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>
1901 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
1902 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1903 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1904 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Wildcard matching available in 2.0.41 and later, directory
1905 wildcard matching available in 2.3.6 and later</td></tr>
1907 <p>This directive allows inclusion of other configuration files
1908 from within the server configuration files.</p>
1910 <p>Shell-style (<code>fnmatch()</code>) wildcard characters can be used
1911 in the filename or directory parts of the path to include several files
1912 at once, in alphabetical order. In addition, if
1913 <code class="directive">Include</code> points to a directory, rather than a file,
1914 Apache httpd will read all files in that directory and any subdirectory.
1915 However, including entire directories is not recommended, because it is
1916 easy to accidentally leave temporary files in a directory that can cause
1917 <code class="program"><a href="../programs/httpd.html">httpd</a></code> to fail. Instead, we encourage you to use the
1918 wildcard syntax shown below, to include files that match a particular
1919 pattern, such as *.conf, for example.</p>
1921 <p>When a wildcard is specified for a <strong>file</strong> component of
1922 the path, and no file matches the wildcard, the
1923 <code class="directive"><a href="#include">Include</a></code>
1924 directive will be <strong>silently ignored</strong>. When a wildcard is
1925 specified for a <strong>directory</strong> component of the path, and
1926 no directory matches the wildcard, the
1927 <code class="directive"><a href="#include">Include</a></code> directive will
1928 <strong>fail with an error</strong> saying the directory cannot be found.
1931 <p>For further control over the behaviour of the server when no files or
1932 directories match, prefix the path with the modifiers <var>optional</var>
1933 or <var>strict</var>. If <var>optional</var> is specified, any wildcard
1934 file or directory that does not match will be silently ignored. If
1935 <var>strict</var> is specified, any wildcard file or directory that does
1936 not match at least one file will cause server startup to fail.</p>
1938 <p>When a directory or file component of the path is
1939 specified exactly, and that directory or file does not exist,
1940 <code class="directive"><a href="#include">Include</a></code> directive will fail with an
1941 error saying the file or directory cannot be found.</p>
1943 <p>The file path specified may be an absolute path, or may be relative
1944 to the <code class="directive"><a href="#serverroot">ServerRoot</a></code> directory.</p>
1948 <div class="example"><p><code>
1949 Include /usr/local/apache2/conf/ssl.conf<br />
1950 Include /usr/local/apache2/conf/vhosts/*.conf
1953 <p>Or, providing paths relative to your <code class="directive"><a href="#serverroot">ServerRoot</a></code> directory:</p>
1955 <div class="example"><p><code>
1956 Include conf/ssl.conf<br />
1957 Include conf/vhosts/*.conf
1960 <p>Wildcards may be included in the directory or file portion of the
1961 path. In the following example, the server will fail to load if no
1962 directories match conf/vhosts/*, but will load successfully if no
1963 files match *.conf.</p>
1965 <div class="example"><p><code>
1966 Include conf/vhosts/*/vhost.conf<br />
1967 Include conf/vhosts/*/*.conf
1970 <p>In this example, the server will fail to load if either
1971 conf/vhosts/* matches no directories, or if *.conf matches no files:</p>
1973 <div class="example"><p><code>
1974 Include strict conf/vhosts/*/*.conf
1977 <p>In this example, the server load successfully if either conf/vhosts/*
1978 matches no directories, or if *.conf matches no files:</p>
1980 <div class="example"><p><code>
1981 Include optional conf/vhosts/*/*.conf
1985 <h3>Consulte también</h3>
1987 <li><code class="program"><a href="../programs/apachectl.html">apachectl</a></code></li>
1990 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
1991 <div class="directive-section"><h2><a name="IncludeOptional" id="IncludeOptional">IncludeOptional</a> <a name="includeoptional" id="includeoptional">Directiva</a></h2>
1992 <table class="directive">
1993 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Includes other configuration files from within
1994 the server configuration files</td></tr>
1995 <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>
1996 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
1997 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
1998 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
1999 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in 2.3.6 and later</td></tr>
2000 </table><p>The documentation for this directive has
2001 not been translated yet. Please have a look at the English
2002 version.</p><h3>Consulte también</h3>
2004 <li><code class="directive"><a href="#include">Include</a></code></li>
2005 <li><code class="program"><a href="../programs/apachectl.html">apachectl</a></code></li>
2008 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2009 <div class="directive-section"><h2><a name="KeepAlive" id="KeepAlive">KeepAlive</a> <a name="keepalive" id="keepalive">Directiva</a></h2>
2010 <table class="directive">
2011 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Enables HTTP persistent connections</td></tr>
2012 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>KeepAlive On|Off</code></td></tr>
2013 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>KeepAlive On</code></td></tr>
2014 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2015 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2016 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2018 <p>The Keep-Alive extension to HTTP/1.0 and the persistent
2019 connection feature of HTTP/1.1 provide long-lived HTTP sessions
2020 which allow multiple requests to be sent over the same TCP
2021 connection. In some cases this has been shown to result in an
2022 almost 50% speedup in latency times for HTML documents with
2023 many images. To enable Keep-Alive connections, set
2024 <code>KeepAlive On</code>.</p>
2026 <p>For HTTP/1.0 clients, Keep-Alive connections will only be
2027 used if they are specifically requested by a client. In
2028 addition, a Keep-Alive connection with an HTTP/1.0 client can
2029 only be used when the length of the content is known in
2030 advance. This implies that dynamic content such as CGI output,
2031 SSI pages, and server-generated directory listings will
2032 generally not use Keep-Alive connections to HTTP/1.0 clients.
2033 For HTTP/1.1 clients, persistent connections are the default
2034 unless otherwise specified. If the client requests it, chunked
2035 encoding will be used in order to send content of unknown
2036 length over persistent connections.</p>
2038 <p>When a client uses a Keep-Alive connection it will be counted
2039 as a single "request" for the <code class="directive"><a href="../mod/mpm_common.html#maxconnectionsperchild">MaxConnectionsPerChild</a></code> directive, regardless
2040 of how many requests are sent using the connection.</p>
2042 <h3>Consulte también</h3>
2044 <li><code class="directive"><a href="#maxkeepaliverequests">MaxKeepAliveRequests</a></code></li>
2047 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2048 <div class="directive-section"><h2><a name="KeepAliveTimeout" id="KeepAliveTimeout">KeepAliveTimeout</a> <a name="keepalivetimeout" id="keepalivetimeout">Directiva</a></h2>
2049 <table class="directive">
2050 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Amount of time the server will wait for subsequent
2051 requests on a persistent connection</td></tr>
2052 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>KeepAliveTimeout <var>num</var>[ms]</code></td></tr>
2053 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>KeepAliveTimeout 5</code></td></tr>
2054 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2055 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2056 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2057 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Specifying a value in milliseconds is available in
2058 Apache httpd 2.3.2 and later</td></tr>
2060 <p>The number of seconds Apache httpd will wait for a subsequent
2061 request before closing the connection. By adding a postfix of ms the
2062 timeout can be also set in milliseconds. Once a request has been
2063 received, the timeout value specified by the
2064 <code class="directive"><a href="#timeout">Timeout</a></code> directive applies.</p>
2066 <p>Setting <code class="directive">KeepAliveTimeout</code> to a high value
2067 may cause performance problems in heavily loaded servers. The
2068 higher the timeout, the more server processes will be kept
2069 occupied waiting on connections with idle clients.</p>
2071 <p>In a name-based virtual host context, the value of the first
2072 defined virtual host (the default host) in a set of <code class="directive"><a href="#namevirtualhost">NameVirtualHost</a></code> will be used.
2073 The other values will be ignored.</p>
2076 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2077 <div class="directive-section"><h2><a name="Limit" id="Limit"><Limit></a> <a name="limit" id="limit">Directiva</a></h2>
2078 <table class="directive">
2079 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Restrict enclosed access controls to only certain HTTP
2081 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><Limit <var>method</var> [<var>method</var>] ... > ...
2082 </Limit></code></td></tr>
2083 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
2084 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>AuthConfig, Limit</td></tr>
2085 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2086 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2088 <p>Access controls are normally effective for
2089 <strong>all</strong> access methods, and this is the usual
2090 desired behavior. <strong>In the general case, access control
2091 directives should not be placed within a
2092 <code class="directive"><Limit></code> section.</strong></p>
2094 <p>The purpose of the <code class="directive"><Limit></code>
2095 directive is to restrict the effect of the access controls to the
2096 nominated HTTP methods. For all other methods, the access
2097 restrictions that are enclosed in the <code class="directive"><Limit></code> bracket <strong>will have no
2098 effect</strong>. The following example applies the access control
2099 only to the methods <code>POST</code>, <code>PUT</code>, and
2100 <code>DELETE</code>, leaving all other methods unprotected:</p>
2102 <div class="example"><p><code>
2103 <Limit POST PUT DELETE><br />
2104 <span class="indent">
2105 Require valid-user<br />
2110 <p>The method names listed can be one or more of: <code>GET</code>,
2111 <code>POST</code>, <code>PUT</code>, <code>DELETE</code>,
2112 <code>CONNECT</code>, <code>OPTIONS</code>,
2113 <code>PATCH</code>, <code>PROPFIND</code>, <code>PROPPATCH</code>,
2114 <code>MKCOL</code>, <code>COPY</code>, <code>MOVE</code>,
2115 <code>LOCK</code>, and <code>UNLOCK</code>. <strong>The method name is
2116 case-sensitive.</strong> If <code>GET</code> is used it will also
2117 restrict <code>HEAD</code> requests. The <code>TRACE</code> method
2118 cannot be limited (see <code class="directive"><a href="#traceenable">TraceEnable</a></code>).</p>
2120 <div class="warning">A <code class="directive"><a href="#limitexcept"><LimitExcept></a></code> section should always be
2121 used in preference to a <code class="directive"><Limit></code>
2122 section when restricting access, since a <code class="directive"><a href="#limitexcept"><LimitExcept></a></code> section provides protection
2123 against arbitrary methods.</div>
2125 <p>The <code class="directive"><Limit></code> and
2126 <code class="directive"><a href="#limitexcept"><LimitExcept></a></code>
2127 directives may be nested. In this case, each successive level of
2128 <code class="directive"><Limit></code> or <code class="directive"><a href="#limitexcept"><LimitExcept></a></code> directives must
2129 further restrict the set of methods to which access controls apply.</p>
2131 <div class="warning">When using
2132 <code class="directive"><Limit></code> or
2133 <code class="directive"><LimitExcept></code> directives with
2134 the <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> directive,
2135 note that the first <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>
2136 to succeed authorizes the request, regardless of the presence of other
2137 <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> directives.</div>
2139 <p>For example, given the following configuration, all users will
2140 be authorized for <code>POST</code> requests, and the
2141 <code>Require group editors</code> directive will be ignored
2144 <div class="example"><p><code>
2145 <LimitExcept GET>
2146 <span class="indent">
2149 </LimitExcept><br />
2151 <span class="indent">
2152 Require group editors
2158 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2159 <div class="directive-section"><h2><a name="LimitExcept" id="LimitExcept"><LimitExcept></a> <a name="limitexcept" id="limitexcept">Directiva</a></h2>
2160 <table class="directive">
2161 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Restrict access controls to all HTTP methods
2162 except the named ones</td></tr>
2163 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><LimitExcept <var>method</var> [<var>method</var>] ... > ...
2164 </LimitExcept></code></td></tr>
2165 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>directory, .htaccess</td></tr>
2166 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>AuthConfig, Limit</td></tr>
2167 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2168 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2170 <p><code class="directive"><LimitExcept></code> and
2171 <code></LimitExcept></code> are used to enclose
2172 a group of access control directives which will then apply to any
2173 HTTP access method <strong>not</strong> listed in the arguments;
2174 i.e., it is the opposite of a <code class="directive"><a href="#limit"><Limit></a></code> section and can be used to control
2175 both standard and nonstandard/unrecognized methods. See the
2176 documentation for <code class="directive"><a href="#limit"><Limit></a></code> for more details.</p>
2180 <div class="example"><p><code>
2181 <LimitExcept POST GET><br />
2182 <span class="indent">
2183 Require valid-user<br />
2185 </LimitExcept>
2190 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2191 <div class="directive-section"><h2><a name="LimitInternalRecursion" id="LimitInternalRecursion">LimitInternalRecursion</a> <a name="limitinternalrecursion" id="limitinternalrecursion">Directiva</a></h2>
2192 <table class="directive">
2193 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determine maximum number of internal redirects and nested
2194 subrequests</td></tr>
2195 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitInternalRecursion <var>number</var> [<var>number</var>]</code></td></tr>
2196 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitInternalRecursion 10</code></td></tr>
2197 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2198 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2199 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2200 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache httpd 2.0.47 and later</td></tr>
2202 <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
2203 redirects the original request to a CGI script. A subrequest is Apache httpd's
2204 mechanism to find out what would happen for some URI if it were requested.
2205 For example, <code class="module"><a href="../mod/mod_dir.html">mod_dir</a></code> uses subrequests to look for the
2206 files listed in the <code class="directive"><a href="../mod/mod_dir.html#directoryindex">DirectoryIndex</a></code>
2209 <p><code class="directive">LimitInternalRecursion</code> prevents the server
2210 from crashing when entering an infinite loop of internal redirects or
2211 subrequests. Such loops are usually caused by misconfigurations.</p>
2213 <p>The directive stores two different limits, which are evaluated on
2214 per-request basis. The first <var>number</var> is the maximum number of
2215 internal redirects, that may follow each other. The second <var>number</var>
2216 determines, how deep subrequests may be nested. If you specify only one
2217 <var>number</var>, it will be assigned to both limits.</p>
2219 <div class="example"><h3>Example</h3><p><code>
2220 LimitInternalRecursion 5
2224 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2225 <div class="directive-section"><h2><a name="LimitRequestBody" id="LimitRequestBody">LimitRequestBody</a> <a name="limitrequestbody" id="limitrequestbody">Directiva</a></h2>
2226 <table class="directive">
2227 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Restricts the total size of the HTTP request body sent
2228 from the client</td></tr>
2229 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitRequestBody <var>bytes</var></code></td></tr>
2230 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitRequestBody 0</code></td></tr>
2231 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
2232 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
2233 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2234 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2236 <p>This directive specifies the number of <var>bytes</var> from 0
2237 (meaning unlimited) to 2147483647 (2GB) that are allowed in a
2238 request body. See the note below for the limited applicability
2239 to proxy requests.</p>
2241 <p>The <code class="directive">LimitRequestBody</code> directive allows
2242 the user to set a limit on the allowed size of an HTTP request
2243 message body within the context in which the directive is given
2244 (server, per-directory, per-file or per-location). If the client
2245 request exceeds that limit, the server will return an error
2246 response instead of servicing the request. The size of a normal
2247 request message body will vary greatly depending on the nature of
2248 the resource and the methods allowed on that resource. CGI scripts
2249 typically use the message body for retrieving form information.
2250 Implementations of the <code>PUT</code> method will require
2251 a value at least as large as any representation that the server
2252 wishes to accept for that resource.</p>
2254 <p>This directive gives the server administrator greater
2255 control over abnormal client request behavior, which may be
2256 useful for avoiding some forms of denial-of-service
2259 <p>If, for example, you are permitting file upload to a particular
2260 location, and wish to limit the size of the uploaded file to 100K,
2261 you might use the following directive:</p>
2263 <div class="example"><p><code>
2264 LimitRequestBody 102400
2267 <div class="note"><p>For a full description of how this directive is interpreted by
2268 proxy requests, see the <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> documentation.</p>
2273 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2274 <div class="directive-section"><h2><a name="LimitRequestFields" id="LimitRequestFields">LimitRequestFields</a> <a name="limitrequestfields" id="limitrequestfields">Directiva</a></h2>
2275 <table class="directive">
2276 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the number of HTTP request header fields that
2277 will be accepted from the client</td></tr>
2278 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitRequestFields <var>number</var></code></td></tr>
2279 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitRequestFields 100</code></td></tr>
2280 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2281 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2282 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2284 <p><var>Number</var> is an integer from 0 (meaning unlimited) to
2285 32767. The default value is defined by the compile-time
2286 constant <code>DEFAULT_LIMIT_REQUEST_FIELDS</code> (100 as
2289 <p>The <code class="directive">LimitRequestFields</code> directive allows
2290 the server administrator to modify the limit on the number of
2291 request header fields allowed in an HTTP request. A server needs
2292 this value to be larger than the number of fields that a normal
2293 client request might include. The number of request header fields
2294 used by a client rarely exceeds 20, but this may vary among
2295 different client implementations, often depending upon the extent
2296 to which a user has configured their browser to support detailed
2297 content negotiation. Optional HTTP extensions are often expressed
2298 using request header fields.</p>
2300 <p>This directive gives the server administrator greater
2301 control over abnormal client request behavior, which may be
2302 useful for avoiding some forms of denial-of-service attacks.
2303 The value should be increased if normal clients see an error
2304 response from the server that indicates too many fields were
2305 sent in the request.</p>
2309 <div class="example"><p><code>
2310 LimitRequestFields 50
2313 <div class="warning"><h3>Warning</h3>
2314 <p> When name-based virtual hosting is used, the value for this
2315 directive is taken from the default (first-listed) virtual host for the
2316 <code class="directive">NameVirtualHost</code> the connection was mapped to.</p>
2321 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2322 <div class="directive-section"><h2><a name="LimitRequestFieldSize" id="LimitRequestFieldSize">LimitRequestFieldSize</a> <a name="limitrequestfieldsize" id="limitrequestfieldsize">Directiva</a></h2>
2323 <table class="directive">
2324 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the size of the HTTP request header allowed from the
2326 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitRequestFieldSize <var>bytes</var></code></td></tr>
2327 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitRequestFieldSize 8190</code></td></tr>
2328 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2329 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2330 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2332 <p>This directive specifies the number of <var>bytes</var>
2333 that will be allowed in an HTTP request header.</p>
2335 <p>The <code class="directive">LimitRequestFieldSize</code> directive
2336 allows the server administrator to reduce or increase the limit
2337 on the allowed size of an HTTP request header field. A server
2338 needs this value to be large enough to hold any one header field
2339 from a normal client request. The size of a normal request header
2340 field will vary greatly among different client implementations,
2341 often depending upon the extent to which a user has configured
2342 their browser to support detailed content negotiation. SPNEGO
2343 authentication headers can be up to 12392 bytes.</p>
2345 <p>This directive gives the server administrator greater
2346 control over abnormal client request behavior, which may be
2347 useful for avoiding some forms of denial-of-service attacks.</p>
2351 <div class="example"><p><code>
2352 LimitRequestFieldSize 4094
2355 <div class="note">Under normal conditions, the value should not be changed from
2358 <div class="warning"><h3>Warning</h3>
2359 <p> When name-based virtual hosting is used, the value for this
2360 directive is taken from the default (first-listed) virtual host for the
2361 <code class="directive">NameVirtualHost</code> the connection was mapped to.</p>
2366 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2367 <div class="directive-section"><h2><a name="LimitRequestLine" id="LimitRequestLine">LimitRequestLine</a> <a name="limitrequestline" id="limitrequestline">Directiva</a></h2>
2368 <table class="directive">
2369 <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
2370 from the client</td></tr>
2371 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitRequestLine <var>bytes</var></code></td></tr>
2372 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitRequestLine 8190</code></td></tr>
2373 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2374 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2375 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2377 <p>This directive sets the number of <var>bytes</var> that will be
2378 allowed on the HTTP request-line.</p>
2380 <p>The <code class="directive">LimitRequestLine</code> directive allows
2381 the server administrator to reduce or increase the limit on the allowed size
2382 of a client's HTTP request-line. Since the request-line consists of the
2383 HTTP method, URI, and protocol version, the
2384 <code class="directive">LimitRequestLine</code> directive places a
2385 restriction on the length of a request-URI allowed for a request
2386 on the server. A server needs this value to be large enough to
2387 hold any of its resource names, including any information that
2388 might be passed in the query part of a <code>GET</code> request.</p>
2390 <p>This directive gives the server administrator greater
2391 control over abnormal client request behavior, which may be
2392 useful for avoiding some forms of denial-of-service attacks.</p>
2396 <div class="example"><p><code>
2397 LimitRequestLine 4094
2400 <div class="note">Under normal conditions, the value should not be changed from
2403 <div class="warning"><h3>Warning</h3>
2404 <p> When name-based virtual hosting is used, the value for this
2405 directive is taken from the default (first-listed) virtual host for the
2406 <code class="directive">NameVirtualHost</code> the connection was mapped to.</p>
2411 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2412 <div class="directive-section"><h2><a name="LimitXMLRequestBody" id="LimitXMLRequestBody">LimitXMLRequestBody</a> <a name="limitxmlrequestbody" id="limitxmlrequestbody">Directiva</a></h2>
2413 <table class="directive">
2414 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the size of an XML-based request body</td></tr>
2415 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LimitXMLRequestBody <var>bytes</var></code></td></tr>
2416 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LimitXMLRequestBody 1000000</code></td></tr>
2417 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
2418 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
2419 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2420 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2422 <p>Limit (in bytes) on maximum size of an XML-based request
2423 body. A value of <code>0</code> will disable any checking.</p>
2427 <div class="example"><p><code>
2428 LimitXMLRequestBody 0
2433 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2434 <div class="directive-section"><h2><a name="Location" id="Location"><Location></a> <a name="location" id="location">Directiva</a></h2>
2435 <table class="directive">
2436 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Applies the enclosed directives only to matching
2438 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><Location
2439 <var>URL-path</var>|<var>URL</var>> ... </Location></code></td></tr>
2440 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2441 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2442 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2444 <p>The <code class="directive"><Location></code> directive
2445 limits the scope of the enclosed directives by URL. It is similar to the
2446 <code class="directive"><a href="#directory"><Directory></a></code>
2447 directive, and starts a subsection which is terminated with a
2448 <code></Location></code> directive. <code class="directive"><Location></code> sections are processed in the
2449 order they appear in the configuration file, after the <code class="directive"><a href="#directory"><Directory></a></code> sections and
2450 <code>.htaccess</code> files are read, and after the <code class="directive"><a href="#files"><Files></a></code> sections.</p>
2452 <p><code class="directive"><Location></code> sections operate
2453 completely outside the filesystem. This has several consequences.
2454 Most importantly, <code class="directive"><Location></code>
2455 directives should not be used to control access to filesystem
2456 locations. Since several different URLs may map to the same
2457 filesystem location, such access controls may by circumvented.</p>
2459 <p>The enclosed directives will be applied to the request if the path component
2460 of the URL meets <em>any</em> of the following criteria:
2463 <li>The specified location matches exactly the path component of the URL.
2465 <li>The specified location, which ends in a forward slash, is a prefix
2466 of the path component of the URL (treated as a context root).
2468 <li>The specified location, with the addition of a trailing slash, is a
2469 prefix of the path component of the URL (also treated as a context root).
2473 In the example below, where no trailing slash is used, requests to
2474 /private1, /private1/ and /private1/file.txt will have the enclosed
2475 directives applied, but /private1other would not.
2477 <div class="example"><p><code>
2478 <Location /private1>
2482 In the example below, where a trailing slash is used, requests to
2483 /private2/ and /private2/file.txt will have the enclosed
2484 directives applied, but /private2 and /private2other would not.
2486 <div class="example"><p><code>
2487 <Location /private2<em>/</em>>
2491 <div class="note"><h3>When to use <code class="directive"><Location></code></h3>
2493 <p>Use <code class="directive"><Location></code> to apply
2494 directives to content that lives outside the filesystem. For
2495 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
2496 <code><Location /></code>, which is an easy way to
2497 apply a configuration to the entire server.</p>
2500 <p>For all origin (non-proxy) requests, the URL to be matched is a
2501 URL-path of the form <code>/path/</code>. <em>No scheme, hostname,
2502 port, or query string may be included.</em> For proxy requests, the
2503 URL to be matched is of the form
2504 <code>scheme://servername/path</code>, and you must include the
2507 <p>The URL may use wildcards. In a wild-card string, <code>?</code> matches
2508 any single character, and <code>*</code> matches any sequences of
2509 characters. Neither wildcard character matches a / in the URL-path.</p>
2511 <p><a class="glossarylink" href="../glossary.html#regex" title="ver glosario">Regular expressions</a>
2512 can also be used, with the addition of the <code>~</code>
2513 character. For example:</p>
2515 <div class="example"><p><code>
2516 <Location ~ "/(extra|special)/data">
2519 <p>would match URLs that contained the substring <code>/extra/data</code>
2520 or <code>/special/data</code>. The directive <code class="directive"><a href="#locationmatch"><LocationMatch></a></code> behaves
2521 identical to the regex version of <code class="directive"><Location></code>, and is preferred, for the
2522 simple reason that <code>~</code> is hard to distinguish from
2523 <code>-</code> in many fonts.</p>
2525 <p>The <code class="directive"><Location></code>
2526 functionality is especially useful when combined with the
2527 <code class="directive"><a href="#sethandler">SetHandler</a></code>
2528 directive. For example, to enable status requests, but allow them
2529 only from browsers at <code>example.com</code>, you might use:</p>
2531 <div class="example"><p><code>
2532 <Location /status><br />
2533 <span class="indent">
2534 SetHandler server-status<br />
2535 Require host example.com<br />
2540 <div class="note"><h3>Note about / (slash)</h3>
2541 <p>The slash character has special meaning depending on where in a
2542 URL it appears. People may be used to its behavior in the filesystem
2543 where multiple adjacent slashes are frequently collapsed to a single
2544 slash (<em>i.e.</em>, <code>/home///foo</code> is the same as
2545 <code>/home/foo</code>). In URL-space this is not necessarily true.
2546 The <code class="directive"><a href="#locationmatch"><LocationMatch></a></code>
2547 directive and the regex version of <code class="directive"><Location></code> require you to explicitly specify multiple
2548 slashes if that is your intention.</p>
2550 <p>For example, <code><LocationMatch ^/abc></code> would match
2551 the request URL <code>/abc</code> but not the request URL <code>
2552 //abc</code>. The (non-regex) <code class="directive"><Location></code> directive behaves similarly when used for
2553 proxy requests. But when (non-regex) <code class="directive"><Location></code> is used for non-proxy requests it will
2554 implicitly match multiple slashes with a single slash. For example,
2555 if you specify <code><Location /abc/def></code> and the
2556 request is to <code>/abc//def</code> then it will match.</p>
2559 <h3>Consulte también</h3>
2561 <li><a href="../sections.html">How <Directory>, <Location>
2562 and <Files> sections work</a> for an explanation of how these
2563 different sections are combined when a request is received.</li>
2564 <li><code class="directive"><a href="#locationmatch">LocationMatch</a></code></li>
2567 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2568 <div class="directive-section"><h2><a name="LocationMatch" id="LocationMatch"><LocationMatch></a> <a name="locationmatch" id="locationmatch">Directiva</a></h2>
2569 <table class="directive">
2570 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Applies the enclosed directives only to regular-expression
2571 matching URLs</td></tr>
2572 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><LocationMatch
2573 <var>regex</var>> ... </LocationMatch></code></td></tr>
2574 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2575 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2576 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2578 <p>The <code class="directive"><LocationMatch></code> directive
2579 limits the scope of the enclosed directives by URL, in an identical manner
2580 to <code class="directive"><a href="#location"><Location></a></code>. However,
2581 it takes a <a class="glossarylink" href="../glossary.html#regex" title="ver glosario">regular expression</a>
2582 as an argument instead of a simple string. For example:</p>
2584 <div class="example"><p><code>
2585 <LocationMatch "/(extra|special)/data">
2588 <p>would match URLs that contained the substring <code>/extra/data</code>
2589 or <code>/special/data</code>.</p>
2591 <h3>Consulte también</h3>
2593 <li><a href="../sections.html">How <Directory>, <Location>
2594 and <Files> sections work</a> for an explanation of how these
2595 different sections are combined when a request is received</li>
2598 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2599 <div class="directive-section"><h2><a name="LogLevel" id="LogLevel">LogLevel</a> <a name="loglevel" id="loglevel">Directiva</a></h2>
2600 <table class="directive">
2601 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Controls the verbosity of the ErrorLog</td></tr>
2602 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LogLevel [<var>module</var>:]<var>level</var>
2603 [<var>module</var>:<var>level</var>] ...
2605 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>LogLevel warn</code></td></tr>
2606 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
2607 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2608 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2609 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Per-module and per-directory configuration is available in
2610 Apache HTTP Server 2.3.6 and later</td></tr>
2612 <p><code class="directive">LogLevel</code> adjusts the verbosity of the
2613 messages recorded in the error logs (see <code class="directive"><a href="#errorlog">ErrorLog</a></code> directive). The following
2614 <var>level</var>s are available, in order of decreasing
2617 <table class="bordered">
2620 <th><strong>Level</strong> </th>
2622 <th><strong>Description</strong> </th>
2624 <th><strong>Example</strong> </th>
2628 <td><code>emerg</code> </td>
2630 <td>Emergencies - system is unusable.</td>
2632 <td>"Child cannot open lock file. Exiting"</td>
2636 <td><code>alert</code> </td>
2638 <td>Action must be taken immediately.</td>
2640 <td>"getpwuid: couldn't determine user name from uid"</td>
2644 <td><code>crit</code> </td>
2646 <td>Critical Conditions.</td>
2648 <td>"socket: Failed to get a socket, exiting child"</td>
2652 <td><code>error</code> </td>
2654 <td>Error conditions.</td>
2656 <td>"Premature end of script headers"</td>
2660 <td><code>warn</code> </td>
2662 <td>Warning conditions.</td>
2664 <td>"child process 1234 did not exit, sending another
2669 <td><code>notice</code> </td>
2671 <td>Normal but significant condition.</td>
2673 <td>"httpd: caught SIGBUS, attempting to dump core in
2678 <td><code>info</code> </td>
2680 <td>Informational.</td>
2682 <td>"Server seems busy, (you may need to increase
2683 StartServers, or Min/MaxSpareServers)..."</td>
2687 <td><code>debug</code> </td>
2689 <td>Debug-level messages</td>
2691 <td>"Opening config file ..."</td>
2694 <td><code>trace1</code> </td>
2696 <td>Trace messages</td>
2698 <td>"proxy: FTP: control connection complete"</td>
2701 <td><code>trace2</code> </td>
2703 <td>Trace messages</td>
2705 <td>"proxy: CONNECT: sending the CONNECT request to the remote proxy"</td>
2708 <td><code>trace3</code> </td>
2710 <td>Trace messages</td>
2712 <td>"openssl: Handshake: start"</td>
2715 <td><code>trace4</code> </td>
2717 <td>Trace messages</td>
2719 <td>"read from buffered SSL brigade, mode 0, 17 bytes"</td>
2722 <td><code>trace5</code> </td>
2724 <td>Trace messages</td>
2726 <td>"map lookup FAILED: map=rewritemap key=keyname"</td>
2729 <td><code>trace6</code> </td>
2731 <td>Trace messages</td>
2733 <td>"cache lookup FAILED, forcing new map lookup"</td>
2736 <td><code>trace7</code> </td>
2738 <td>Trace messages, dumping large amounts of data</td>
2740 <td>"| 0000: 02 23 44 30 13 40 ac 34 df 3d bf 9a 19 49 39 15 |"</td>
2743 <td><code>trace8</code> </td>
2745 <td>Trace messages, dumping large amounts of data</td>
2747 <td>"| 0000: 02 23 44 30 13 40 ac 34 df 3d bf 9a 19 49 39 15 |"</td>
2751 <p>When a particular level is specified, messages from all
2752 other levels of higher significance will be reported as well.
2753 <em>E.g.</em>, when <code>LogLevel info</code> is specified,
2754 then messages with log levels of <code>notice</code> and
2755 <code>warn</code> will also be posted.</p>
2757 <p>Using a level of at least <code>crit</code> is
2762 <div class="example"><p><code>
2766 <div class="note"><h3>Note</h3>
2767 <p>When logging to a regular file messages of the level
2768 <code>notice</code> cannot be suppressed and thus are always
2769 logged. However, this doesn't apply when logging is done
2770 using <code>syslog</code>.</p>
2773 <p>Specifying a level without a module name will reset the level
2774 for all modules to that level. Specifying a level with a module
2775 name will set the level for that module only. It is possible to
2776 use the module source file name, the module identifier, or the
2777 module identifier with the trailing <code>_module</code> omitted
2778 as module specification. This means the following three specifications
2781 <div class="example"><p><code>
2782 LogLevel info ssl:warn<br />
2783 LogLevel info mod_ssl.c:warn<br />
2784 LogLevel info ssl_module:warn<br />
2787 <p>It is also possible to change the level per directory:</p>
2789 <div class="example"><p><code>
2791 <Directory /usr/local/apache/htdocs/app><br />
2792 LogLevel debug<br />
2797 Per directory loglevel configuration only affects messages that are
2798 logged after the request has been parsed and that are associated with
2799 the request. Log messages which are associated with the connection or
2800 the server are not affected.
2804 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2805 <div class="directive-section"><h2><a name="LogLevelOverride" id="LogLevelOverride">LogLevelOverride</a> <a name="logleveloverride" id="logleveloverride">Directiva</a></h2>
2806 <table class="directive">
2807 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Override the verbosity of the ErrorLog for certain clients</td></tr>
2808 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>LogLevel <var>ipaddress</var>[/<var>prefixlen</var>]
2809 [<var>module</var>:]<var>level</var> [<var>module</var>:<var>level</var>] ...
2811 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>unset</code></td></tr>
2812 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2813 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2814 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2815 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.5.0 and later</td></tr>
2816 </table><p>The documentation for this directive has
2817 not been translated yet. Please have a look at the English
2818 version.</p><h3>Consulte también</h3>
2820 <li><code class="directive"><a href="#loglevel">LogLevel</a></code></li>
2823 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2824 <div class="directive-section"><h2><a name="MaxKeepAliveRequests" id="MaxKeepAliveRequests">MaxKeepAliveRequests</a> <a name="maxkeepaliverequests" id="maxkeepaliverequests">Directiva</a></h2>
2825 <table class="directive">
2826 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Number of requests allowed on a persistent
2827 connection</td></tr>
2828 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>MaxKeepAliveRequests <var>number</var></code></td></tr>
2829 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>MaxKeepAliveRequests 100</code></td></tr>
2830 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2831 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2832 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2834 <p>The <code class="directive">MaxKeepAliveRequests</code> directive
2835 limits the number of requests allowed per connection when
2836 <code class="directive"><a href="#keepalive">KeepAlive</a></code> is on. If it is
2837 set to <code>0</code>, unlimited requests will be allowed. We
2838 recommend that this setting be kept to a high value for maximum
2839 server performance.</p>
2843 <div class="example"><p><code>
2844 MaxKeepAliveRequests 500
2848 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2849 <div class="directive-section"><h2><a name="MaxRangeOverlaps" id="MaxRangeOverlaps">MaxRangeOverlaps</a> <a name="maxrangeoverlaps" id="maxrangeoverlaps">Directiva</a></h2>
2850 <table class="directive">
2851 <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
2853 <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>
2854 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>MaxRangeOverlaps 20</code></td></tr>
2855 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
2856 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2857 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2858 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache HTTP Server 2.3.15 and later</td></tr>
2859 </table><p>The documentation for this directive has
2860 not been translated yet. Please have a look at the English
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="MaxRangeReversals" id="MaxRangeReversals">MaxRangeReversals</a> <a name="maxrangereversals" id="maxrangereversals">Directiva</a></h2>
2864 <table class="directive">
2865 <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
2867 <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>
2868 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>MaxRangeReversals 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="MaxRanges" id="MaxRanges">MaxRanges</a> <a name="maxranges" id="maxranges">Directiva</a></h2>
2878 <table class="directive">
2879 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Number of ranges allowed before returning the complete
2881 <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>
2882 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>MaxRanges 200</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="MergeTrailers" id="MergeTrailers">MergeTrailers</a> <a name="mergetrailers" id="mergetrailers">Directiva</a></h2>
2892 <table class="directive">
2893 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determines whether trailers are merged into headers</td></tr>
2894 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>MergeTrailers [on|off]</code></td></tr>
2895 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>MergeTrailers off</code></td></tr>
2896 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
2897 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
2898 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
2899 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>2.4.11 and later</td></tr>
2900 </table><p>The documentation for this directive has
2901 not been translated yet. Please have a look at the English
2903 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
2904 <div class="directive-section"><h2><a name="Mutex" id="Mutex">Mutex</a> <a name="mutex" id="mutex">Directiva</a></h2>
2905 <table class="directive">
2906 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures mutex mechanism and lock file directory for all
2907 or specified mutexes</td></tr>
2908 <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>
2909 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Mutex default</code></td></tr>
2910 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</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>Available in Apache HTTP Server 2.3.4 and later</td></tr>
2915 <p>The <code class="directive">Mutex</code> directive sets the mechanism,
2916 and optionally the lock file location, that httpd and modules use
2917 to serialize access to resources. Specify <code>default</code> as
2918 the first argument to change the settings for all mutexes; specify
2919 a mutex name (see table below) as the first argument to override
2920 defaults only for that mutex.</p>
2922 <p>The <code class="directive">Mutex</code> directive is typically used in
2923 the following exceptional situations:</p>
2926 <li>change the mutex mechanism when the default mechanism selected
2927 by <a class="glossarylink" href="../glossary.html#apr" title="ver glosario">APR</a> has a functional or performance
2930 <li>change the directory used by file-based mutexes when the
2931 default directory does not support locking</li>
2934 <div class="note"><h3>Supported modules</h3>
2935 <p>This directive only configures mutexes which have been registered
2936 with the core server using the <code>ap_mutex_register()</code> API.
2937 All modules bundled with httpd support the <code class="directive">Mutex</code>
2938 directive, but third-party modules may not. Consult the documentation
2939 of the third-party module, which must indicate the mutex name(s) which
2940 can be configured if this directive is supported.</p>
2943 <p>The following mutex <em>mechanisms</em> are available:</p>
2945 <li><code>default | yes</code>
2946 <p>This selects the default locking implementation, as determined by
2947 <a class="glossarylink" href="../glossary.html#apr" title="ver glosario">APR</a>. The default locking implementation can
2948 be displayed by running <code class="program"><a href="../programs/httpd.html">httpd</a></code> with the
2949 <code>-V</code> option.</p></li>
2951 <li><code>none | no</code>
2952 <p>This effectively disables the mutex, and is only allowed for a
2953 mutex if the module indicates that it is a valid choice. Consult the
2954 module documentation for more information.</p></li>
2956 <li><code>posixsem</code>
2957 <p>This is a mutex variant based on a Posix semaphore.</p>
2959 <div class="warning"><h3>Warning</h3>
2960 <p>The semaphore ownership is not recovered if a thread in the process
2961 holding the mutex segfaults, resulting in a hang of the web server.</p>
2965 <li><code>sysvsem</code>
2966 <p>This is a mutex variant based on a SystemV IPC semaphore.</p>
2968 <div class="warning"><h3>Warning</h3>
2969 <p>It is possible to "leak" SysV semaphores if processes crash
2970 before the semaphore is removed.</p>
2973 <div class="warning"><h3>Security</h3>
2974 <p>The semaphore API allows for a denial of service attack by any
2975 CGIs running under the same uid as the webserver (<em>i.e.</em>,
2976 all CGIs, unless you use something like <code class="program"><a href="../programs/suexec.html">suexec</a></code>
2977 or <code>cgiwrapper</code>).</p>
2981 <li><code>sem</code>
2982 <p>This selects the "best" available semaphore implementation, choosing
2983 between Posix and SystemV IPC semaphores, in that order.</p></li>
2985 <li><code>pthread</code>
2986 <p>This is a mutex variant based on cross-process Posix thread
2989 <div class="warning"><h3>Warning</h3>
2990 <p>On most systems, if a child process terminates abnormally while
2991 holding a mutex that uses this implementation, the server will deadlock
2992 and stop responding to requests. When this occurs, the server will
2993 require a manual restart to recover.</p>
2994 <p>Solaris is a notable exception as it provides a mechanism which
2995 usually allows the mutex to be recovered after a child process
2996 terminates abnormally while holding a mutex.</p>
2997 <p>If your system implements the
2998 <code>pthread_mutexattr_setrobust_np()</code> function, you may be able
2999 to use the <code>pthread</code> option safely.</p>
3003 <li><code>fcntl:/path/to/mutex</code>
3004 <p>This is a mutex variant where a physical (lock-)file and the
3005 <code>fcntl()</code> function are used as the mutex.</p>
3007 <div class="warning"><h3>Warning</h3>
3008 <p>When multiple mutexes based on this mechanism are used within
3009 multi-threaded, multi-process environments, deadlock errors (EDEADLK)
3010 can be reported for valid mutex operations if <code>fcntl()</code>
3011 is not thread-aware, such as on Solaris.</p>
3015 <li><code>flock:/path/to/mutex</code>
3016 <p>This is similar to the <code>fcntl:/path/to/mutex</code> method
3017 with the exception that the <code>flock()</code> function is used to
3018 provide file locking.</p></li>
3020 <li><code>file:/path/to/mutex</code>
3021 <p>This selects the "best" available file locking implementation,
3022 choosing between <code>fcntl</code> and <code>flock</code>, in that
3026 <p>Most mechanisms are only available on selected platforms, where the
3027 underlying platform and <a class="glossarylink" href="../glossary.html#apr" title="ver glosario">APR</a> support it. Mechanisms
3028 which aren't available on all platforms are <em>posixsem</em>,
3029 <em>sysvsem</em>, <em>sem</em>, <em>pthread</em>, <em>fcntl</em>,
3030 <em>flock</em>, and <em>file</em>.</p>
3032 <p>With the file-based mechanisms <em>fcntl</em> and <em>flock</em>,
3033 the path, if provided, is a directory where the lock file will be created.
3034 The default directory is httpd's run-time file directory relative to
3035 <code class="directive"><a href="#serverroot">ServerRoot</a></code>. Always use a local disk
3036 filesystem for <code>/path/to/mutex</code> and never a directory residing
3037 on a NFS- or AFS-filesystem. The basename of the file will be the mutex
3038 type, an optional instance string provided by the module, and unless the
3039 <code>OmitPID</code> keyword is specified, the process id of the httpd
3040 parent process will be appended to to make the file name unique, avoiding
3041 conflicts when multiple httpd instances share a lock file directory. For
3042 example, if the mutex name is <code>mpm-accept</code> and the lock file
3043 directory is <code>/var/httpd/locks</code>, the lock file name for the
3044 httpd instance with parent process id 12345 would be
3045 <code>/var/httpd/locks/mpm-accept.12345</code>.</p>
3047 <div class="warning"><h3>Security</h3>
3048 <p>It is best to <em>avoid</em> putting mutex files in a world-writable
3049 directory such as <code>/var/tmp</code> because someone could create
3050 a denial of service attack and prevent the server from starting by
3051 creating a lockfile with the same name as the one the server will try
3055 <p>The following table documents the names of mutexes used by httpd
3056 and bundled modules.</p>
3058 <table class="bordered"><tr class="header">
3061 <th>Protected resource</th>
3064 <td><code>mpm-accept</code></td>
3065 <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>
3066 <td>incoming connections, to avoid the thundering herd problem;
3067 for more information, refer to the
3068 <a href="../misc/perf-tuning.html">performance tuning</a>
3072 <td><code>authdigest-client</code></td>
3073 <td><code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code></td>
3074 <td>client list in shared memory</td>
3077 <td><code>authdigest-opaque</code></td>
3078 <td><code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code></td>
3079 <td>counter in shared memory</td>
3082 <td><code>ldap-cache</code></td>
3083 <td><code class="module"><a href="../mod/mod_ldap.html">mod_ldap</a></code></td>
3084 <td>LDAP result cache</td>
3087 <td><code>rewrite-map</code></td>
3088 <td><code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code></td>
3089 <td>communication with external mapping programs, to avoid
3090 intermixed I/O from multiple requests</td>
3093 <td><code>ssl-cache</code></td>
3094 <td><code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code></td>
3095 <td>SSL session cache</td>
3098 <td><code>ssl-stapling</code></td>
3099 <td><code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code></td>
3100 <td>OCSP stapling response cache</td>
3103 <td><code>watchdog-callback</code></td>
3104 <td><code class="module"><a href="../mod/mod_watchdog.html">mod_watchdog</a></code></td>
3105 <td>callback function of a particular client module</td>
3109 <p>The <code>OmitPID</code> keyword suppresses the addition of the httpd
3110 parent process id from the lock file name.</p>
3112 <p>In the following example, the mutex mechanism for the MPM accept
3113 mutex will be changed from the compiled-in default to <code>fcntl</code>,
3114 with the associated lock file created in directory
3115 <code>/var/httpd/locks</code>. The mutex mechanism for all other mutexes
3116 will be changed from the compiled-in default to <code>sysvsem</code>.</p>
3118 <div class="example"><p><code>
3119 Mutex default sysvsem<br />
3120 Mutex mpm-accept fcntl:/var/httpd/locks
3124 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3125 <div class="directive-section"><h2><a name="NameVirtualHost" id="NameVirtualHost">NameVirtualHost</a> <a name="namevirtualhost" id="namevirtualhost">Directiva</a></h2>
3126 <table class="directive">
3127 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Designates an IP address for name-virtual
3129 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>NameVirtualHost <var>addr</var>[:<var>port</var>]</code></td></tr>
3130 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
3131 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3132 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3135 <p>A single <code class="directive">NameVirtualHost</code> directive
3136 identifies a set of identical virtual hosts on which the server will
3137 further select from on the basis of the <em>hostname</em>
3138 requested by the client. The <code class="directive">NameVirtualHost</code>
3139 directive is a required directive if you want to configure
3140 <a href="../vhosts/">name-based virtual hosts</a>.</p>
3142 <p>This directive, and the corresponding <code class="directive">VirtualHost</code>,
3143 <em>must</em> be qualified with a port number if the server supports both HTTP
3144 and HTTPS connections.</p>
3146 <p>Although <var>addr</var> can be a hostname, it is recommended
3147 that you always use an IP address or a wildcard. A wildcard
3148 NameVirtualHost matches only virtualhosts that also have a literal wildcard
3149 as their argument.</p>
3151 <p>In cases where a firewall or other proxy receives the requests and
3152 forwards them on a different IP address to the server, you must specify the
3153 IP address of the physical interface on the machine which will be
3154 servicing the requests. </p>
3156 <p> In the example below, requests received on interface 192.0.2.1 and port 80
3157 will only select among the first two virtual hosts. Requests received on
3158 port 80 on any other interface will only select among the third and fourth
3159 virtual hosts. In the common case where the interface isn't important
3160 to the mapping, only the "*:80" NameVirtualHost and VirtualHost directives
3163 <div class="example"><p><code>
3164 NameVirtualHost 192.0.2.1:80<br />
3165 NameVirtualHost *:80<br /><br />
3167 <VirtualHost 192.0.2.1:80><br />
3168 ServerName namebased-a.example.com<br />
3169 </VirtualHost><br />
3171 <VirtualHost 192.0.2.1:80><br />
3172 Servername namebased-b.example.com<br />
3173 </VirtualHost><br />
3175 <VirtualHost *:80><br />
3176 ServerName namebased-c.example.com <br />
3177 </VirtualHost><br />
3179 <VirtualHost *:80><br />
3180 ServerName namebased-d.example.com <br />
3181 </VirtualHost><br />
3186 <p>If no matching virtual host is found, then the first listed
3187 virtual host that matches the IP address and port will be used.</p>
3190 <p>IPv6 addresses must be enclosed in square brackets, as shown
3191 in the following example:</p>
3193 <div class="example"><p><code>
3194 NameVirtualHost [2001:db8::a00:20ff:fea7:ccea]:8080
3197 <div class="note"><h3>Argument to <code class="directive"><VirtualHost></code>
3199 <p>Note that the argument to the <code class="directive"><VirtualHost></code> directive must
3200 exactly match the argument to the <code class="directive">NameVirtualHost</code> directive.</p>
3202 <div class="example"><p><code>
3203 NameVirtualHost 192.0.2.2:80<br />
3204 <VirtualHost 192.0.2.2:80><br />
3206 </VirtualHost><br />
3210 <h3>Consulte también</h3>
3212 <li><a href="../vhosts/">Virtual Hosts
3213 documentation</a></li>
3216 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3217 <div class="directive-section"><h2><a name="Options" id="Options">Options</a> <a name="options" id="options">Directiva</a></h2>
3218 <table class="directive">
3219 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures what features are available in a particular
3221 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Options
3222 [+|-]<var>option</var> [[+|-]<var>option</var>] ...</code></td></tr>
3223 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Options All</code></td></tr>
3224 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3225 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>Options</td></tr>
3226 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3227 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3229 <p>The <code class="directive">Options</code> directive controls which
3230 server features are available in a particular directory.</p>
3232 <p><var>option</var> can be set to <code>None</code>, in which
3233 case none of the extra features are enabled, or one or more of
3237 <dt><code>All</code></dt>
3239 <dd>All options except for <code>MultiViews</code>. This is the default
3242 <dt><code>ExecCGI</code></dt>
3245 Execution of CGI scripts using <code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code>
3248 <dt><code>FollowSymLinks</code></dt>
3252 The server will follow symbolic links in this directory.
3254 <p>Even though the server follows the symlink it does <em>not</em>
3255 change the pathname used to match against <code class="directive"><a href="#directory"><Directory></a></code> sections.</p>
3256 <p>Note also, that this option <strong>gets ignored</strong> if set
3257 inside a <code class="directive"><a href="#location"><Location></a></code>
3259 <p>Omitting this option should not be considered a security restriction,
3260 since symlink testing is subject to race conditions that make it
3264 <dt><code>Includes</code></dt>
3267 Server-side includes provided by <code class="module"><a href="../mod/mod_include.html">mod_include</a></code>
3270 <dt><code>IncludesNOEXEC</code></dt>
3274 Server-side includes are permitted, but the <code>#exec
3275 cmd</code> and <code>#exec cgi</code> are disabled. It is still
3276 possible to <code>#include virtual</code> CGI scripts from
3277 <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code>ed
3280 <dt><code>Indexes</code></dt>
3283 If a URL which maps to a directory is requested, and there
3284 is no <code class="directive"><a href="../mod/mod_dir.html#directoryindex">DirectoryIndex</a></code>
3285 (<em>e.g.</em>, <code>index.html</code>) in that directory, then
3286 <code class="module"><a href="../mod/mod_autoindex.html">mod_autoindex</a></code> will return a formatted listing
3287 of the directory.</dd>
3289 <dt><code>MultiViews</code></dt>
3292 <a href="../content-negotiation.html">Content negotiated</a>
3293 "MultiViews" are allowed using
3294 <code class="module"><a href="../mod/mod_negotiation.html">mod_negotiation</a></code>.
3295 <div class="note"><h3>Note</h3> <p>This option gets ignored if set
3296 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>
3297 needs real resources to compare against and evaluate from.</p></div>
3300 <dt><code>SymLinksIfOwnerMatch</code></dt>
3302 <dd>The server will only follow symbolic links for which the
3303 target file or directory is owned by the same user id as the
3306 <div class="note"><h3>Note</h3> <p>This option gets ignored if
3307 set inside a <code class="directive"><a href="#location"><Location></a></code> section.</p>
3308 <p>This option should not be considered a security restriction,
3309 since symlink testing is subject to race conditions that make it
3310 circumventable.</p></div>
3314 <p>Normally, if multiple <code class="directive">Options</code> could
3315 apply to a directory, then the most specific one is used and
3316 others are ignored; the options are not merged. (See <a href="../sections.html#mergin">how sections are merged</a>.)
3317 However if <em>all</em> the options on the
3318 <code class="directive">Options</code> directive are preceded by a
3319 <code>+</code> or <code>-</code> symbol, the options are
3320 merged. Any options preceded by a <code>+</code> are added to the
3321 options currently in force, and any options preceded by a
3322 <code>-</code> are removed from the options currently in
3325 <div class="warning"><h3>Warning</h3>
3326 <p>Mixing <code class="directive">Options</code> with a <code>+</code> or
3327 <code>-</code> with those without is not valid syntax, and is likely
3328 to cause unexpected results.</p>
3331 <p>For example, without any <code>+</code> and <code>-</code> symbols:</p>
3333 <div class="example"><p><code>
3334 <Directory /web/docs><br />
3335 <span class="indent">
3336 Options Indexes FollowSymLinks<br />
3338 </Directory><br />
3340 <Directory /web/docs/spec><br />
3341 <span class="indent">
3342 Options Includes<br />
3347 <p>then only <code>Includes</code> will be set for the
3348 <code>/web/docs/spec</code> directory. However if the second
3349 <code class="directive">Options</code> directive uses the <code>+</code> and
3350 <code>-</code> symbols:</p>
3352 <div class="example"><p><code>
3353 <Directory /web/docs><br />
3354 <span class="indent">
3355 Options Indexes FollowSymLinks<br />
3357 </Directory><br />
3359 <Directory /web/docs/spec><br />
3360 <span class="indent">
3361 Options +Includes -Indexes<br />
3366 <p>then the options <code>FollowSymLinks</code> and
3367 <code>Includes</code> are set for the <code>/web/docs/spec</code>
3370 <div class="note"><h3>Note</h3>
3371 <p>Using <code>-IncludesNOEXEC</code> or
3372 <code>-Includes</code> disables server-side includes completely
3373 regardless of the previous setting.</p>
3376 <p>The default in the absence of any other settings is
3377 <code>All</code>.</p>
3380 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3381 <div class="directive-section"><h2><a name="Protocol" id="Protocol">Protocol</a> <a name="protocol" id="protocol">Directiva</a></h2>
3382 <table class="directive">
3383 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Protocol for a listening socket</td></tr>
3384 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Protocol <var>protocol</var></code></td></tr>
3385 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
3386 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3387 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3388 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache 2.1.5 and later.
3389 On Windows from Apache 2.3.3 and later.</td></tr>
3391 <p>This directive specifies the protocol used for a specific listening socket.
3392 The protocol is used to determine which module should handle a request, and
3393 to apply protocol specific optimizations with the <code class="directive">AcceptFilter</code>
3396 <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>
3398 <p>For example, if you are running <code>https</code> on a non-standard port, specify the protocol explicitly:</p>
3400 <div class="example"><p><code>
3404 <p>You can also specify the protocol using the <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> directive.</p>
3406 <h3>Consulte también</h3>
3408 <li><code class="directive">AcceptFilter</code></li>
3409 <li><code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code></li>
3412 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3413 <div class="directive-section"><h2><a name="Protocols" id="Protocols">Protocols</a> <a name="protocols" id="protocols">Directiva</a></h2>
3414 <table class="directive">
3415 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Protocols available for a server/virtual host</td></tr>
3416 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Protocols <var>protocol</var> ...</code></td></tr>
3417 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Protocols http/1.1</code></td></tr>
3418 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
3419 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3420 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3421 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Only available from Apache 2.4.17 and later.</td></tr>
3422 </table><p>The documentation for this directive has
3423 not been translated yet. Please have a look at the English
3424 version.</p><h3>Consulte también</h3>
3426 <li><code class="directive"><a href="#protocolshonororder">ProtocolsHonorOrder</a></code></li>
3429 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3430 <div class="directive-section"><h2><a name="ProtocolsHonorOrder" id="ProtocolsHonorOrder">ProtocolsHonorOrder</a> <a name="protocolshonororder" id="protocolshonororder">Directiva</a></h2>
3431 <table class="directive">
3432 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determines if order of Protocols determines precedence during negotiation</td></tr>
3433 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ProtocolsHonorOrder On|Off</code></td></tr>
3434 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ProtocolsHonorOrder On</code></td></tr>
3435 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
3436 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3437 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3438 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Only available from Apache 2.4.17 and later.</td></tr>
3439 </table><p>The documentation for this directive has
3440 not been translated yet. Please have a look at the English
3441 version.</p><h3>Consulte también</h3>
3443 <li><code class="directive"><a href="#protocols">Protocols</a></code></li>
3446 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3447 <div class="directive-section"><h2><a name="QualifyRedirectURL" id="QualifyRedirectURL">QualifyRedirectURL</a> <a name="qualifyredirecturl" id="qualifyredirecturl">Directiva</a></h2>
3448 <table class="directive">
3449 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Controls whether the REDIRECT_URL environent variable is
3450 fully qualified</td></tr>
3451 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>QualifyRedirectURL ON|OFF</code></td></tr>
3452 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>QualifyRedirectURL OFF</code></td></tr>
3453 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
3454 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
3455 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3456 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3457 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Directive supported in 2.4.18 and later. 2.4.17 acted
3458 as if 'QualifyRedirectURL ON' was configured.</td></tr>
3459 </table><p>The documentation for this directive has
3460 not been translated yet. Please have a look at the English
3462 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3463 <div class="directive-section"><h2><a name="RegisterHttpMethod" id="RegisterHttpMethod">RegisterHttpMethod</a> <a name="registerhttpmethod" id="registerhttpmethod">Directiva</a></h2>
3464 <table class="directive">
3465 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Register non-standard HTTP methods</td></tr>
3466 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>RegisterHttpMethod <var>method</var> [<var>method</var> [...]]</code></td></tr>
3467 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
3468 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3469 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3470 </table><p>The documentation for this directive has
3471 not been translated yet. Please have a look at the English
3473 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3474 <div class="directive-section"><h2><a name="RLimitCPU" id="RLimitCPU">RLimitCPU</a> <a name="rlimitcpu" id="rlimitcpu">Directiva</a></h2>
3475 <table class="directive">
3476 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the CPU consumption of processes launched
3477 by Apache httpd children</td></tr>
3478 <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>
3479 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Unset; uses operating system defaults</code></td></tr>
3480 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3481 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</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>
3485 <p>Takes 1 or 2 parameters. The first parameter sets the soft
3486 resource limit for all processes and the second parameter sets
3487 the maximum resource limit. Either parameter can be a number,
3488 or <code>max</code> to indicate to the server that the limit should
3489 be set to the maximum allowed by the operating system
3490 configuration. Raising the maximum resource limit requires that
3491 the server is running as <code>root</code>, or in the initial startup
3494 <p>This applies to processes forked off from Apache httpd children
3495 servicing requests, not the Apache httpd children themselves. This
3496 includes CGI scripts and SSI exec commands, but not any
3497 processes forked off from the Apache httpd parent such as piped
3500 <p>CPU resource limits are expressed in seconds per
3503 <h3>Consulte también</h3>
3505 <li><code class="directive"><a href="#rlimitmem">RLimitMEM</a></code></li>
3506 <li><code class="directive"><a href="#rlimitnproc">RLimitNPROC</a></code></li>
3509 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3510 <div class="directive-section"><h2><a name="RLimitMEM" id="RLimitMEM">RLimitMEM</a> <a name="rlimitmem" id="rlimitmem">Directiva</a></h2>
3511 <table class="directive">
3512 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the memory consumption of processes launched
3513 by Apache httpd children</td></tr>
3514 <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>
3515 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Unset; uses operating system defaults</code></td></tr>
3516 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3517 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
3518 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3519 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3521 <p>Takes 1 or 2 parameters. The first parameter sets the soft
3522 resource limit for all processes and the second parameter sets
3523 the maximum resource limit. Either parameter can be a number,
3524 or <code>max</code> to indicate to the server that the limit should
3525 be set to the maximum allowed by the operating system
3526 configuration. Raising the maximum resource limit requires that
3527 the server is running as <code>root</code>, or in the initial startup
3530 <p>This applies to processes forked off from Apache httpd children
3531 servicing requests, not the Apache httpd children themselves. This
3532 includes CGI scripts and SSI exec commands, but not any
3533 processes forked off from the Apache httpd parent such as piped
3536 <p>Memory resource limits are expressed in bytes per
3539 <h3>Consulte también</h3>
3541 <li><code class="directive"><a href="#rlimitcpu">RLimitCPU</a></code></li>
3542 <li><code class="directive"><a href="#rlimitnproc">RLimitNPROC</a></code></li>
3545 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3546 <div class="directive-section"><h2><a name="RLimitNPROC" id="RLimitNPROC">RLimitNPROC</a> <a name="rlimitnproc" id="rlimitnproc">Directiva</a></h2>
3547 <table class="directive">
3548 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Limits the number of processes that can be launched by
3549 processes launched by Apache httpd children</td></tr>
3550 <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>
3551 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>Unset; uses operating system defaults</code></td></tr>
3552 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3553 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
3554 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3555 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3557 <p>Takes 1 or 2 parameters. The first parameter sets the soft
3558 resource limit for all processes and the second parameter sets
3559 the maximum resource limit. Either parameter can be a number,
3560 or <code>max</code> to indicate to the server that the limit
3561 should be set to the maximum allowed by the operating system
3562 configuration. Raising the maximum resource limit requires that
3563 the server is running as <code>root</code>, or in the initial startup
3566 <p>This applies to processes forked off from Apache httpd children
3567 servicing requests, not the Apache httpd children themselves. This
3568 includes CGI scripts and SSI exec commands, but not any
3569 processes forked off from the Apache httpd parent such as piped
3572 <p>Process limits control the number of processes per user.</p>
3574 <div class="note"><h3>Note</h3>
3575 <p>If CGI processes are <strong>not</strong> running
3576 under user ids other than the web server user id, this directive
3577 will limit the number of processes that the server itself can
3578 create. Evidence of this situation will be indicated by
3579 <strong><code>cannot fork</code></strong> messages in the
3580 <code>error_log</code>.</p>
3583 <h3>Consulte también</h3>
3585 <li><code class="directive"><a href="#rlimitmem">RLimitMEM</a></code></li>
3586 <li><code class="directive"><a href="#rlimitcpu">RLimitCPU</a></code></li>
3589 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3590 <div class="directive-section"><h2><a name="ScriptInterpreterSource" id="ScriptInterpreterSource">ScriptInterpreterSource</a> <a name="scriptinterpretersource" id="scriptinterpretersource">Directiva</a></h2>
3591 <table class="directive">
3592 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Technique for locating the interpreter for CGI
3594 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ScriptInterpreterSource Registry|Registry-Strict|Script</code></td></tr>
3595 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ScriptInterpreterSource Script</code></td></tr>
3596 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3597 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
3598 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3599 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3600 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Win32 only;
3601 option <code>Registry-Strict</code> is available in Apache HTTP Server 2.0 and
3604 <p>This directive is used to control how Apache httpd finds the
3605 interpreter used to run CGI scripts. The default setting is
3606 <code>Script</code>. This causes Apache httpd to use the interpreter pointed to
3607 by the shebang line (first line, starting with <code>#!</code>) in the
3608 script. On Win32 systems this line usually looks like:</p>
3610 <div class="example"><p><code>
3611 #!C:/Perl/bin/perl.exe
3614 <p>or, if <code>perl</code> is in the <code>PATH</code>, simply:</p>
3616 <div class="example"><p><code>
3620 <p>Setting <code>ScriptInterpreterSource Registry</code> will
3621 cause the Windows Registry tree <code>HKEY_CLASSES_ROOT</code> to be
3622 searched using the script file extension (e.g., <code>.pl</code>) as a
3623 search key. The command defined by the registry subkey
3624 <code>Shell\ExecCGI\Command</code> or, if it does not exist, by the subkey
3625 <code>Shell\Open\Command</code> is used to open the script file. If the
3626 registry keys cannot be found, Apache httpd falls back to the behavior of the
3627 <code>Script</code> option.</p>
3629 <div class="warning"><h3>Security</h3>
3630 <p>Be careful when using <code>ScriptInterpreterSource
3631 Registry</code> with <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code>'ed directories, because
3632 Apache httpd will try to execute <strong>every</strong> file within this
3633 directory. The <code>Registry</code> setting may cause undesired
3634 program calls on files which are typically not executed. For
3635 example, the default open command on <code>.htm</code> files on
3636 most Windows systems will execute Microsoft Internet Explorer, so
3637 any HTTP request for an <code>.htm</code> file existing within the
3638 script directory would start the browser in the background on the
3639 server. This is a good way to crash your system within a minute or
3643 <p>The option <code>Registry-Strict</code> which is new in Apache HTTP Server
3644 2.0 does the same thing as <code>Registry</code> but uses only the
3645 subkey <code>Shell\ExecCGI\Command</code>. The
3646 <code>ExecCGI</code> key is not a common one. It must be
3647 configured manually in the windows registry and hence prevents
3648 accidental program calls on your system.</p>
3651 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3652 <div class="directive-section"><h2><a name="SeeRequestTail" id="SeeRequestTail">SeeRequestTail</a> <a name="seerequesttail" id="seerequesttail">Directiva</a></h2>
3653 <table class="directive">
3654 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determine if mod_status displays the first 63 characters
3655 of a request or the last 63, assuming the request itself is greater than
3657 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>SeeRequestTail On|Off</code></td></tr>
3658 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>SeeRequestTail Off</code></td></tr>
3659 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
3660 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3661 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3662 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Available in Apache httpd 2.2.7 and later.</td></tr>
3664 <p>mod_status with <code>ExtendedStatus On</code>
3665 displays the actual request being handled.
3666 For historical purposes, only 63 characters of the request
3667 are actually stored for display purposes. This directive
3668 controls whether the 1st 63 characters are stored (the previous
3669 behavior and the default) or if the last 63 characters are. This
3670 is only applicable, of course, if the length of the request is
3671 64 characters or greater.</p>
3673 <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:
3676 <table class="bordered">
3678 <th>Off (default)</th>
3679 <td>GET /disk1/storage/apache/htdocs/images/imagestore1/food/apples</td>
3683 <td>orage/apache/htdocs/images/imagestore1/food/apples.jpg HTTP/1.1</td>
3689 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3690 <div class="directive-section"><h2><a name="ServerAdmin" id="ServerAdmin">ServerAdmin</a> <a name="serveradmin" id="serveradmin">Directiva</a></h2>
3691 <table class="directive">
3692 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Email address that the server includes in error
3693 messages sent to the client</td></tr>
3694 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ServerAdmin <var>email-address</var>|<var>URL</var></code></td></tr>
3695 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
3696 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3697 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3699 <p>The <code class="directive">ServerAdmin</code> sets the contact address
3700 that the server includes in any error messages it returns to the
3701 client. If the <code>httpd</code> doesn't recognize the supplied argument
3703 assumes, that it's an <var>email-address</var> and prepends it with
3704 <code>mailto:</code> in hyperlink targets. However, it's recommended to
3705 actually use an email address, since there are a lot of CGI scripts that
3706 make that assumption. If you want to use an URL, it should point to another
3707 server under your control. Otherwise users may not be able to contact you in
3710 <p>It may be worth setting up a dedicated address for this, e.g.</p>
3712 <div class="example"><p><code>
3713 ServerAdmin www-admin@foo.example.com
3715 <p>as users do not always mention that they are talking about the
3719 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3720 <div class="directive-section"><h2><a name="ServerAlias" id="ServerAlias">ServerAlias</a> <a name="serveralias" id="serveralias">Directiva</a></h2>
3721 <table class="directive">
3722 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Alternate names for a host used when matching requests
3723 to name-virtual hosts</td></tr>
3724 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ServerAlias <var>hostname</var> [<var>hostname</var>] ...</code></td></tr>
3725 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>virtual host</td></tr>
3726 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3727 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3729 <p>The <code class="directive">ServerAlias</code> directive sets the
3730 alternate names for a host, for use with <a href="../vhosts/name-based.html">name-based virtual hosts</a>. The
3731 <code class="directive">ServerAlias</code> may include wildcards, if appropriate.</p>
3733 <div class="example"><p><code>
3734 <VirtualHost *:80><br />
3735 ServerName server.domain.com<br />
3736 ServerAlias server server2.domain.com server2<br />
3737 ServerAlias *.example.com<br />
3738 UseCanonicalName Off<br />
3740 </VirtualHost>
3743 <h3>Consulte también</h3>
3745 <li><code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code></li>
3746 <li><a href="../vhosts/">Apache HTTP Server Virtual Host documentation</a></li>
3749 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3750 <div class="directive-section"><h2><a name="ServerName" id="ServerName">ServerName</a> <a name="servername" id="servername">Directiva</a></h2>
3751 <table class="directive">
3752 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Hostname and port that the server uses to identify
3754 <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>
3755 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
3756 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3757 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3759 <p>The <code class="directive">ServerName</code> directive sets the
3760 request scheme, hostname and
3761 port that the server uses to identify itself. This is used when
3762 creating redirection URLs.</p>
3764 <p>Additionally, <code class="directive">ServerName</code> is used (possibly
3765 in conjunction with <code class="directive">ServerAlias</code>) to uniquely
3766 identify a virtual host, when using <a href="../vhosts/name-based.html">name-based virtual hosts</a>.</p>
3768 <p>For example, if the name of the
3769 machine hosting the web server is <code>simple.example.com</code>,
3770 but the machine also has the DNS alias <code>www.example.com</code>
3771 and you wish the web server to be so identified, the following
3772 directive should be used:</p>
3774 <div class="example"><p><code>
3775 ServerName www.example.com:80
3778 <p>The <code class="directive">ServerName</code> directive
3779 may appear anywhere within the definition of a server. However,
3780 each appearance overrides the previous appearance (within that
3783 <p>If no <code class="directive">ServerName</code> is specified, then the
3784 server attempts to deduce the hostname by performing a reverse
3785 lookup on the IP address. If no port is specified in the
3786 <code class="directive">ServerName</code>, then the server will use the
3787 port from the incoming request. For optimal reliability and
3788 predictability, you should specify an explicit hostname and port
3789 using the <code class="directive">ServerName</code> directive.</p>
3791 <p>If you are using <a href="../vhosts/name-based.html">name-based virtual hosts</a>,
3792 the <code class="directive">ServerName</code> inside a
3793 <code class="directive"><a href="#virtualhost"><VirtualHost></a></code>
3794 section specifies what hostname must appear in the request's
3795 <code>Host:</code> header to match this virtual host.</p>
3797 <p>Sometimes, the server runs behind a device that processes SSL,
3798 such as a reverse proxy, load balancer or SSL offload
3799 appliance. When this is the case, specify the
3800 <code>https://</code> scheme and the port number to which the
3801 clients connect in the <code class="directive">ServerName</code> directive
3802 to make sure that the server generates the correct
3803 self-referential URLs.
3806 <p>See the description of the
3807 <code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code> and
3808 <code class="directive"><a href="#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></code> directives for
3809 settings which determine whether self-referential URLs (e.g., by the
3810 <code class="module"><a href="../mod/mod_dir.html">mod_dir</a></code> module) will refer to the
3811 specified port, or to the port number given in the client's request.
3814 <div class="warning">
3815 <p>Failure to set <code class="directive">ServerName</code> to a name that
3816 your server can resolve to an IP address will result in a startup
3817 warning. <code>httpd</code> will then use whatever hostname it can
3818 determine, using the system's <code>hostname</code> command. This
3819 will almost never be the hostname you actually want.</p>
3820 <div class="example"><p><code>
3821 httpd: Could not reliably determine the server's fully qualified domain name, using rocinante.local for ServerName
3826 <h3>Consulte también</h3>
3828 <li><a href="../dns-caveats.html">Issues Regarding DNS and
3829 Apache HTTP Server</a></li>
3830 <li><a href="../vhosts/">Apache HTTP Server virtual host
3831 documentation</a></li>
3832 <li><code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code></li>
3833 <li><code class="directive"><a href="#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></code></li>
3834 <li><code class="directive"><a href="#namevirtualhost">NameVirtualHost</a></code></li>
3835 <li><code class="directive"><a href="#serveralias">ServerAlias</a></code></li>
3838 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3839 <div class="directive-section"><h2><a name="ServerPath" id="ServerPath">ServerPath</a> <a name="serverpath" id="serverpath">Directiva</a></h2>
3840 <table class="directive">
3841 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Legacy URL pathname for a name-based virtual host that
3842 is accessed by an incompatible browser</td></tr>
3843 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ServerPath <var>URL-path</var></code></td></tr>
3844 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>virtual host</td></tr>
3845 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3846 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3848 <p>The <code class="directive">ServerPath</code> directive sets the legacy
3849 URL pathname for a host, for use with <a href="../vhosts/">name-based virtual hosts</a>.</p>
3851 <h3>Consulte también</h3>
3853 <li><a href="../vhosts/">Apache HTTP Server Virtual Host documentation</a></li>
3856 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3857 <div class="directive-section"><h2><a name="ServerRoot" id="ServerRoot">ServerRoot</a> <a name="serverroot" id="serverroot">Directiva</a></h2>
3858 <table class="directive">
3859 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Base directory for the server installation</td></tr>
3860 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ServerRoot <var>directory-path</var></code></td></tr>
3861 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ServerRoot /usr/local/apache</code></td></tr>
3862 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
3863 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3864 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3866 <p>The <code class="directive">ServerRoot</code> directive sets the
3867 directory in which the server lives. Typically it will contain the
3868 subdirectories <code>conf/</code> and <code>logs/</code>. Relative
3869 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
3870 relative to this directory.</p>
3872 <div class="example"><h3>Example</h3><p><code>
3873 ServerRoot /home/httpd
3877 <h3>Consulte también</h3>
3879 <li><a href="../invoking.html">the <code>-d</code>
3880 option to <code>httpd</code></a></li>
3881 <li><a href="../misc/security_tips.html#serverroot">the
3882 security tips</a> for information on how to properly set
3883 permissions on the <code class="directive">ServerRoot</code></li>
3886 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3887 <div class="directive-section"><h2><a name="ServerSignature" id="ServerSignature">ServerSignature</a> <a name="serversignature" id="serversignature">Directiva</a></h2>
3888 <table class="directive">
3889 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures the footer on server-generated documents</td></tr>
3890 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>ServerSignature On|Off|EMail</code></td></tr>
3891 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ServerSignature Off</code></td></tr>
3892 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3893 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>All</td></tr>
3894 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3895 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3897 <p>The <code class="directive">ServerSignature</code> directive allows the
3898 configuration of a trailing footer line under server-generated
3899 documents (error messages, <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> ftp directory
3900 listings, <code class="module"><a href="../mod/mod_info.html">mod_info</a></code> output, ...). The reason why you
3901 would want to enable such a footer line is that in a chain of proxies,
3902 the user often has no possibility to tell which of the chained servers
3903 actually produced a returned error message.</p>
3905 <p>The <code>Off</code>
3906 setting, which is the default, suppresses the footer line (and is
3907 therefore compatible with the behavior of Apache-1.2 and
3908 below). The <code>On</code> setting simply adds a line with the
3909 server version number and <code class="directive"><a href="#servername">ServerName</a></code> of the serving virtual host,
3910 and the <code>EMail</code> setting additionally creates a
3911 "mailto:" reference to the <code class="directive"><a href="#serveradmin">ServerAdmin</a></code> of the referenced
3914 <p>After version 2.0.44, the details of the server version number
3915 presented are controlled by the <code class="directive"><a href="#servertokens">ServerTokens</a></code> directive.</p>
3917 <h3>Consulte también</h3>
3919 <li><code class="directive"><a href="#servertokens">ServerTokens</a></code></li>
3922 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3923 <div class="directive-section"><h2><a name="ServerTokens" id="ServerTokens">ServerTokens</a> <a name="servertokens" id="servertokens">Directiva</a></h2>
3924 <table class="directive">
3925 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures the <code>Server</code> HTTP response
3927 <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>
3928 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>ServerTokens Full</code></td></tr>
3929 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
3930 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3931 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
3933 <p>This directive controls whether <code>Server</code> response
3934 header field which is sent back to clients includes a
3935 description of the generic OS-type of the server as well as
3936 information about compiled-in modules.</p>
3939 <dt><code>ServerTokens Full</code> (or not specified)</dt>
3941 <dd>Server sends (<em>e.g.</em>): <code>Server: Apache/2.4.1
3942 (Unix) PHP/4.2.2 MyMod/1.2</code></dd>
3944 <dt><code>ServerTokens Prod[uctOnly]</code></dt>
3946 <dd>Server sends (<em>e.g.</em>): <code>Server:
3949 <dt><code>ServerTokens Major</code></dt>
3951 <dd>Server sends (<em>e.g.</em>): <code>Server:
3952 Apache/2</code></dd>
3954 <dt><code>ServerTokens Minor</code></dt>
3956 <dd>Server sends (<em>e.g.</em>): <code>Server:
3957 Apache/2.4</code></dd>
3959 <dt><code>ServerTokens Min[imal]</code></dt>
3961 <dd>Server sends (<em>e.g.</em>): <code>Server:
3962 Apache/2.4.1</code></dd>
3964 <dt><code>ServerTokens OS</code></dt>
3966 <dd>Server sends (<em>e.g.</em>): <code>Server: Apache/2.4.1
3971 <p>This setting applies to the entire server, and cannot be
3972 enabled or disabled on a virtualhost-by-virtualhost basis.</p>
3974 <p>After version 2.0.44, this directive also controls the
3975 information presented by the <code class="directive"><a href="#serversignature">ServerSignature</a></code> directive.</p>
3977 <div class="note">Setting <code class="directive">ServerTokens</code> to less than
3978 <code>minimal</code> is not recommended because it makes it more
3979 difficult to debug interoperational problems. Also note that
3980 disabling the Server: header does nothing at all to make your
3981 server more secure; the idea of "security through obscurity"
3982 is a myth and leads to a false sense of safety.</div>
3985 <h3>Consulte también</h3>
3987 <li><code class="directive"><a href="#serversignature">ServerSignature</a></code></li>
3990 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
3991 <div class="directive-section"><h2><a name="SetHandler" id="SetHandler">SetHandler</a> <a name="sethandler" id="sethandler">Directiva</a></h2>
3992 <table class="directive">
3993 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Forces all matching files to be processed by a
3995 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>SetHandler <var>handler-name</var>|None</code></td></tr>
3996 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
3997 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
3998 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
3999 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4000 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>Moved into the core in Apache httpd 2.0</td></tr>
4002 <p>When placed into an <code>.htaccess</code> file or a
4003 <code class="directive"><a href="#directory"><Directory></a></code> or
4004 <code class="directive"><a href="#location"><Location></a></code>
4005 section, this directive forces all matching files to be parsed
4006 through the <a href="../handler.html">handler</a> given by
4007 <var>handler-name</var>. For example, if you had a directory you
4008 wanted to be parsed entirely as imagemap rule files, regardless
4009 of extension, you might put the following into an
4010 <code>.htaccess</code> file in that directory:</p>
4012 <div class="example"><p><code>
4013 SetHandler imap-file
4016 <p>Another example: if you wanted to have the server display a
4017 status report whenever a URL of
4018 <code>http://servername/status</code> was called, you might put
4019 the following into <code>httpd.conf</code>:</p>
4021 <div class="example"><p><code>
4022 <Location /status><br />
4023 <span class="indent">
4024 SetHandler server-status<br />
4029 <p>You can override an earlier defined <code class="directive">SetHandler</code>
4030 directive by using the value <code>None</code>.</p>
4031 <p><strong>Note:</strong> because SetHandler overrides default handlers,
4032 normal behaviour such as handling of URLs ending in a slash (/) as
4033 directories or index files is suppressed.</p>
4035 <h3>Consulte también</h3>
4037 <li><code class="directive"><a href="../mod/mod_mime.html#addhandler">AddHandler</a></code></li>
4040 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4041 <div class="directive-section"><h2><a name="SetInputFilter" id="SetInputFilter">SetInputFilter</a> <a name="setinputfilter" id="setinputfilter">Directiva</a></h2>
4042 <table class="directive">
4043 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Sets the filters that will process client requests and POST
4045 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>SetInputFilter <var>filter</var>[;<var>filter</var>...]</code></td></tr>
4046 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
4047 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
4048 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4049 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4051 <p>The <code class="directive">SetInputFilter</code> directive sets the
4052 filter or filters which will process client requests and POST
4053 input when they are received by the server. This is in addition to
4054 any filters defined elsewhere, including the
4055 <code class="directive"><a href="../mod/mod_mime.html#addinputfilter">AddInputFilter</a></code>
4058 <p>If more than one filter is specified, they must be separated
4059 by semicolons in the order in which they should process the
4062 <h3>Consulte también</h3>
4064 <li><a href="../filter.html">Filters</a> documentation</li>
4067 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4068 <div class="directive-section"><h2><a name="SetOutputFilter" id="SetOutputFilter">SetOutputFilter</a> <a name="setoutputfilter" id="setoutputfilter">Directiva</a></h2>
4069 <table class="directive">
4070 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Sets the filters that will process responses from the
4072 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>SetOutputFilter <var>filter</var>[;<var>filter</var>...]</code></td></tr>
4073 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
4074 <tr><th><a href="directive-dict.html#Override">Anula:</a></th><td>FileInfo</td></tr>
4075 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4076 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4078 <p>The <code class="directive">SetOutputFilter</code> directive sets the filters
4079 which will process responses from the server before they are
4080 sent to the client. This is in addition to any filters defined
4081 elsewhere, including the
4082 <code class="directive"><a href="../mod/mod_mime.html#addoutputfilter">AddOutputFilter</a></code>
4085 <p>For example, the following configuration will process all files
4086 in the <code>/www/data/</code> directory for server-side
4089 <div class="example"><p><code>
4090 <Directory /www/data/><br />
4091 <span class="indent">
4092 SetOutputFilter INCLUDES<br />
4097 <p>If more than one filter is specified, they must be separated
4098 by semicolons in the order in which they should process the
4101 <h3>Consulte también</h3>
4103 <li><a href="../filter.html">Filters</a> documentation</li>
4106 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4107 <div class="directive-section"><h2><a name="TimeOut" id="TimeOut">TimeOut</a> <a name="timeout" id="timeout">Directiva</a></h2>
4108 <table class="directive">
4109 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Amount of time the server will wait for
4110 certain events before failing a request</td></tr>
4111 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>TimeOut <var>seconds</var></code></td></tr>
4112 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>TimeOut 60</code></td></tr>
4113 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host</td></tr>
4114 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4115 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4117 <p>The <code class="directive">TimeOut</code> directive defines the length
4118 of time Apache httpd will wait for I/O in various circumstances:</p>
4121 <li>When reading data from the client, the length of time to
4122 wait for a TCP packet to arrive if the read buffer is
4125 <li>When writing data to the client, the length of time to wait
4126 for an acknowledgement of a packet if the send buffer is
4129 <li>In <code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code>, the length of time to wait for
4130 output from a CGI script.</li>
4132 <li>In <code class="module"><a href="../mod/mod_ext_filter.html">mod_ext_filter</a></code>, the length of time to
4133 wait for output from a filtering process.</li>
4135 <li>In <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>, the default timeout value if
4136 <code class="directive"><a href="../mod/mod_proxy.html#proxytimeout">ProxyTimeout</a></code> is not
4142 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4143 <div class="directive-section"><h2><a name="TraceEnable" id="TraceEnable">TraceEnable</a> <a name="traceenable" id="traceenable">Directiva</a></h2>
4144 <table class="directive">
4145 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Determines the behaviour on <code>TRACE</code> requests</td></tr>
4146 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>TraceEnable <var>[on|off|extended]</var></code></td></tr>
4147 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>TraceEnable on</code></td></tr>
4148 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
4149 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4150 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4151 <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>
4153 <p>This directive overrides the behavior of <code>TRACE</code> for both
4154 the core server and <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>. The default
4155 <code>TraceEnable on</code> permits <code>TRACE</code> requests per
4156 RFC 2616, which disallows any request body to accompany the request.
4157 <code>TraceEnable off</code> causes the core server and
4158 <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> to return a <code>405</code> (Method not
4159 allowed) error to the client.</p>
4161 <p>Finally, for testing and diagnostic purposes only, request
4162 bodies may be allowed using the non-compliant <code>TraceEnable
4163 extended</code> directive. The core (as an origin server) will
4164 restrict the request body to 64k (plus 8k for chunk headers if
4165 <code>Transfer-Encoding: chunked</code> is used). The core will
4166 reflect the full headers and all chunk headers with the response
4167 body. As a proxy server, the request body is not restricted to 64k.</p>
4170 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4171 <div class="directive-section"><h2><a name="UnDefine" id="UnDefine">UnDefine</a> <a name="undefine" id="undefine">Directiva</a></h2>
4172 <table class="directive">
4173 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Undefine the existence of a variable</td></tr>
4174 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>UnDefine <var>parameter-name</var></code></td></tr>
4175 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
4176 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4177 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4179 <p>Undoes the effect of a <code class="directive"><a href="#define">Define</a></code> or
4180 of passing a <code>-D</code> argument to <code class="program"><a href="../programs/httpd.html">httpd</a></code>.</p>
4181 <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
4182 <code>-D</code> arguments in any startup scripts.</p>
4185 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4186 <div class="directive-section"><h2><a name="UseCanonicalName" id="UseCanonicalName">UseCanonicalName</a> <a name="usecanonicalname" id="usecanonicalname">Directiva</a></h2>
4187 <table class="directive">
4188 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures how the server determines its own name and
4190 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>UseCanonicalName On|Off|DNS</code></td></tr>
4191 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>UseCanonicalName Off</code></td></tr>
4192 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
4193 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4194 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4196 <p>In many situations Apache httpd must construct a <em>self-referential</em>
4197 URL -- that is, a URL that refers back to the same server. With
4198 <code>UseCanonicalName On</code> Apache httpd will use the hostname and port
4199 specified in the <code class="directive"><a href="#servername">ServerName</a></code>
4200 directive to construct the canonical name for the server. This name
4201 is used in all self-referential URLs, and for the values of
4202 <code>SERVER_NAME</code> and <code>SERVER_PORT</code> in CGIs.</p>
4204 <p>With <code>UseCanonicalName Off</code> Apache httpd will form
4205 self-referential URLs using the hostname and port supplied by
4206 the client if any are supplied (otherwise it will use the
4207 canonical name, as defined above). These values are the same
4208 that are used to implement <a href="../vhosts/name-based.html">name-based virtual hosts</a>,
4209 and are available with the same clients. The CGI variables
4210 <code>SERVER_NAME</code> and <code>SERVER_PORT</code> will be
4211 constructed from the client supplied values as well.</p>
4213 <p>An example where this may be useful is on an intranet server
4214 where you have users connecting to the machine using short
4215 names such as <code>www</code>. You'll notice that if the users
4216 type a shortname, and a URL which is a directory, such as
4217 <code>http://www/splat</code>, <em>without the trailing
4218 slash</em> then Apache httpd will redirect them to
4219 <code>http://www.domain.com/splat/</code>. If you have
4220 authentication enabled, this will cause the user to have to
4221 authenticate twice (once for <code>www</code> and once again
4222 for <code>www.domain.com</code> -- see <a href="http://httpd.apache.org/docs/misc/FAQ.html#prompted-twice">the
4223 FAQ on this subject for more information</a>). But if
4224 <code class="directive">UseCanonicalName</code> is set <code>Off</code>, then
4225 Apache httpd will redirect to <code>http://www/splat/</code>.</p>
4227 <p>There is a third option, <code>UseCanonicalName DNS</code>,
4228 which is intended for use with mass IP-based virtual hosting to
4229 support ancient clients that do not provide a
4230 <code>Host:</code> header. With this option Apache httpd does a
4231 reverse DNS lookup on the server IP address that the client
4232 connected to in order to work out self-referential URLs.</p>
4234 <div class="warning"><h3>Warning</h3>
4235 <p>If CGIs make assumptions about the values of <code>SERVER_NAME</code>
4236 they may be broken by this option. The client is essentially free
4237 to give whatever value they want as a hostname. But if the CGI is
4238 only using <code>SERVER_NAME</code> to construct self-referential URLs
4239 then it should be just fine.</p>
4242 <h3>Consulte también</h3>
4244 <li><code class="directive"><a href="#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></code></li>
4245 <li><code class="directive"><a href="#servername">ServerName</a></code></li>
4246 <li><code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code></li>
4249 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4250 <div class="directive-section"><h2><a name="UseCanonicalPhysicalPort" id="UseCanonicalPhysicalPort">UseCanonicalPhysicalPort</a> <a name="usecanonicalphysicalport" id="usecanonicalphysicalport">Directiva</a></h2>
4251 <table class="directive">
4252 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Configures how the server determines its own name and
4254 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>UseCanonicalPhysicalPort On|Off</code></td></tr>
4255 <tr><th><a href="directive-dict.html#Default">Valor por defecto:</a></th><td><code>UseCanonicalPhysicalPort Off</code></td></tr>
4256 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory</td></tr>
4257 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4258 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4260 <p>In many situations Apache httpd must construct a <em>self-referential</em>
4261 URL -- that is, a URL that refers back to the same server. With
4262 <code>UseCanonicalPhysicalPort On</code> Apache httpd will, when
4263 constructing the canonical port for the server to honor
4264 the <code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code> directive,
4265 provide the actual physical port number being used by this request
4266 as a potential port. With <code>UseCanonicalPhysicalPort Off</code>
4267 Apache httpd will not ever use the actual physical port number, instead
4268 relying on all configured information to construct a valid port number.</p>
4270 <div class="note"><h3>Note</h3>
4271 <p>The ordering of when the physical port is used is as follows:<br /><br />
4272 <code>UseCanonicalName On</code></p>
4274 <li>Port provided in <code>Servername</code></li>
4275 <li>Physical port</li>
4276 <li>Default port</li>
4278 <code>UseCanonicalName Off | DNS</code>
4280 <li>Parsed port from <code>Host:</code> header</li>
4281 <li>Physical port</li>
4282 <li>Port provided in <code>Servername</code></li>
4283 <li>Default port</li>
4286 <p>With <code>UseCanonicalPhysicalPort Off</code>, the
4287 physical ports are removed from the ordering.</p>
4291 <h3>Consulte también</h3>
4293 <li><code class="directive"><a href="#usecanonicalname">UseCanonicalName</a></code></li>
4294 <li><code class="directive"><a href="#servername">ServerName</a></code></li>
4295 <li><code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code></li>
4298 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4299 <div class="directive-section"><h2><a name="VirtualHost" id="VirtualHost"><VirtualHost></a> <a name="virtualhost" id="virtualhost">Directiva</a></h2>
4300 <table class="directive">
4301 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Contains directives that apply only to a specific
4302 hostname or IP address</td></tr>
4303 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code><VirtualHost
4304 <var>addr</var>[:<var>port</var>] [<var>addr</var>[:<var>port</var>]]
4305 ...> ... </VirtualHost></code></td></tr>
4306 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config</td></tr>
4307 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4308 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4310 <p><code class="directive"><VirtualHost></code> and
4311 <code></VirtualHost></code> are used to enclose a group of
4312 directives that will apply only to a particular virtual host. Any
4313 directive that is allowed in a virtual host context may be
4314 used. When the server receives a request for a document on a
4315 particular virtual host, it uses the configuration directives
4316 enclosed in the <code class="directive"><VirtualHost></code>
4317 section. <var>Addr</var> can be:</p>
4320 <li>The IP address of the virtual host;</li>
4322 <li>A fully qualified domain name for the IP address of the
4323 virtual host (not recommended);</li>
4325 <li>The character <code>*</code>, which is used only in combination with
4326 <code>NameVirtualHost *</code> to match all IP addresses; or</li>
4328 <li>The string <code>_default_</code>, which is used only
4329 with IP virtual hosting to catch unmatched IP addresses.</li>
4332 <div class="example"><h3>Example</h3><p><code>
4333 <VirtualHost 10.1.2.3><br />
4334 <span class="indent">
4335 ServerAdmin webmaster@host.example.com<br />
4336 DocumentRoot /www/docs/host.example.com<br />
4337 ServerName host.example.com<br />
4338 ErrorLog logs/host.example.com-error_log<br />
4339 TransferLog logs/host.example.com-access_log<br />
4341 </VirtualHost>
4345 <p>IPv6 addresses must be specified in square brackets because
4346 the optional port number could not be determined otherwise. An
4347 IPv6 example is shown below:</p>
4349 <div class="example"><p><code>
4350 <VirtualHost [2001:db8::a00:20ff:fea7:ccea]><br />
4351 <span class="indent">
4352 ServerAdmin webmaster@host.example.com<br />
4353 DocumentRoot /www/docs/host.example.com<br />
4354 ServerName host.example.com<br />
4355 ErrorLog logs/host.example.com-error_log<br />
4356 TransferLog logs/host.example.com-access_log<br />
4358 </VirtualHost>
4361 <p>Each Virtual Host must correspond to a different IP address,
4362 different port number or a different host name for the server,
4363 in the former case the server machine must be configured to
4364 accept IP packets for multiple addresses. (If the machine does
4365 not have multiple network interfaces, then this can be
4366 accomplished with the <code>ifconfig alias</code> command -- if
4367 your OS supports it).</p>
4369 <div class="note"><h3>Note</h3>
4370 <p>The use of <code class="directive"><VirtualHost></code> does
4371 <strong>not</strong> affect what addresses Apache httpd listens on. You
4372 may need to ensure that Apache httpd is listening on the correct addresses
4373 using <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>.</p>
4376 <p>When using IP-based virtual hosting, the special name
4377 <code>_default_</code> can be specified in
4378 which case this virtual host will match any IP address that is
4379 not explicitly listed in another virtual host. In the absence
4380 of any <code>_default_</code> virtual host the "main" server config,
4381 consisting of all those definitions outside any VirtualHost
4382 section, is used when no IP-match occurs.</p>
4384 <p>You can specify a <code>:port</code> to change the port that is
4385 matched. If unspecified then it defaults to the same port as the
4386 most recent <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>
4387 statement of the main server. You may also specify <code>:*</code>
4388 to match all ports on that address. (This is recommended when used
4389 with <code>_default_</code>.)</p>
4391 <p>A <code class="directive"><a href="#servername">ServerName</a></code> should be
4392 specified inside each <code class="directive"><VirtualHost></code> block. If it is absent, the
4393 <code class="directive"><a href="#servername">ServerName</a></code> from the "main"
4394 server configuration will be inherited.</p>
4396 <p>If no matching virtual host is found, then the first listed
4397 virtual host that matches the IP address will be used. As a
4398 consequence, the first listed virtual host is the default virtual
4401 <div class="warning"><h3>Security</h3>
4402 <p>See the <a href="../misc/security_tips.html">security tips</a>
4403 document for details on why your security could be compromised if the
4404 directory where log files are stored is writable by anyone other
4405 than the user that starts the server.</p>
4408 <h3>Consulte también</h3>
4410 <li><a href="../vhosts/">Apache HTTP Server Virtual Host documentation</a></li>
4411 <li><a href="../dns-caveats.html">Issues Regarding DNS and
4412 Apache HTTP Server</a></li>
4413 <li><a href="../bind.html">Setting
4414 which addresses and ports Apache HTTP Server uses</a></li>
4415 <li><a href="../sections.html">How <Directory>, <Location>
4416 and <Files> sections work</a> for an explanation of how these
4417 different sections are combined when a request is received</li>
4420 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
4421 <div class="directive-section"><h2><a name="Warning" id="Warning">Warning</a> <a name="warning" id="warning">Directiva</a></h2>
4422 <table class="directive">
4423 <tr><th><a href="directive-dict.html#Description">Descripción:</a></th><td>Warn from configuration parsing with a custom message</td></tr>
4424 <tr><th><a href="directive-dict.html#Syntax">Sintaxis:</a></th><td><code>Warning <var>message</var></code></td></tr>
4425 <tr><th><a href="directive-dict.html#Context">Contexto:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
4426 <tr><th><a href="directive-dict.html#Status">Estado:</a></th><td>Core</td></tr>
4427 <tr><th><a href="directive-dict.html#Module">Módulo:</a></th><td>core</td></tr>
4428 <tr><th><a href="directive-dict.html#Compatibility">Compatibilidad:</a></th><td>2.5 and later</td></tr>
4429 </table><p>The documentation for this directive has
4430 not been translated yet. Please have a look at the English
4433 <div class="bottomlang">
4434 <p><span>Idiomas disponibles: </span><a href="../de/mod/core.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> |
4435 <a href="../en/mod/core.html" hreflang="en" rel="alternate" title="English"> en </a> |
4436 <a href="../es/mod/core.html" title="Español"> es </a> |
4437 <a href="../fr/mod/core.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
4438 <a href="../ja/mod/core.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
4439 <a href="../tr/mod/core.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p>
4440 </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>
4441 <script type="text/javascript"><!--//--><![CDATA[//><!--
4442 var comments_shortname = 'httpd';
4443 var comments_identifier = 'http://httpd.apache.org/docs/trunk/mod/core.html';
4445 if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
4446 d.write('<div id="comments_thread"><\/div>');
4447 var s = d.createElement('script');
4448 s.type = 'text/javascript';
4450 s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
4451 (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
4454 d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
4456 })(window, document);
4457 //--><!]]></script></div><div id="footer">
4458 <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>
4459 <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