<p>IPv6 addresses must be enclosed in square brackets, as in the
following example:</p>
- <pre class="prettyprint lang-config"> Listen [2001:db8::a00:20ff:fea7:ccea]:80</pre>
+ <pre class="prettyprint lang-config">Listen [2001:db8::a00:20ff:fea7:ccea]:80</pre>
<div class="warning"><p>Overlapping <code class="directive"><a href="./mod/mpm_common.html#listen">Listen</a></code> directives will result in a
<p>You only need to set the protocol if you are running on non-standard
ports. For example, running an <code>https</code> site on port 8443:</p>
- <pre class="prettyprint lang-config"> Listen 192.170.2.1:8443 https</pre>
+ <pre class="prettyprint lang-config">Listen 192.170.2.1:8443 https</pre>
</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
<div class="section">
<p>Les adresses IPv6 doivent être mises entre crochets, comme dans
l'exemple suivant :</p>
- <pre class="prettyprint lang-config"> Listen [2001:db8::a00:20ff:fea7:ccea]:80</pre>
+ <pre class="prettyprint lang-config">Listen [2001:db8::a00:20ff:fea7:ccea]:80</pre>
<div class="warning"><p>Des directives <code class="directive"><a href="./mod/mpm_common.html#listen">Listen</a></code>
des ports non standards. Par exemple, pour travailler en
<code>https</code> sur le port 8443 :</p>
- <pre class="prettyprint lang-config"> Listen 192.170.2.1:8443 https</pre>
+ <pre class="prettyprint lang-config">Listen 192.170.2.1:8443 https</pre>
</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
<div class="section">
instructs httpd to open the file when it is started and to re-use
this file-handle for all subsequent access to this file.</p>
- <pre class="prettyprint lang-config"> CacheFile /usr/local/apache2/htdocs/index.html</pre>
+ <pre class="prettyprint lang-config">CacheFile /usr/local/apache2/htdocs/index.html</pre>
<p>If you intend to cache a large number of files in this manner, you
start time (using the mmap system call). httpd will use the in-memory
contents for all subsequent accesses to this file.</p>
- <pre class="prettyprint lang-config"> MMapFile /usr/local/apache2/htdocs/index.html</pre>
+ <pre class="prettyprint lang-config">MMapFile /usr/local/apache2/htdocs/index.html</pre>
<p>As with the
réutiliser le descripteur de fichier mis en cache pour tous les
accès futurs à ce fichier.</p>
- <pre class="prettyprint lang-config"> CacheFile /usr/local/apache2/htdocs/index.html</pre>
+ <pre class="prettyprint lang-config">CacheFile /usr/local/apache2/htdocs/index.html</pre>
<p>Si vous désirez mettre en cache un grand nombre de fichiers
utilisera le contenu chargé en mémoire pour satisfaire ultérieurement
toutes les demandes d'accès à ce fichier.</p>
- <pre class="prettyprint lang-config"> MMapFile /usr/local/apache2/htdocs/index.html</pre>
+ <pre class="prettyprint lang-config">MMapFile /usr/local/apache2/htdocs/index.html</pre>
<p>Comme dans le cas de la directive
<p>The syntax of the <code>ErrorDocument</code> directive is:</p>
- <pre class="prettyprint lang-config"> ErrorDocument <3-digit-code> <action></pre>
+ <pre class="prettyprint lang-config">ErrorDocument <3-digit-code> <action></pre>
<p>where the action will be treated as:</p>
<p>In your server configuration file, you'll see a line such as:</p>
- <pre class="prettyprint lang-config"> # Multi-language error messages<br />
+ <pre class="prettyprint lang-config"># Multi-language error messages<br />
#Include conf/extra/httpd-multilang-errordoc.conf</pre>
<p>La syntaxe de la directive <code>ErrorDocument</code> est :</p>
- <pre class="prettyprint lang-config"> ErrorDocument <code_3_chiffres> <action></pre>
+ <pre class="prettyprint lang-config">ErrorDocument <code_3_chiffres> <action></pre>
<p>où action peut être traitée comme :</p>
<ol>
<p>Dans le fichier de configuration de votre serveur, vous trouverez
un groupe de lignes du style :</p>
- <pre class="prettyprint lang-config"> # Multi-language error messages<br />
+ <pre class="prettyprint lang-config"># Multi-language error messages<br />
#Include conf/extra/httpd-multilang-errordoc.conf</pre>
arguments. For example, if the hook returns an <code>int</code> and
takes a <code>request_rec *</code> and an <code>int</code> and is
called <code>do_something</code>, then declare it like this:</p>
- <pre class="prettyprint lang-c"> AP_DECLARE_HOOK(int, do_something, (request_rec *r, int n))</pre>
+ <pre class="prettyprint lang-c">AP_DECLARE_HOOK(int, do_something, (request_rec *r, int n))</pre>
<p>This should go in a header which modules will include if
<p>If the return value of a hook is <code>void</code>, then all the
hooks are called, and the caller is implemented like this:</p>
- <pre class="prettyprint lang-c"> AP_IMPLEMENT_HOOK_VOID(do_something, (request_rec *r, int n), (r, n))</pre>
+ <pre class="prettyprint lang-c">AP_IMPLEMENT_HOOK_VOID(do_something, (request_rec *r, int n), (r, n))</pre>
<p>The second and third arguments are the dummy argument
<p>If the hook returns a value, then it can either be run until
the first hook that does something interesting, like so:</p>
- <pre class="prettyprint lang-c"> AP_IMPLEMENT_HOOK_RUN_FIRST(int, do_something, (request_rec *r, int n), (r, n), DECLINED)</pre>
+ <pre class="prettyprint lang-c">AP_IMPLEMENT_HOOK_RUN_FIRST(int, do_something, (request_rec *r, int n), (r, n), DECLINED)</pre>
<p>The first hook that does <em>not</em> return <code>DECLINED</code>
value other than one of those two stops the loop, and its
return is the return value. Declare these like so:</p>
- <pre class="prettyprint lang-c"> AP_IMPLEMENT_HOOK_RUN_ALL(int, do_something, (request_rec *r, int n), (r, n), OK, DECLINED)</pre>
+ <pre class="prettyprint lang-c">AP_IMPLEMENT_HOOK_RUN_ALL(int, do_something, (request_rec *r, int n), (r, n), OK, DECLINED)</pre>
<p>Again, <code>OK</code> and <code>DECLINED</code> are the traditional
brigade should have no side effects (such as changing any state
private to the filter).</p>
- <div class="example"><h3>How to handle an empty brigade</h3><pre class="prettyprint lang-c"> apr_status_t dummy_filter(ap_filter_t *f, apr_bucket_brigade *bb)<br />
+ <div class="example"><h3>How to handle an empty brigade</h3><pre class="prettyprint lang-c">apr_status_t dummy_filter(ap_filter_t *f, apr_bucket_brigade *bb)<br />
{
if (APR_BRIGADE_EMPTY(bb)) {
return APR_SUCCESS;
you may wish to make use of. Specifically, a new record has
been added to the <code>request_rec</code> structure:</p>
- <pre class="prettyprint lang-c"> char *handler</pre>
+ <pre class="prettyprint lang-c">char *handler</pre>
<p>If you wish to have your module engage a handler, you need
Plus précisément, un nouvel enregistrement a été ajouté à la structure
<code>request_rec</code> :</p>
- <pre class="prettyprint lang-c"> char *handler</pre>
+ <pre class="prettyprint lang-c">char *handler</pre>
<p>Si vous voulez que votre module déclenche l'utilisation d'un
directive has not been commented out. A correctly configured directive
may look like this:
- <pre class="prettyprint lang-config"> LoadModule cgi_module modules/mod_cgi.so</pre>
+ <pre class="prettyprint lang-config">LoadModule cgi_module modules/mod_cgi.so</pre>
</div>
<h3><a name="scriptalias" id="scriptalias">ScriptAlias</a></h3>
<p>The <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code>
directive looks like:</p>
- <pre class="prettyprint lang-config"> ScriptAlias /cgi-bin/ /usr/local/apache2/cgi-bin/</pre>
+ <pre class="prettyprint lang-config">ScriptAlias /cgi-bin/ /usr/local/apache2/cgi-bin/</pre>
<p>The example shown is from your default <code>httpd.conf</code>
files with the <code>cgi</code> or <code>pl</code> extension as CGI
programs:</p>
- <pre class="prettyprint lang-config"> AddHandler cgi-script .cgi .pl</pre>
+ <pre class="prettyprint lang-config">AddHandler cgi-script .cgi .pl</pre>
interpreter (often <code>perl</code>) indicated in the first
line of your CGI program, which will look something like:</p>
- <pre class="prettyprint lang-perl"> #!/usr/bin/perl</pre>
+ <pre class="prettyprint lang-perl">#!/usr/bin/perl</pre>
<p>Make sure that this is in fact the path to the
commentée dans votre <code>httpd.conf</code>. Une directive correcte
doit ressembler à ceci :
- <pre class="prettyprint lang-config"> LoadModule cgi_module modules/mod_cgi.so</pre>
+ <pre class="prettyprint lang-config">LoadModule cgi_module modules/mod_cgi.so</pre>
</div>
<h3><a name="scriptalias" id="scriptalias">ScriptAlias</a></h3>
<p>La directive <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code> se présente comme suit
:</p>
- <pre class="prettyprint lang-config"> ScriptAlias /cgi-bin/ /usr/local/apache2/cgi-bin/</pre>
+ <pre class="prettyprint lang-config">ScriptAlias /cgi-bin/ /usr/local/apache2/cgi-bin/</pre>
<p>Cet exemple est tiré de votre fichier de configuration
extension <code>cgi</code> ou <code>pl</code> en tant que
programmes CGI :</p>
- <pre class="prettyprint lang-config"> AddHandler cgi-script .cgi .pl</pre>
+ <pre class="prettyprint lang-config">AddHandler cgi-script .cgi .pl</pre>
trouve à la première ligne de votre programme CGI et qui va
ressembler à ceci :</p>
- <pre class="prettyprint lang-perl"> #!/usr/bin/perl</pre>
+ <pre class="prettyprint lang-perl">#!/usr/bin/perl</pre>
<p>Assurez-vous qu'il s'agit bien du chemin correct vers
<code>.config</code>, vous pouvez mettre ceci dans le fichier de
configuration de votre serveur :</p>
- <pre class="prettyprint lang-config"> AccessFileName .config</pre>
+ <pre class="prettyprint lang-config">AccessFileName .config</pre>
</div>
You can, likewise, disable the feature for all but a few users by
using a configuration like the following:</p>
- <pre class="prettyprint lang-config"> UserDir disabled<br />
+ <pre class="prettyprint lang-config">UserDir disabled<br />
UserDir enabled rbowen krietz</pre>
utilisateurs sauf certains d'entre eux en utilisant une
configuration du style :</p>
- <pre class="prettyprint lang-config"> UserDir disabled<br />
+ <pre class="prettyprint lang-config">UserDir disabled<br />
UserDir enabled rbowen krietz</pre>
<p>To permit SSI on your server, you must have the following
directive either in your <code>httpd.conf</code> file, or in a
<code>.htaccess</code> file:</p>
-<pre class="prettyprint lang-config"> Options +Includes</pre>
+<pre class="prettyprint lang-config">Options +Includes</pre>
<p>This tells Apache that you want to permit files to be parsed
do this. You can tell Apache to parse any file with a
particular file extension, such as <code>.shtml</code>, with
the following directives:</p>
-<pre class="prettyprint lang-config"> AddType text/html .shtml<br />
+<pre class="prettyprint lang-config">AddType text/html .shtml<br />
AddOutputFilter INCLUDES .shtml</pre>
directives would be executed.</p>
<p>The other method is to use the <code class="directive"><a href="../mod/mod_include.html#xbithack">XBitHack</a></code> directive:</p>
-<pre class="prettyprint lang-config"> XBitHack on</pre>
+<pre class="prettyprint lang-config">XBitHack on</pre>
<p><code class="directive"><a href="../mod/mod_include.html#xbithack">XBitHack</a></code>
<p>In your configuration file, you could put the following
line:</p>
-<pre class="prettyprint lang-config"> BrowserMatchNoCase macintosh Mac<br />
+<pre class="prettyprint lang-config">BrowserMatchNoCase macintosh Mac<br />
BrowserMatchNoCase MSIE InternetExplorer</pre>
devez ajouter la directive suivante dans votre fichier
<code>httpd.conf</code>, ou dans un fichier <code>.htaccess</code>
:</p>
-<pre class="prettyprint lang-config"> Options +Includes</pre>
+<pre class="prettyprint lang-config">Options +Includes</pre>
<p>Cette directive indique à Apache que vous désirez permettre la
directives SSI. Vous devez indiquer à Apache quels fichiers seront
concernés. Vous pouvez y parvenir en indiquant une extension, comme
<code>.shtml</code>, à l'aide des directives suivantes :</p>
-<pre class="prettyprint lang-config"> AddType text/html .shtml<br />
+<pre class="prettyprint lang-config">AddType text/html .shtml<br />
AddOutputFilter INCLUDES .shtml</pre>
SSI qu'elle contient soient traitées.</p>
<p>Une autre méthode consiste à utiliser la directive <code class="directive"><a href="../mod/mod_include.html#xbithack">XBitHack</a></code> :</p>
-<pre class="prettyprint lang-config"> XBitHack on</pre>
+<pre class="prettyprint lang-config">XBitHack on</pre>
<p>La directive <code class="directive"><a href="../mod/mod_include.html#xbithack">XBitHack</a></code>
<p>Vous pouvez ajouter les lignes suivantes dans votre fichier de
configuration :</p>
-<pre class="prettyprint lang-config"> BrowserMatchNoCase macintosh Mac<br />
+<pre class="prettyprint lang-config">BrowserMatchNoCase macintosh Mac<br />
BrowserMatchNoCase MSIE InternetExplorer</pre>
<p>Do this by specifying the name of the module in your
<code class="directive">LogLevel</code> directive:</p>
- <pre class="prettyprint lang-config"> LogLevel info rewrite:trace5</pre>
+ <pre class="prettyprint lang-config">LogLevel info rewrite:trace5</pre>
<p>This sets the main <code class="directive">LogLevel</code> to info, but
for this purpose. For example, to rotate the logs every 24 hours, you
can use:</p>
- <pre class="prettyprint lang-config"> CustomLog "|/usr/local/apache/bin/rotatelogs /var/log/access_log 86400" common</pre>
+ <pre class="prettyprint lang-config">CustomLog "|/usr/local/apache/bin/rotatelogs /var/log/access_log 86400" common</pre>
<p>Notice that quotes are used to enclose the entire command
<p>Pour ce faire, vous devez spécifier le nom du module dans votre
directive <code class="directive">LogLevel</code> :</p>
- <pre class="prettyprint lang-config"> LogLevel info rewrite:trace5</pre>
+ <pre class="prettyprint lang-config">LogLevel info rewrite:trace5</pre>
<p>Dans cet exemple, le niveau de journalisation général est défini
appelé <code class="program"><a href="./programs/rotatelogs.html">rotatelogs</a></code>. Par exemple, pour une rotation des
journaux toutes les 24 heures, ajoutez ces lignes :</p>
- <pre class="prettyprint lang-config"> CustomLog "|/usr/local/apache/bin/rotatelogs /var/log/access_log 86400" common</pre>
+ <pre class="prettyprint lang-config">CustomLog "|/usr/local/apache/bin/rotatelogs /var/log/access_log 86400" common</pre>
<p>Notez que l'ensemble de la commande qui sera appelée par le tube de
can be specified on a per module basis:
</p>
- <pre class="prettyprint lang-config"> LogLevel debug mod_ssl:warn</pre>
+ <pre class="prettyprint lang-config">LogLevel debug mod_ssl:warn</pre>
<p>
<p>Using <code>none</code> for an argument will disable any accept filters
for that protocol. This is useful for protocols that require a server
send data first, such as <code>ftp:</code> or <code>nntp</code>:</p>
- <pre class="prettyprint lang-config"> AcceptFilter nntp none</pre>
+ <pre class="prettyprint lang-config">AcceptFilter nntp none</pre>
<p>The default protocol names are <code>https</code> for port 443
filtre d'acceptation pour ce protocole. Ceci s'avère utile pour les
protocoles qui nécessitent l'envoi de données par le serveur en
premier, comme <code>ftp:</code> ou <code>nntp</code>:</p>
- <pre class="prettyprint lang-config"> AcceptFilter nntp none</pre>
+ <pre class="prettyprint lang-config">AcceptFilter nntp none</pre>
<p>Les noms de protocoles par défaut sont <code>https</code> pour le
<dt>A network/netmask pair</dt>
<dd>
- <pre class="prettyprint lang-config"> Allow from 10.1.0.0/255.255.0.0</pre>
+ <pre class="prettyprint lang-config">Allow from 10.1.0.0/255.255.0.0</pre>
<p>A network a.b.c.d, and a netmask w.x.y.z. For more
fine-grained subnet restriction.</p></dd>
<dt>A network/nnn CIDR specification</dt>
<dd>
- <pre class="prettyprint lang-config"> Allow from 10.1.0.0/16</pre>
+ <pre class="prettyprint lang-config">Allow from 10.1.0.0/16</pre>
<p>Similar to the previous case, except the netmask consists of
nnn high-order 1 bits.</p></dd>
<dt>Une paire réseau/masque de sous-réseau</dt>
<dd>
- <pre class="prettyprint lang-config"> Allow from 10.1.0.0/255.255.0.0</pre>
+ <pre class="prettyprint lang-config">Allow from 10.1.0.0/255.255.0.0</pre>
<p>Un réseau a.b.c.d, et un masque de sous-réseau w.x.y.z, pour
une définition plus précise de la restriction d'accès imposée à un
<dt>Une spécification CIDR réseau/nnn</dt>
<dd>
- <pre class="prettyprint lang-config"> Allow from 10.1.0.0/16</pre>
+ <pre class="prettyprint lang-config">Allow from 10.1.0.0/16</pre>
<p>Identique au cas précédent, mis à part que le masque est
constitué des nnn bits de poids fort.</p></dd>
<var>URL-path</var> is case-sensitive, even on case-insensitive
file systems.</p>
- <pre class="prettyprint lang-config"> Alias /image /ftp/pub/image</pre>
+ <pre class="prettyprint lang-config">Alias /image /ftp/pub/image</pre>
<p>A request for <code>http://example.com/image/foo.gif</code> would cause
<var>URL-path</var> then the server will require a trailing / in
order to expand the alias. That is, if you use</p>
- <pre class="prettyprint lang-config"> Alias /icons/ /usr/local/apache/icons/</pre>
+ <pre class="prettyprint lang-config">Alias /icons/ /usr/local/apache/icons/</pre>
<p>then the url <code>/icons</code> will not be aliased, as it lacks
example, to activate the <code>/icons</code> directory, one might
use:</p>
- <pre class="prettyprint lang-config"> AliasMatch ^/icons(.*) /usr/local/apache/icons$1</pre>
+ <pre class="prettyprint lang-config">AliasMatch ^/icons(.*) /usr/local/apache/icons$1</pre>
<p>The full range of <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular expression</a>
it is possible to construct an alias with case-insensitive
matching of the URL-path:</p>
- <pre class="prettyprint lang-config"> AliasMatch (?i)^/image(.*) /ftp/pub/image$1</pre>
+ <pre class="prettyprint lang-config">AliasMatch (?i)^/image(.*) /ftp/pub/image$1</pre>
<p>One subtle difference
<p>For example, suppose you want to replace this with AliasMatch:</p>
- <pre class="prettyprint lang-config"> Alias /image/ /ftp/pub/image/</pre>
+ <pre class="prettyprint lang-config">Alias /image/ /ftp/pub/image/</pre>
<p>This is NOT equivalent - don't do this! This will send all
requests that have /image/ anywhere in them to /ftp/pub/image/:</p>
- <pre class="prettyprint lang-config"> AliasMatch /image/ /ftp/pub/image/</pre>
+ <pre class="prettyprint lang-config">AliasMatch /image/ /ftp/pub/image/</pre>
<p>This is what you need to get the same effect:</p>
- <pre class="prettyprint lang-config"> AliasMatch ^/image/(.*)$ /ftp/pub/image/$1</pre>
+ <pre class="prettyprint lang-config">AliasMatch ^/image/(.*)$ /ftp/pub/image/$1</pre>
<p>Of course, there's no point in
you do more complicated things. For example, you could
serve different kinds of files from different directories:</p>
- <pre class="prettyprint lang-config"> AliasMatch ^/image/(.*)\.jpg$ /files/jpg.images/$1.jpg<br />
+ <pre class="prettyprint lang-config">AliasMatch ^/image/(.*)\.jpg$ /files/jpg.images/$1.jpg<br />
AliasMatch ^/image/(.*)\.gif$ /files/gif.images/$1.gif</pre>
example, to redirect all GIF files to like-named JPEG files on
another server, one might use:</p>
- <pre class="prettyprint lang-config"> RedirectMatch (.*)\.gif$ http://other.example.com$1.jpg</pre>
+ <pre class="prettyprint lang-config">RedirectMatch (.*)\.gif$ http://other.example.com$1.jpg</pre>
<p>The considerations related to the difference between
to scripts beginning with the second argument, which is a full
pathname in the local filesystem.</p>
- <pre class="prettyprint lang-config"> ScriptAlias /cgi-bin/ /web/cgi-bin/</pre>
+ <pre class="prettyprint lang-config">ScriptAlias /cgi-bin/ /web/cgi-bin/</pre>
<p>A request for <code>http://example.com/cgi-bin/foo</code> would cause the
<p><code class="directive">ScriptAlias</code> can also be used in conjunction with
a script or handler you have. For example:</p>
- <pre class="prettyprint lang-config"> ScriptAlias /cgi-bin/ /web/cgi-handler.pl</pre>
+ <pre class="prettyprint lang-config">ScriptAlias /cgi-bin/ /web/cgi-handler.pl</pre>
<p>In this scenario all files requested in <code>/cgi-bin/</code> will be
example, to activate the standard <code>/cgi-bin</code>, one
might use:</p>
- <pre class="prettyprint lang-config"> ScriptAliasMatch ^/cgi-bin(.*) /usr/local/apache/cgi-bin$1</pre>
+ <pre class="prettyprint lang-config">ScriptAliasMatch ^/cgi-bin(.*) /usr/local/apache/cgi-bin$1</pre>
<p>As for AliasMatch, the full range of <a class="glossarylink" href="../glossary.html#rexex" title="see glossary">regular
For example, it is possible to construct an alias with case-insensitive
matching of the URL-path:</p>
- <pre class="prettyprint lang-config"> ScriptAliasMatch (?i)^/cgi-bin(.*) /usr/local/apache/cgi-bin$1</pre>
+ <pre class="prettyprint lang-config">ScriptAliasMatch (?i)^/cgi-bin(.*) /usr/local/apache/cgi-bin$1</pre>
<p>The considerations related to the difference between
est sensible à la casse, même sur les systèmes de fichiers
insensibles à la casse.</p>
- <pre class="prettyprint lang-config"> Alias /image /ftp/pub/image</pre>
+ <pre class="prettyprint lang-config">Alias /image /ftp/pub/image</pre>
<p>Une requête pour <code>http://example.com/image/foo.gif</code> fera
URL</var>, vous devrez aussi ajouter un slash de fin au chemin de la
requête. Autrement dit, si vous définissez</p>
- <pre class="prettyprint lang-config"> Alias /icons/ /usr/local/apache/icons/</pre>
+ <pre class="prettyprint lang-config">Alias /icons/ /usr/local/apache/icons/</pre>
<p>l'alias précédent ne s'appliquera pas à l'url
Par exemple, pour activer le répertoire <code>/icons</code>, on peut
utiliser :</p>
- <pre class="prettyprint lang-config"> AliasMatch ^/icons(.*) /usr/local/apache/icons$1</pre>
+ <pre class="prettyprint lang-config">AliasMatch ^/icons(.*) /usr/local/apache/icons$1</pre>
<p>Toute la puissance des <a class="glossarylink" href="../glossary.html#regex" title="voir glossaire">expressions
il est possible de construire un alias avec un modèle de chemin URL
insensible à la casse :</p>
- <pre class="prettyprint lang-config"> AliasMatch (?i)^/image(.*) /ftp/pub/image$1</pre>
+ <pre class="prettyprint lang-config">AliasMatch (?i)^/image(.*) /ftp/pub/image$1</pre>
<p>Il existe une différence subtile entre <code class="directive"><a href="#alias">Alias</a></code> et <code class="directive"><a href="#aliasmatch">AliasMatch</a></code> : <code class="directive"><a href="#alias">Alias</a></code> copie automatiquement toute
<p>Par exemple, supposons que nous voulions reformuler cet alias
avec AliasMatch :</p>
- <pre class="prettyprint lang-config"> Alias /image/ /ftp/pub/image/</pre>
+ <pre class="prettyprint lang-config">Alias /image/ /ftp/pub/image/</pre>
<p>Le simple remplacement d'Alias par AliasMatch ne produira pas le
même résultat. Ainsi, ce qui suit va rediriger toutes les requêtes
qui contiennent /image/ vers /ftp/pub/image/ :</p>
- <pre class="prettyprint lang-config"> AliasMatch /image/ /ftp/pub/image/</pre>
+ <pre class="prettyprint lang-config">AliasMatch /image/ /ftp/pub/image/</pre>
<p>Voici la directive AliasMatch qui produira le même résultat que
la directive Alias ci-dessus :</p>
- <pre class="prettyprint lang-config"> AliasMatch ^/image/(.*)$ /ftp/pub/image/$1</pre>
+ <pre class="prettyprint lang-config">AliasMatch ^/image/(.*)$ /ftp/pub/image/$1</pre>
<p>Bien entendu, il n'y a aucune raison d'utiliser <code class="directive"><a href="#aliasmatch">AliasMatch</a></code> dans le cas où <code class="directive"><a href="#alias">Alias</a></code> suffit. <code class="directive"><a href="#aliasmatch">AliasMatch</a></code> vous permet d'effectuer
servir différentes sortes de fichiers à partir de répertoires
différents :</p>
- <pre class="prettyprint lang-config"> AliasMatch ^/image/(.*)\.jpg$ /fichiers/jpg.images/$1.jpg<br />
+ <pre class="prettyprint lang-config">AliasMatch ^/image/(.*)\.jpg$ /fichiers/jpg.images/$1.jpg<br />
AliasMatch ^/image/(.*)\.gif$ /fichiers/gif.images/$1.gif</pre>
les fichiers GIF vers les fichiers JPEG de même nom sur un autre
serveur, on peut utiliser :</p>
- <pre class="prettyprint lang-config"> RedirectMatch (.*)\.gif$ http://autre.example.com$1.jpg</pre>
+ <pre class="prettyprint lang-config">RedirectMatch (.*)\.gif$ http://autre.example.com$1.jpg</pre>
<p>Les remarques à propos de la différence entre <code class="directive"><a href="#alias">Alias</a></code> et <code class="directive"><a href="#aliasmatch">AliasMatch</a></code> s'appliquent aussi à la
second argument, qui est un chemin complet dans le système de
fichiers local.</p>
- <pre class="prettyprint lang-config"> ScriptAlias /cgi-bin/ /web/cgi-bin/</pre>
+ <pre class="prettyprint lang-config">ScriptAlias /cgi-bin/ /web/cgi-bin/</pre>
<p>Une requête pour <code>http://example.com/cgi-bin/foo</code>
<p>Vous pouvez aussi utiliser <code class="directive">ScriptAlias</code>
avec un script ou gestionnaire de votre cru. Par exemple :</p>
- <pre class="prettyprint lang-config"> ScriptAlias /cgi-bin/ /web/cgi-handler.pl</pre>
+ <pre class="prettyprint lang-config">ScriptAlias /cgi-bin/ /web/cgi-handler.pl</pre>
<p>Dans ce scénario, tous les fichiers faisant l'objet d'une requête
comme nom de fichier. Par exemple, pour activer le répertoire
standard <code>/cgi-bin</code>, on peut utiliser :</p>
- <pre class="prettyprint lang-config"> ScriptAliasMatch ^/cgi-bin(.*) /usr/local/apache/cgi-bin$1</pre>
+ <pre class="prettyprint lang-config">ScriptAliasMatch ^/cgi-bin(.*) /usr/local/apache/cgi-bin$1</pre>
<p>Comme dans le cas d'AliasMatch, toute la puissance des <a class="glossarylink" href="../glossary.html#rexex" title="voir glossaire">expressions rationnelles</a> peut être mise à
contribution. Par exemple, il est possible de construire un alias
avec une comparaison du modèle du chemin URL insensible à la casse :</p>
- <pre class="prettyprint lang-config"> ScriptAliasMatch (?i)^/cgi-bin(.*) /usr/local/apache/cgi-bin$1</pre>
+ <pre class="prettyprint lang-config">ScriptAliasMatch (?i)^/cgi-bin(.*) /usr/local/apache/cgi-bin$1</pre>
<p>Les remarques à propos de la différence entre <code class="directive"><a href="#alias">Alias</a></code> et <code class="directive"><a href="#aliasmatch">AliasMatch</a></code> s'appliquent aussi à la
'<code>anonymous</code>' is always one of the allowed
userIDs.</p>
- <div class="example"><h3>Example:</h3><pre class="prettyprint lang-config"> Anonymous anonymous "Not Registered" "I don't know"</pre>
+ <div class="example"><h3>Example:</h3><pre class="prettyprint lang-config">Anonymous anonymous "Not Registered" "I don't know"</pre>
</div>
<p>This would allow the user to enter without password
Il est fortement conseillé d'intégrer l'utilisateur spécial
'<code>anonymous</code>' dans la liste des identifiants.</p>
- <div class="example"><h3>Exemple:</h3><pre class="prettyprint lang-config"> Anonymous anonymous "Not Registered" "I don't know"</pre>
+ <div class="example"><h3>Exemple:</h3><pre class="prettyprint lang-config">Anonymous anonymous "Not Registered" "I don't know"</pre>
</div>
<p>Dans cet exemple, l'utilisateur peut accéder au site sans
<p>For example:</p>
- <pre class="prettyprint lang-config"> AuthName "Top Secret"</pre>
+ <pre class="prettyprint lang-config">AuthName "Top Secret"</pre>
<p>The string provided for the <code>AuthName</code> is what will
<p>Par exemple :</p>
- <pre class="prettyprint lang-config"> AuthName "Top Secret"</pre>
+ <pre class="prettyprint lang-config">AuthName "Top Secret"</pre>
<p>La chaîne fournie comme argument à <code>AuthName</code>
<code class="directive"><a href="#authldapbinddn">AuthLDAPBindDN</a></code>.
</p>
- <pre class="prettyprint lang-config"> AuthLDAPInitialBindPattern (.+) $1@example.com</pre>
+ <pre class="prettyprint lang-config">AuthLDAPInitialBindPattern (.+) $1@example.com</pre>
- <pre class="prettyprint lang-config"> AuthLDAPInitialBindPattern (.+) cn=$1,dc=example,dc=com</pre>
+ <pre class="prettyprint lang-config">AuthLDAPInitialBindPattern (.+) cn=$1,dc=example,dc=com</pre>
<div class="note"><h3>Not available with authorization-only</h3>
utiliser de nom d'utilisateur dédié via la directive <code class="directive"><a href="#authldapbinddn">AuthLDAPBindDN</a></code>.
</p>
- <pre class="prettyprint lang-config"> AuthLDAPInitialBindPattern (.+) $1@example.com</pre>
+ <pre class="prettyprint lang-config">AuthLDAPInitialBindPattern (.+) $1@example.com</pre>
- <pre class="prettyprint lang-config"> AuthLDAPInitialBindPattern (.+) cn=$1,dc=example,dc=com</pre>
+ <pre class="prettyprint lang-config">AuthLDAPInitialBindPattern (.+) cn=$1,dc=example,dc=com</pre>
<div class="note"><h3>Non disponible dans la cas d'une autorisation seule</h3>
'granted' or 'denied'. The following examples will grant or deny
access to all requests.</p>
- <pre class="prettyprint lang-config"> Require all granted</pre>
+ <pre class="prettyprint lang-config">Require all granted</pre>
- <pre class="prettyprint lang-config"> Require all denied</pre>
+ <pre class="prettyprint lang-config">Require all denied</pre>
<p>The following example will only allow GET, HEAD, POST, and OPTIONS
requests:</p>
- <pre class="prettyprint lang-config"> Require method GET POST OPTIONS</pre>
+ <pre class="prettyprint lang-config">Require method GET POST OPTIONS</pre>
<p>The following example will allow GET, HEAD, POST, and OPTIONS
<p>The <code>expr</code> provider allows to base authorization
decisions on arbitrary expressions.</p>
- <pre class="prettyprint lang-config"> Require expr "%{TIME_HOUR} -ge 9 && %{TIME_HOUR} -le 17"</pre>
+ <pre class="prettyprint lang-config">Require expr "%{TIME_HOUR} -ge 9 && %{TIME_HOUR} -le 17"</pre>
<p>The syntax is described in the <a href="../expr.html">ap_expr</a>
sont : 'granted' ou 'denied'. Les exemples suivants autorisent ou
interdisent l'accès à toutes les requêtes.</p>
- <pre class="prettyprint lang-config"> Require all granted</pre>
+ <pre class="prettyprint lang-config">Require all granted</pre>
- <pre class="prettyprint lang-config"> Require all denied</pre>
+ <pre class="prettyprint lang-config">Require all denied</pre>
<p>Dans l'exemple suivant, seules les méthodes GET, HEAD, POST, et
OPTIONS sont autorisées :</p>
- <pre class="prettyprint lang-config"> Require method GET POST OPTIONS</pre>
+ <pre class="prettyprint lang-config">Require method GET POST OPTIONS</pre>
<p>Dans l'exemple suivant, les méthodes GET, HEAD, POST, et OPTIONS
<p>Le fournisseur <code>expr</code> permet d'accorder l'autorisation
d'accès en fonction d'expressions arbitraires.</p>
- <pre class="prettyprint lang-config"> Require expr "%{TIME_HOUR} -ge 9 && %{TIME_HOUR} -le 17"</pre>
+ <pre class="prettyprint lang-config">Require expr "%{TIME_HOUR} -ge 9 && %{TIME_HOUR} -le 17"</pre>
<p>La syntaxe de l'expression est décrite dans la documentation de <a href="../expr.html">ap_expr</a>.</p>
<p>This directive specifies group membership that is required for the
user to gain access.</p>
- <pre class="prettyprint lang-config"> Require dbm-group admin</pre>
+ <pre class="prettyprint lang-config">Require dbm-group admin</pre>
<p>When this directive is specified, the user must be a member of the group
assigned to the file being accessed.</p>
- <pre class="prettyprint lang-config"> Require dbm-file-group</pre>
+ <pre class="prettyprint lang-config">Require dbm-file-group</pre>
<p>Cette directive permet de spécifier à quel groupe un utilisateur
doit appartenir pour obtenir l'autorisation d'accès.</p>
- <pre class="prettyprint lang-config"> Require dbm-group admin</pre>
+ <pre class="prettyprint lang-config">Require dbm-group admin</pre>
<p>Lorsque cette directive est définie, l'utilisateur doit
appartenir au groupe du fichier pour pouvoir y accéder.</p>
- <pre class="prettyprint lang-config"> Require dbm-file-group</pre>
+ <pre class="prettyprint lang-config">Require dbm-file-group</pre>
<p>This directive specifies group membership that is required for the
user to gain access.</p>
- <pre class="prettyprint lang-config"> Require group admin</pre>
+ <pre class="prettyprint lang-config">Require group admin</pre>
<p>When this directive is specified, the user must be a member of the group
assigned to the file being accessed.</p>
- <pre class="prettyprint lang-config"> Require file-group</pre>
+ <pre class="prettyprint lang-config">Require file-group</pre>
<p>Cette directive permet de spécifier à quel groupe un utilisateur
doit appartenir pour obtenir l'autorisation d'accès.</p>
- <pre class="prettyprint lang-config"> Require group admin</pre>
+ <pre class="prettyprint lang-config">Require group admin</pre>
<p>Lorsque cette directive est définie, l'utilisateur doit
appartenir au groupe du fichier pour pouvoir y accéder.</p>
- <pre class="prettyprint lang-config"> Require file-group</pre>
+ <pre class="prettyprint lang-config">Require file-group</pre>
<p>A network/netmask pair:</p>
- <pre class="prettyprint lang-config"> Require ip 10.1.0.0/255.255.0.0</pre>
+ <pre class="prettyprint lang-config">Require ip 10.1.0.0/255.255.0.0</pre>
<p>A network a.b.c.d, and a netmask w.x.y.z. For more
fine-grained subnet restriction.</p>
<p>A network/nnn CIDR specification:</p>
- <pre class="prettyprint lang-config"> Require ip 10.1.0.0/16</pre>
+ <pre class="prettyprint lang-config">Require ip 10.1.0.0/16</pre>
<p>Similar to the previous case, except the netmask consists of
nnn high-order 1 bits.</p>
<p>This allows a convenient way to match connections that originate from
the local host:</p>
- <pre class="prettyprint lang-config"> Require local</pre>
+ <pre class="prettyprint lang-config">Require local</pre>
<p>Une paire réseau/masque de sous-réseau :</p>
- <pre class="prettyprint lang-config"> Require ip 10.1.0.0/255.255.0.0</pre>
+ <pre class="prettyprint lang-config">Require ip 10.1.0.0/255.255.0.0</pre>
<p>Un réseau a.b.c.d, et un masque de sous-réseau w.x.y.z. pour une
restriction de sous-réseau plus fine.</p>
<p>Une spécification CIDR réseau/nnn :</p>
- <pre class="prettyprint lang-config"> Require ip 10.1.0.0/16</pre>
+ <pre class="prettyprint lang-config">Require ip 10.1.0.0/16</pre>
<p>Identique au cas précédent, excepté que le masque de sous-réseau
représente les nnn premiers bits de poids fort.</p>
<p>L'exemple suivant montre une méthode simple pour sélectionner les
connexions en provenance de l'hôte local :</p>
- <pre class="prettyprint lang-config"> Require local</pre>
+ <pre class="prettyprint lang-config">Require local</pre>
<p>This directive specifies a list of users that are allowed to gain
access.</p>
- <pre class="prettyprint lang-config"> Require user john paul george ringo</pre>
+ <pre class="prettyprint lang-config">Require user john paul george ringo</pre>
<p>When this directive is specified, any successfully authenticated
user will be allowed to gain access.</p>
- <pre class="prettyprint lang-config"> Require valid-user</pre>
+ <pre class="prettyprint lang-config">Require valid-user</pre>
<p>Cette directive permet de spécifier une liste d'utilisateurs
autorisés à accéder à la ressource.</p>
- <pre class="prettyprint lang-config"> Require user john paul george ringo</pre>
+ <pre class="prettyprint lang-config">Require user john paul george ringo</pre>
<p>Lorsque cette directive est définie, tout utilisateur qui s'est
authentifié avec succès aura l'autorisation d'accès à la ressource.</p>
- <pre class="prettyprint lang-config"> Require valid-user</pre>
+ <pre class="prettyprint lang-config">Require valid-user</pre>
This alternate text is displayed if the client is image-incapable,
has image loading disabled, or fails to retrieve the icon.</p>
- <pre class="prettyprint lang-config"> AddAltByEncoding gzip x-gzip</pre>
+ <pre class="prettyprint lang-config">AddAltByEncoding gzip x-gzip</pre>
</div>
This alternate text is displayed if the client is image-incapable,
has image loading disabled, or fails to retrieve the icon.</p>
- <pre class="prettyprint lang-config"> AddAltByType 'plain text' text/plain</pre>
+ <pre class="prettyprint lang-config">AddAltByType 'plain text' text/plain</pre>
</div>
<p><var>MIME-encoding</var> is a valid content-encoding, such as
<code>x-compress</code>.</p>
- <pre class="prettyprint lang-config"> AddIconByEncoding /icons/compress.png x-compress</pre>
+ <pre class="prettyprint lang-config">AddIconByEncoding /icons/compress.png x-compress</pre>
</div>
<p><var>MIME-type</var> is a wildcard expression matching
required the mime types.</p>
- <pre class="prettyprint lang-config"> AddIconByType (IMG,/icons/image.png) image/*</pre>
+ <pre class="prettyprint lang-config">AddIconByType (IMG,/icons/image.png) image/*</pre>
</div>
<var>Url-path</var> is a (%-escaped) relative URL to the icon,
or a fully qualified remote URL.</p>
- <pre class="prettyprint lang-config"> DefaultIcon /icon/unknown.png</pre>
+ <pre class="prettyprint lang-config">DefaultIcon /icon/unknown.png</pre>
</div>
of the file that will be inserted at the top of the index
listing. <var>Filename</var> is the name of the file to include.</p>
- <pre class="prettyprint lang-config"> HeaderName HEADER.html</pre>
+ <pre class="prettyprint lang-config">HeaderName HEADER.html</pre>
<div class="note">
access the directory being indexed. If <var>Filename</var> begins
with a slash, it will be taken to be relative to the <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>.</p>
- <pre class="prettyprint lang-config"> HeaderName /include/HEADER.html</pre>
+ <pre class="prettyprint lang-config">HeaderName /include/HEADER.html</pre>
<p><var>Filename</var> must resolve to a document with a major
actual file type (as opposed to its output) is marked as
<code>text/html</code> such as with a directive like:</p>
- <pre class="prettyprint lang-config"> AddType text/html .cgi</pre>
+ <pre class="prettyprint lang-config">AddType text/html .cgi</pre>
<p><a href="../content-negotiation.html">Content negotiation</a>
<p>The <code class="directive">IndexHeadInsert</code> directive specifies a
string to insert in the <var><head></var> section of the HTML
generated for the index page.</p>
- <pre class="prettyprint lang-config"> IndexHeadInsert "<link rel=\"sitemap\" href=\"/sitemap.html\">"</pre>
+ <pre class="prettyprint lang-config">IndexHeadInsert "<link rel=\"sitemap\" href=\"/sitemap.html\">"</pre>
</div>
files. By default, the list contains <code>.</code> (the current
directory).</p>
- <pre class="prettyprint lang-config"> IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t</pre>
+ <pre class="prettyprint lang-config">IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t</pre>
<div class="note"><h3>Regular Expressions</h3>
(It depends on whether the underlying file system
uses Unicode filenames or not.)
- <pre class="prettyprint lang-config"> IndexOptions Charset=UTF-8</pre>
+ <pre class="prettyprint lang-config">IndexOptions Charset=UTF-8</pre>
</dd>
specify the MIME content-type of the generated page. The default
is <var>text/html</var>.
- <pre class="prettyprint lang-config"> IndexOptions Type=text/plain</pre>
+ <pre class="prettyprint lang-config">IndexOptions Type=text/plain</pre>
</dd>
<p>will be the equivalent of</p>
- <pre class="prettyprint lang-config"> IndexOptions HTMLTable SuppressColumnsorting</pre>
+ <pre class="prettyprint lang-config">IndexOptions HTMLTable SuppressColumnsorting</pre>
</li>
<p>The <code class="directive">IndexStyleSheet</code> directive sets the name of
the file that will be used as the CSS for the index listing.
</p>
- <pre class="prettyprint lang-config"> IndexStyleSheet "/css/style.css"</pre>
+ <pre class="prettyprint lang-config">IndexStyleSheet "/css/style.css"</pre>
<p>Using this directive in conjunction with <code>IndexOptions
peut pas afficher d'images, si le chargement d'images est désactivé
ou si l'icône ne peut pas être trouvé.</p>
- <pre class="prettyprint lang-config"> AddAltByEncoding gzip x-gzip</pre>
+ <pre class="prettyprint lang-config">AddAltByEncoding gzip x-gzip</pre>
</div>
peut pas afficher d'images, si le chargement d'images est désactivé
ou si l'icône ne peut pas être trouvé.</p>
- <pre class="prettyprint lang-config"> AddAltByType 'Fichier texte' text/plain</pre>
+ <pre class="prettyprint lang-config">AddAltByType 'Fichier texte' text/plain</pre>
</div>
<p><var>codage MIME</var> doit être un codage valide, comme
<code>x-compress</code>.</p>
- <pre class="prettyprint lang-config"> AddIconByEncoding /icons/compress.png x-compress</pre>
+ <pre class="prettyprint lang-config">AddIconByEncoding /icons/compress.png x-compress</pre>
</div>
<p><var>type MIME</var> est une expression avec caractères
génériques représentant le type MIME.</p>
- <pre class="prettyprint lang-config"> AddIconByType (IMG,/icons/image.png) image/*</pre>
+ <pre class="prettyprint lang-config">AddIconByType (IMG,/icons/image.png) image/*</pre>
</div>
<var>chemin URL</var> est une URL relative (échappée par des
caractères '%') vers l'icône ou une URL pleinement qualifiée.</p>
- <pre class="prettyprint lang-config"> DefaultIcon /icon/unknown.png</pre>
+ <pre class="prettyprint lang-config">DefaultIcon /icon/unknown.png</pre>
</div>
le nom du fichier qui sera inséré au début de la page contenant
l'index. <var>nom fichier</var> est le nom du fichier à inclure.</p>
- <pre class="prettyprint lang-config"> HeaderName HEADER.html</pre>
+ <pre class="prettyprint lang-config">HeaderName HEADER.html</pre>
<div class="note">
considéré comme relatif au répertoire défini par la directive
<code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>.</p>
- <pre class="prettyprint lang-config"> HeaderName /include/HEADER.html</pre>
+ <pre class="prettyprint lang-config">HeaderName /include/HEADER.html</pre>
<p><var>nom fichier</var> doit correspondre à un document dont le
sortie) est marqué comme <code>text/html</code> par exemple à
l'aide d'une directive comme :</p>
- <pre class="prettyprint lang-config"> AddType text/html .cgi</pre>
+ <pre class="prettyprint lang-config">AddType text/html .cgi</pre>
<p>Une <a href="../content-negotiation.html">négociation de
spécifier une chaîne de caractères à insérer dans la section
<var><head></var> du code HTML généré pour la page
d'index.</p>
- <pre class="prettyprint lang-config"> IndexHeadInsert "<link rel=\"sitemap\" href=\"/sitemap.html\">"</pre>
+ <pre class="prettyprint lang-config">IndexHeadInsert "<link rel=\"sitemap\" href=\"/sitemap.html\">"</pre>
</div>
ignorer. Par défaut, la liste contient <code>.</code> (le répertoire
courant).</p>
- <pre class="prettyprint lang-config"> IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t</pre>
+ <pre class="prettyprint lang-config">IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t</pre>
<div class="note"><h3>Expressions rationnelles</h3>
système de fichiers sous-jacent utilise les noms de fichiers en
Unicode ou non).
- <pre class="prettyprint lang-config"> IndexOptions Charset=UTF-8</pre>
+ <pre class="prettyprint lang-config">IndexOptions Charset=UTF-8</pre>
</dd>
MIME de la page générée. La valeur par défaut est
<var>text/html</var>.
- <pre class="prettyprint lang-config"> IndexOptions Type=text/plain</pre>
+ <pre class="prettyprint lang-config">IndexOptions Type=text/plain</pre>
</dd>
<p>est équivalent à</p>
- <pre class="prettyprint lang-config"> IndexOptions HTMLTable SuppressColumnsorting</pre>
+ <pre class="prettyprint lang-config">IndexOptions HTMLTable SuppressColumnsorting</pre>
</li>
définir le nom du fichier qui servira de feuille de style CSS pour
l'index.
</p>
- <pre class="prettyprint lang-config"> IndexStyleSheet "/css/style.css"</pre>
+ <pre class="prettyprint lang-config">IndexStyleSheet "/css/style.css"</pre>
<p>L'utilisation de cette directive en conjonction avec <code>IndexOptions
<code class="directive"><a href="../mod/mod_mime.html#addoutputfilter">AddOutputFilter</a></code> or
<code class="directive"><a href="../mod/mod_filter.html#addoutputfilterbytype">AddOutputFilterByType</a></code> directives.</p>
- <div class="example"><h3>Using buffer with mod_include</h3><pre class="prettyprint lang-config"> AddOutputFilterByType INCLUDES;BUFFER text/html</pre>
+ <div class="example"><h3>Using buffer with mod_include</h3><pre class="prettyprint lang-config">AddOutputFilterByType INCLUDES;BUFFER text/html</pre>
</div>
<div class="warning">The buffer filters read the request/response into
directives <code class="directive"><a href="../mod/core.html#setinputfilter">SetInputFilter</a></code>,
<code class="directive"><a href="../mod/core.html#setoutputfilter">SetOutputFilter</a></code>, <code class="directive"><a href="../mod/mod_mime.html#addoutputfilter">AddOutputFilter</a></code> ou <code class="directive"><a href="../mod/mod_filter.html#addoutputfilterbytype">AddOutputFilterByType</a></code>.</p>
- <div class="example"><h3>Utilisation d'un tampon avec mod_include</h3><pre class="prettyprint lang-config"> AddOutputFilterByType INCLUDES;BUFFER text/html</pre>
+ <div class="example"><h3>Utilisation d'un tampon avec mod_include</h3><pre class="prettyprint lang-config">AddOutputFilterByType INCLUDES;BUFFER text/html</pre>
</div>
<div class="warning">Les filtres de mise en tampon lisent la
<code class="directive"><a href="../mod/mod_log_config.html#logformat">LogFormat</a></code> directive as
follows:</p>
- <pre class="prettyprint lang-config"> LogFormat "%{cache-status}e ..."</pre>
+ <pre class="prettyprint lang-config">LogFormat "%{cache-status}e ..."</pre>
<p>Based on the caching decision made, the reason is also written to the
with the document. The value specified with the <code class="directive">CacheMaxExpire</code>
directive does <em>not</em> override this setting.</p>
- <pre class="prettyprint lang-config"> CacheDefaultExpire 86400</pre>
+ <pre class="prettyprint lang-config">CacheDefaultExpire 86400</pre>
</div>
<code class="module"><a href="../mod/mod_cache.html">mod_cache</a></code> to <em>not</em> cache urls at or below
<var>url-string</var>.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> CacheDisable /local_files</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">CacheDisable /local_files</pre>
</div>
<p>If used in a <code class="directive"><Location></code> directive,
CacheHeader on</pre>
- <pre class="prettyprint lang-config"> X-Cache: HIT from localhost</pre>
+ <pre class="prettyprint lang-config">X-Cache: HIT from localhost</pre>
tells the server to attempt to serve the resource from the cache even
if the request contains no-cache header values.</p>
- <pre class="prettyprint lang-config"> CacheIgnoreCacheControl On</pre>
+ <pre class="prettyprint lang-config">CacheIgnoreCacheControl On</pre>
<div class="warning"><h3>Warning:</h3>
behaviour), <code class="directive">CacheIgnoreHeaders</code> can be set to
<code>None</code>.</p>
- <div class="example"><h3>Example 1</h3><pre class="prettyprint lang-config"> CacheIgnoreHeaders Set-Cookie</pre>
+ <div class="example"><h3>Example 1</h3><pre class="prettyprint lang-config">CacheIgnoreHeaders Set-Cookie</pre>
</div>
- <div class="example"><h3>Example 2</h3><pre class="prettyprint lang-config"> CacheIgnoreHeaders None</pre>
+ <div class="example"><h3>Example 2</h3><pre class="prettyprint lang-config">CacheIgnoreHeaders None</pre>
</div>
<div class="warning"><h3>Warning:</h3>
<code class="directive">CacheDefaultExpire</code> directive will be used to
generate an expiration date.</p>
- <pre class="prettyprint lang-config"> CacheIgnoreNoLastMod On</pre>
+ <pre class="prettyprint lang-config">CacheIgnoreNoLastMod On</pre>
</div>
view the request is treated as if having no query string when this
directive is enabled.</p>
- <pre class="prettyprint lang-config"> CacheIgnoreQueryString On</pre>
+ <pre class="prettyprint lang-config">CacheIgnoreQueryString On</pre>
<p><code>CacheIgnoreURLSessionIdentifiers None</code> clears the list of ignored
identifiers. Otherwise, each identifier is added to the list.</p>
- <div class="example"><h3>Example 1</h3><pre class="prettyprint lang-config"> CacheIgnoreURLSessionIdentifiers jsessionid</pre>
+ <div class="example"><h3>Example 1</h3><pre class="prettyprint lang-config">CacheIgnoreURLSessionIdentifiers jsessionid</pre>
</div>
- <div class="example"><h3>Example 2</h3><pre class="prettyprint lang-config"> CacheIgnoreURLSessionIdentifiers None</pre>
+ <div class="example"><h3>Example 2</h3><pre class="prettyprint lang-config">CacheIgnoreURLSessionIdentifiers None</pre>
</div>
<code class="directive">CacheMaxExpire</code>, then the latter takes
precedence.</p>
- <pre class="prettyprint lang-config"> CacheLastModifiedFactor 0.5</pre>
+ <pre class="prettyprint lang-config">CacheLastModifiedFactor 0.5</pre>
</div>
server. Thus, documents will be out of date at most this number of seconds. This maximum
value is enforced even if an expiry date was supplied with the document.</p>
- <pre class="prettyprint lang-config"> CacheMaxExpire 604800</pre>
+ <pre class="prettyprint lang-config">CacheMaxExpire 604800</pre>
</div>
server. This is only used if no valid expire time was supplied with the document.</p>
- <pre class="prettyprint lang-config"> CacheMinExpire 3600</pre>
+ <pre class="prettyprint lang-config">CacheMinExpire 3600</pre>
</div>
the origin server, and the response may be fulfilled from cache
if the backend resource has not changed.</p>
- <pre class="prettyprint lang-config"> CacheStoreExpired On</pre>
+ <pre class="prettyprint lang-config">CacheStoreExpired On</pre>
</div>
tells the server to attempt to cache the resource even if it contains
no-store header values.</p>
- <pre class="prettyprint lang-config"> CacheStoreNoStore On</pre>
+ <pre class="prettyprint lang-config">CacheStoreNoStore On</pre>
<div class="warning"><h3>Warning:</h3>
tells the server to attempt to cache the resource even if it contains
private header values.</p>
- <pre class="prettyprint lang-config"> CacheStorePrivate On</pre>
+ <pre class="prettyprint lang-config">CacheStorePrivate On</pre>
<div class="warning"><h3>Warning:</h3>
interne à la requête sous la clé <strong>cache-status</strong>.
Cette information peut être journalisée via la directive <code class="directive"><a href="../mod/mod_log_config.html#logformat">LogFormat</a></code> comme suit :</p>
- <pre class="prettyprint lang-config"> LogFormat "%{cache-status}e ..."</pre>
+ <pre class="prettyprint lang-config">LogFormat "%{cache-status}e ..."</pre>
<p>En fonction de la décision prise, l'information est aussi écrite
<code class="directive">CacheMaxExpire</code> si cette dernière est
utilisée.</p>
- <pre class="prettyprint lang-config"> CacheDefaultExpire 86400</pre>
+ <pre class="prettyprint lang-config">CacheDefaultExpire 86400</pre>
</div>
spécifiée par <var>chaîne URL</var>, ainsi que les URLs de niveaux
inférieurs.</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> CacheDisable /fichiers_locaux</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">CacheDisable /fichiers_locaux</pre>
</div>
<p>Si la directive se trouve à l'intérieur d'une section <code class="directive"><Location></code>, le chemin doit être spécifié en
CacheHeader on</pre>
- <pre class="prettyprint lang-config"> X-Cache: HIT from localhost</pre>
+ <pre class="prettyprint lang-config">X-Cache: HIT from localhost</pre>
cache, même si la requête contient un en-tête
no-cache.</p>
- <pre class="prettyprint lang-config"> CacheIgnoreCacheControl On</pre>
+ <pre class="prettyprint lang-config">CacheIgnoreCacheControl On</pre>
<div class="warning"><h3>Avertissement :</h3>
<code class="directive">CacheIgnoreHeaders</code> peut être définie à
<code>None</code>.</p>
- <div class="example"><h3>Exemple 1</h3><pre class="prettyprint lang-config"> CacheIgnoreHeaders Set-Cookie</pre>
+ <div class="example"><h3>Exemple 1</h3><pre class="prettyprint lang-config">CacheIgnoreHeaders Set-Cookie</pre>
</div>
- <div class="example"><h3>Exemple 2</h3><pre class="prettyprint lang-config"> CacheIgnoreHeaders None</pre>
+ <div class="example"><h3>Exemple 2</h3><pre class="prettyprint lang-config">CacheIgnoreHeaders None</pre>
</div>
<div class="warning"><h3>Avertissement :</h3>
d'expiration.
</p>
- <pre class="prettyprint lang-config"> CacheIgnoreNoLastMod On</pre>
+ <pre class="prettyprint lang-config">CacheIgnoreNoLastMod On</pre>
</div>
traitée comme si elle ne possèdait pas de chaîne de paramètres
lorsque cette directive est activée.</p>
- <pre class="prettyprint lang-config"> CacheIgnoreQueryString On</pre>
+ <pre class="prettyprint lang-config">CacheIgnoreQueryString On</pre>
des identifiants ignorés. Autrement, chaque identifiant spécifié est
ajouté à la liste.</p>
- <div class="example"><h3>Exemple 1</h3><pre class="prettyprint lang-config"> CacheIgnoreURLSessionIdentifiers jsessionid</pre>
+ <div class="example"><h3>Exemple 1</h3><pre class="prettyprint lang-config">CacheIgnoreURLSessionIdentifiers jsessionid</pre>
</div>
- <div class="example"><h3>Exemple 2</h3><pre class="prettyprint lang-config"> CacheIgnoreURLSessionIdentifiers None</pre>
+ <div class="example"><h3>Exemple 2</h3><pre class="prettyprint lang-config">CacheIgnoreURLSessionIdentifiers None</pre>
</div>
directive <code class="directive">CacheMaxExpire</code>, c'est ce dernier
qui l'emporte.</p>
- <pre class="prettyprint lang-config"> CacheLastModifiedFactor 0.5</pre>
+ <pre class="prettyprint lang-config">CacheLastModifiedFactor 0.5</pre>
</div>
sera pas à jour. L'utilisation de cette valeur maximale est forcée,
même si le document possède une date d'expiration.</p>
- <pre class="prettyprint lang-config"> CacheMaxExpire 604800</pre>
+ <pre class="prettyprint lang-config">CacheMaxExpire 604800</pre>
que dans le cas où le document ne possède aucune date d'expiration
valide.</p>
- <pre class="prettyprint lang-config"> CacheMinExpire 3600</pre>
+ <pre class="prettyprint lang-config">CacheMinExpire 3600</pre>
</div>
de la part du serveur d'origine, et la réponse sera renvoyée à
partir du cache si la ressource d'arrière-plan n'a pas été modifiée.</p>
- <pre class="prettyprint lang-config"> CacheStoreExpired On</pre>
+ <pre class="prettyprint lang-config">CacheStoreExpired On</pre>
un en-tête no-store.</p>
- <pre class="prettyprint lang-config"> CacheStoreNoStore On</pre>
+ <pre class="prettyprint lang-config">CacheStoreNoStore On</pre>
contient un en-tête private.</p>
- <pre class="prettyprint lang-config"> CacheStorePrivate On</pre>
+ <pre class="prettyprint lang-config">CacheStorePrivate On</pre>
maximum size, in bytes, for a document to be considered for storage in
the cache.</p>
- <pre class="prettyprint lang-config"> CacheMaxFileSize 64000</pre>
+ <pre class="prettyprint lang-config">CacheMaxFileSize 64000</pre>
</div>
minimum size, in bytes, for a document to be considered for storage
in the cache.</p>
- <pre class="prettyprint lang-config"> CacheMinFileSize 64</pre>
+ <pre class="prettyprint lang-config">CacheMinFileSize 64</pre>
</div>
<p>This directive only takes effect when the data is being saved to the
cache, as opposed to data being served from the cache.</p>
- <pre class="prettyprint lang-config"> CacheReadSize 102400</pre>
+ <pre class="prettyprint lang-config">CacheReadSize 102400</pre>
</div>
ensure that the server does not buffer excessively should data arrive faster
than expected.</p>
- <pre class="prettyprint lang-config"> CacheReadTime 1000</pre>
+ <pre class="prettyprint lang-config">CacheReadTime 1000</pre>
</div>
a configuration file processing error. The <code class="directive"><a href="#cachedirlevels">CacheDirLevels</a></code> and <code class="directive"><a href="#cachedirlength">CacheDirLength</a></code> directives define
the structure of the directories under the specified root directory.</p>
- <pre class="prettyprint lang-config"> CacheRoot c:/cacheroot</pre>
+ <pre class="prettyprint lang-config">CacheRoot c:/cacheroot</pre>
</div>
définir la taille maximale d'un document, en octets, pour que
celui-ci puisse faire l'objet d'un stockage dans le cache.</p>
- <pre class="prettyprint lang-config"> CacheMaxFileSize 64000</pre>
+ <pre class="prettyprint lang-config">CacheMaxFileSize 64000</pre>
</div>
définir la taille minimale d'un document, en octets, pour que
celui-ci puisse faire l'objet d'un stockage dans le cache.</p>
- <pre class="prettyprint lang-config"> CacheMinFileSize 64</pre>
+ <pre class="prettyprint lang-config">CacheMinFileSize 64</pre>
</div>
enregistrées dans le cache, et non lorsque les données sont servies à
partir du cache.</p>
- <pre class="prettyprint lang-config"> CacheReadSize 102400</pre>
+ <pre class="prettyprint lang-config">CacheReadSize 102400</pre>
</div>
que le serveur n'effectue pas une mise en tampon excessive au cas
où les données arriveraient plus vite que prévu.</p>
- <pre class="prettyprint lang-config"> CacheReadTime 1000</pre>
+ <pre class="prettyprint lang-config">CacheReadTime 1000</pre>
</div>
définir la structure des sous-répertoires du répertoire racine
spécifié.</p>
- <pre class="prettyprint lang-config"> CacheRoot c:/cacheroot</pre>
+ <pre class="prettyprint lang-config">CacheRoot c:/cacheroot</pre>
</div>
implementations</a> of shared object caches are available to choose
from.</p>
- <pre class="prettyprint lang-config"> CacheSocache shmcb</pre>
+ <pre class="prettyprint lang-config">CacheSocache shmcb</pre>
</div>
responses larger than those cacheable within
<code class="module"><a href="../mod/mod_cache_socache.html">mod_cache_socache</a></code>.</p>
- <pre class="prettyprint lang-config"> CacheSocacheMaxSize 102400</pre>
+ <pre class="prettyprint lang-config">CacheSocacheMaxSize 102400</pre>
</div>
the cache. This value overrides the freshness lifetime defined for the
document by the HTTP protocol.</p>
- <pre class="prettyprint lang-config"> CacheSocacheMaxTime 86400</pre>
+ <pre class="prettyprint lang-config">CacheSocacheMaxTime 86400</pre>
</div>
only stored for its freshness lifetime, there will be no opportunity to
revalidate the response to make it fresh again.</p>
- <pre class="prettyprint lang-config"> CacheSocacheMinTime 600</pre>
+ <pre class="prettyprint lang-config">CacheSocacheMinTime 600</pre>
</div>
<p>This directive only takes effect when the data is being saved to the
cache, as opposed to data being served from the cache.</p>
- <pre class="prettyprint lang-config"> CacheReadSize 102400</pre>
+ <pre class="prettyprint lang-config">CacheReadSize 102400</pre>
</div>
to ensure that the server does not buffer excessively should data arrive faster
than expected.</p>
- <pre class="prettyprint lang-config"> CacheSocacheReadTime 1000</pre>
+ <pre class="prettyprint lang-config">CacheSocacheReadTime 1000</pre>
</div>
possible de choisir entre plusieurs <a href="../socache.html">implémentations</a> de caches d'objets
partagés.</p>
- <pre class="prettyprint lang-config"> CacheSocache shmcb</pre>
+ <pre class="prettyprint lang-config">CacheSocache shmcb</pre>
</div>
la taille est trop importante pour pouvoir être mises en cache par
<code class="module"><a href="../mod/mod_cache_socache.html">mod_cache_socache</a></code>.</p>
- <pre class="prettyprint lang-config"> CacheSocacheMaxSize 102400</pre>
+ <pre class="prettyprint lang-config">CacheSocacheMaxSize 102400</pre>
</div>
le cache avant péremption. Cette définition l'emporte sur la durée
de fraîcheur définie pour le document par le protocole HTTP.</p>
- <pre class="prettyprint lang-config"> CacheSocacheMaxTime 86400</pre>
+ <pre class="prettyprint lang-config">CacheSocacheMaxTime 86400</pre>
</div>
pour une durée égale à sa durée de fraîcheur, elle n'a pas besoin
d'être rafraîchie.</p>
- <pre class="prettyprint lang-config"> CacheSocacheMinTime 600</pre>
+ <pre class="prettyprint lang-config">CacheSocacheMinTime 600</pre>
</div>
stockées dans le cache, et non lorsqu'elles sont servies depuis le
cache.</p>
- <pre class="prettyprint lang-config"> CacheReadSize 102400</pre>
+ <pre class="prettyprint lang-config">CacheReadSize 102400</pre>
</div>
manière excessive dans le cas où les données arriveraient plus vite
que prévu.</p>
- <pre class="prettyprint lang-config"> CacheSocacheReadTime 1000</pre>
+ <pre class="prettyprint lang-config">CacheSocacheReadTime 1000</pre>
</div>
will use its contents to generate additional MIME header
information.</p>
- <div class="example"><h3>Example:</h3><pre class="prettyprint lang-config"> MetaSuffix .meta</pre>
+ <div class="example"><h3>Example:</h3><pre class="prettyprint lang-config">MetaSuffix .meta</pre>
</div>
</div>
son contenu pour générer les informations quant aux en-têtes MIME
additionnels.</p>
- <div class="example"><h3>Exemple :</h3><pre class="prettyprint lang-config"> MetaSuffix .meta</pre>
+ <div class="example"><h3>Exemple :</h3><pre class="prettyprint lang-config">MetaSuffix .meta</pre>
</div>
</div>
taken relative to the <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>.
</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> ScriptLog logs/cgi_log</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">ScriptLog logs/cgi_log</pre>
</div>
<p>This log will be opened as the user the child processes run
répertoire défini par la directive <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>.
</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> ScriptLog logs/cgi_log</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">ScriptLog logs/cgi_log</pre>
</div>
<p>Ce journal sera ouvert par l'utilisateur sous lequel les
the CGI program. If the time is exceeded, the request and CGI are
terminated.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> CGIDScriptTimeout 20</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">CGIDScriptTimeout 20</pre>
</div>
will be relative to the value of
<code class="directive"><a href="../mod/core.html#defaultruntimedir">DefaultRuntimeDir</a></code>.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> ScriptSock /var/run/cgid.sock</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">ScriptSock /var/run/cgid.sock</pre>
</div>
reçues en sortie du programme CGI. Si ce temps est dépassé, la requête et le
programme CGI se terminent.</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> CGIDScriptTimeout 20</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">CGIDScriptTimeout 20</pre>
</div>
<p>Si <var>chemin fichier</var> n'est pas un chemin absolu, il est
relatif au chemin défini par la directive <code class="directive"><a href="../mod/core.html#defaultruntimedir">DefaultRuntimeDir</a></code>.</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> ScriptSock /var/run/cgid.sock</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">ScriptSock /var/run/cgid.sock</pre>
</div>
file using the <code class="directive"><a href="../mod/mod_dav_fs.html#davlockdb">DavLockDB</a></code>
directive:</p>
- <pre class="prettyprint lang-config"> DavLockDB /usr/local/apache2/var/DavLock</pre>
+ <pre class="prettyprint lang-config">DavLockDB /usr/local/apache2/var/DavLock</pre>
<p>The directory containing the lock database file must be
verrous DAV via une directive <code class="directive"><a href="../mod/mod_dav_fs.html#davlockdb">DavLockDB</a></code> dans la section globale de
votre fichier <code>httpd.conf</code> :</p>
- <pre class="prettyprint lang-config"> DavLockDB /usr/local/apache2/var/DavLock</pre>
+ <pre class="prettyprint lang-config">DavLockDB /usr/local/apache2/var/DavLock</pre>
<p>Le répertoire contenant le fichier de la base de données des
will be invoked by using the <code class="directive"><a href="../mod/mod_dav.html#dav">Dav</a></code>
directive:</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> Dav filesystem</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">Dav filesystem</pre>
</div>
<p>Since <code>filesystem</code> is the default provider for
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> DavLockDB var/DavLock</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">DavLockDB var/DavLock</pre>
</div>
<p>The directory containing the lock database file must be
de <code class="module"><a href="../mod/mod_dav.html">mod_dav</a></code> sont invoqués via la directive
<code class="directive"><a href="../mod/mod_dav.html#dav">Dav</a></code> :</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> Dav filesystem</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">Dav filesystem</pre>
</div>
<p>Comme <code>filesystem</code> est le fournisseur par défaut de
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> DavLockDB var/DavLock</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">DavLockDB var/DavLock</pre>
</div>
<p>Les utilisateur et groupe sous lesquels Apache s'exécute et qui
<code class="module"><a href="../mod/mod_dav_lock.html">mod_dav_lock</a></code> uses a SDBM database to track user
locks.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> DavGenericLockDB var/DavLock</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">DavGenericLockDB var/DavLock</pre>
</div>
<p>The directory containing the lock database file must be
<code class="module"><a href="../mod/mod_dav_lock.html">mod_dav_lock</a></code> utilise une base de données SDBM pour
surveiller les verrous utilisateurs.</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> DavGenericLockDB var/DavLock</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">DavGenericLockDB var/DavLock</pre>
</div>
<p>Les utilisateur et groupe sous lesquels Apache s'exécute et qui
</div>
<p>This is a simple configuration that compresses common text-based content types.</p>
- <div class="example"><h3>Compress only a few types</h3><pre class="prettyprint lang-config"> AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript</pre>
+ <div class="example"><h3>Compress only a few types</h3><pre class="prettyprint lang-config">AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript</pre>
</div>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
in a typical configuration where the addition of the <code>DEFLATE</code>
filter depends on the <code>User-Agent</code>, you should add:</p>
- <pre class="prettyprint lang-config"> Header append Vary User-Agent</pre>
+ <pre class="prettyprint lang-config">Header append Vary User-Agent</pre>
<p>If your decision about compression depends on other information
<code>Vary</code> header to the value <code>*</code>. This prevents
compliant proxies from caching entirely.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> Header set Vary *</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">Header set Vary *</pre>
</div>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<p>Voici un exemple simple de configuration qui permet de comprimer
les types de contenu à base de texte.</p>
- <div class="example"><h3>Ne comprime que certains types de documents</h3><pre class="prettyprint lang-config"> AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript</pre>
+ <div class="example"><h3>Ne comprime que certains types de documents</h3><pre class="prettyprint lang-config">AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript</pre>
</div>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<code>DEFLATE</code> dépend du contenu de l'en-tête
<code>User-Agent</code>, vous devez spécifier :</p>
- <pre class="prettyprint lang-config"> Header append Vary User-Agent</pre>
+ <pre class="prettyprint lang-config">Header append Vary User-Agent</pre>
<p>Si votre décision de comprimer le contenu dépend d'autres
<code>Vary</code> la valeur <code>*</code>, ce qui permet d'empêcher
les mandataires compatibles de tout mettre en cache.</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> Header set Vary *</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">Header set Vary *</pre>
</div>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
set, the server will generate its own listing of the
directory.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> DirectoryIndex index.html</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">DirectoryIndex index.html</pre>
</div>
<p>then a request for <code>http://example.com/docs/</code> would
<p>Note that the documents do not need to be relative to the
directory;</p>
- <pre class="prettyprint lang-config"> DirectoryIndex index.html index.txt /cgi-bin/index.pl</pre>
+ <pre class="prettyprint lang-config">DirectoryIndex index.html index.txt /cgi-bin/index.pl</pre>
<p>would cause the CGI script <code>/cgi-bin/index.pl</code> to be
</ul>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> DirectoryIndexRedirect on</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">DirectoryIndexRedirect on</pre>
</div>
<p>A request for <code>http://example.com/docs/</code> would
<p>Use this to set a handler for any URL that doesn't map to anything
in your filesystem, and would otherwise return HTTP 404 (Not Found).
For example</p>
- <pre class="prettyprint lang-config"> FallbackResource /not-404.php</pre>
+ <pre class="prettyprint lang-config">FallbackResource /not-404.php</pre>
<p>will cause requests for non-existent files to be handled by
<code>not-404.php</code>, while requests for files that exist
<code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>, and the use of the <code>-f</code> and
<code>-d</code> tests for file and directory existence. This now
requires only one line of configuration.</p>
- <pre class="prettyprint lang-config"> FallbackResource /index.php</pre>
+ <pre class="prettyprint lang-config">FallbackResource /index.php</pre>
<p>Existing files, such as images, css files, and so on, will be
served normally.</p>
<code>Indexes</code> est définie, le serveur générera son propre
listing du répertoire.</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> DirectoryIndex index.html</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">DirectoryIndex index.html</pre>
</div>
<p>Avec cette configuration, une requête pour l'URL
<p>Notez qu'il n'est pas nécessaire que les documents soient
relatifs au répertoire ;</p>
- <pre class="prettyprint lang-config"> DirectoryIndex index.html index.txt /cgi-bin/index.pl</pre>
+ <pre class="prettyprint lang-config">DirectoryIndex index.html index.txt /cgi-bin/index.pl</pre>
<p>provoquerait l'exécution du script CGI
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> DirectoryIndexRedirect on</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">DirectoryIndexRedirect on</pre>
</div>
<p>Une requête pour <code>http://example.com/docs/</code> se
et qui provoquerait sans cela l'envoi d'un code d'erreur HTTP 404
(Not Found).
Par exemple</p>
- <pre class="prettyprint lang-config"> FallbackResource /not-404.php</pre>
+ <pre class="prettyprint lang-config">FallbackResource /not-404.php</pre>
<p>fait en sorte que les requêtes ne correspondant à aucun fichier
soient traitées par <code>non-404.php</code>, sans affecter les
conditionnels <code>-f</code> et <code>-d</code> pour vérifier
l'existence des fichiers et répertoires. Maintenant, une seule ligne
de configuration est nécessaire.</p>
- <pre class="prettyprint lang-config"> FallbackResource /index.php</pre>
+ <pre class="prettyprint lang-config">FallbackResource /index.php</pre>
<p>Les fichiers existants comme des images, des fichiers css, etc...
seront traités normalement.</p>
the below directives. Additionally, <code class="module"><a href="../mod/mod_dumpio.html">mod_dumpio</a></code>
needs to be configured to <code class="directive"><a href="../mod/core.html#loglevel">LogLevel</a></code> <code>trace7</code>:
</p>
- <pre class="prettyprint lang-config"> LogLevel dumpio:trace7</pre>
+ <pre class="prettyprint lang-config">LogLevel dumpio:trace7</pre>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
</table>
<p>Enable dumping of all input.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> DumpIOInput On</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">DumpIOInput On</pre>
</div>
</div>
</table>
<p>Enable dumping of all output.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> DumpIOOutput On</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">DumpIOOutput On</pre>
</div>
</div>
<p>The <code class="directive">ProtocolEcho</code> directive enables or
disables the echo server.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> ProtocolEcho On</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">ProtocolEcho On</pre>
</div>
</div>
<p>La directive <code class="directive">ProtocolEcho</code> permet d'activer
ou de désactiver le serveur d'écho.</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> ProtocolEcho On</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">ProtocolEcho On</pre>
</div>
</div>
native OS environment of the shell which invoked the
<code class="program"><a href="../programs/httpd.html">httpd</a></code> process.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> PassEnv LD_LIBRARY_PATH</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">PassEnv LD_LIBRARY_PATH</pre>
</div>
</div>
<p>Sets an internal environment variable, which is then available to Apache
HTTP Server modules, and passed on to CGI scripts and SSI pages.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> SetEnv SPECIAL_PATH /foo/bin</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">SetEnv SPECIAL_PATH /foo/bin</pre>
</div>
<p> If you omit the <var>value</var> argument, the variable is set to
<p>Removes one or more internal environment variables from those passed
on to CGI scripts and SSI pages.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> UnsetEnv LD_LIBRARY_PATH</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">UnsetEnv LD_LIBRARY_PATH</pre>
</div>
</div>
valeurs sont issues de l'environnement natif de l'OS associé au
shell qui a invoqué le processus <code class="program"><a href="../programs/httpd.html">httpd</a></code>.</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> PassEnv LD_LIBRARY_PATH</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">PassEnv LD_LIBRARY_PATH</pre>
</div>
</div>
ensuite disponible pour les modules du serveur HTTP Apache et
transmise aux scripts CGI et aux pages SSI.</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> SetEnv SPECIAL_PATH /foo/bin</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">SetEnv SPECIAL_PATH /foo/bin</pre>
</div>
<p>Si l'argument <var>valeur</var> est absent, la variable est
<p>Supprime une ou plusieurs variables d'environnement internes parmi celles
qui sont transmises aux scripts CGI et aux pages SSI.</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> UnsetEnv LD_LIBRARY_PATH</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">UnsetEnv LD_LIBRARY_PATH</pre>
</div>
</div>
<p>As an alternative, you can put the following into a <a href="core.html#accessfilename"><code>.htaccess</code></a> file
and then request the file "test.example" from that location:</p>
-<pre class="prettyprint lang-config"> AddHandler example-handler .example</pre>
+<pre class="prettyprint lang-config">AddHandler example-handler .example</pre>
<p>After reloading/restarting your server, you should be able
accéder au fichier "test.example" à partir du répertoire
correspondant :</p>
-<pre class="prettyprint lang-config"> AddHandler example-handler .example</pre>
+<pre class="prettyprint lang-config">AddHandler example-handler .example</pre>
filter is removed and the request continues without it.</dd>
</dl>
- <pre class="prettyprint lang-config"> ExtFilterOptions LogStderr</pre>
+ <pre class="prettyprint lang-config">ExtFilterOptions LogStderr</pre>
<p>Messages written to the filter's standard error will be stored
sans lui.</dd>
</dl>
- <pre class="prettyprint lang-config"> ExtFilterOptions LogStderr</pre>
+ <pre class="prettyprint lang-config">ExtFilterOptions LogStderr</pre>
<p>Les messages envoyés vers la sortie d'erreurs standard du filtre
with filenames rewritten by <code class="module"><a href="../mod/mod_alias.html">mod_alias</a></code> or
<code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> CacheFile /usr/local/apache/htdocs/index.html</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">CacheFile /usr/local/apache/htdocs/index.html</pre>
</div>
</div>
with filenames rewritten by <code class="module"><a href="../mod/mod_alias.html">mod_alias</a></code> or
<code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> MMapFile /usr/local/apache/htdocs/index.html</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">MMapFile /usr/local/apache/htdocs/index.html</pre>
</div>
</div>
fichiers réécrits par <code class="module"><a href="../mod/mod_alias.html">mod_alias</a></code> ou
<code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>.</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> CacheFile /usr/local/apache/htdocs/index.html</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">CacheFile /usr/local/apache/htdocs/index.html</pre>
</div>
</div>
fichiers réécrits par <code class="module"><a href="../mod/mod_alias.html">mod_alias</a></code> ou
<code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>.</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> MMapFile /usr/local/apache/htdocs/index.html</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">MMapFile /usr/local/apache/htdocs/index.html</pre>
</div>
</div>
<code>text/html</code> or <code>text/plain</code> before it is sent
to the client.</p>
- <pre class="prettyprint lang-config"> AddOutputFilterByType DEFLATE text/html text/plain</pre>
+ <pre class="prettyprint lang-config">AddOutputFilterByType DEFLATE text/html text/plain</pre>
<p>If you want the content to be processed by more than one filter, their
requests will be captured within the same connection if keepalive is
present.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> FirehoseConnectionInput connection-input.firehose</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">FirehoseConnectionInput connection-input.firehose</pre>
</div>
</div>
Multiple requests will be captured within the same connection if
keepalive is present.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> FirehoseConnectionOutput connection-output.firehose</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">FirehoseConnectionOutput connection-output.firehose</pre>
</div>
</div>
</table>
<p>Capture traffic being received by mod_proxy.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> FirehoseProxyConnectionInput proxy-input.firehose</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">FirehoseProxyConnectionInput proxy-input.firehose</pre>
</div>
</div>
</table>
<p>Capture traffic being sent out by mod_proxy.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> FirehoseProxyConnectionOutput proxy-output.firehose</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">FirehoseProxyConnectionOutput proxy-output.firehose</pre>
</div>
</div>
<p>Capture traffic coming into the server on each request. Requests
will be captured separately, regardless of the presence of keepalive.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> FirehoseRequestInput request-input.firehose</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">FirehoseRequestInput request-input.firehose</pre>
</div>
</div>
<p>Capture traffic going out of the server on each request. Requests
will be captured separately, regardless of the presence of keepalive.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> FirehoseRequestOutput request-output.firehose</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">FirehoseRequestOutput request-output.firehose</pre>
</div>
</div>
Copy all request headers that begin with "TS" to the
response headers:
- <pre class="prettyprint lang-config"> Header echo ^TS</pre>
+ <pre class="prettyprint lang-config">Header echo ^TS</pre>
</li>
the client to intuit load on the server or in isolating
bottlenecks between the client and the server.
- <pre class="prettyprint lang-config"> Header set MyHeader "%D %t"</pre>
+ <pre class="prettyprint lang-config">Header set MyHeader "%D %t"</pre>
<p>results in this header being added to the response:</p>
description</a>) by replacing <var>https:</var> with
<var>http:</var> in the <var>Destination</var> header:
- <pre class="prettyprint lang-config"> RequestHeader edit Destination ^https: http: early</pre>
+ <pre class="prettyprint lang-config">RequestHeader edit Destination ^https: http: early</pre>
</li>
</li>
<li>
Set a test cookie if and only if the client didn't send us a cookie
- <pre class="prettyprint lang-config"> Header set Set-Cookie testcookie "expr=-z %{req:Cookie}"</pre>
+ <pre class="prettyprint lang-config">Header set Set-Cookie testcookie "expr=-z %{req:Cookie}"</pre>
</li>
</ol>
Copie tous les en-têtes de requête qui commencent par "TS" vers
les en-têtes de la réponse :
- <pre class="prettyprint lang-config"> Header echo ^TS</pre>
+ <pre class="prettyprint lang-config">Header echo ^TS</pre>
</li>
isoler les goulets d'étranglement entre le client et le
serveur.
- <pre class="prettyprint lang-config"> Header set mon-en-tête "%D %t"</pre>
+ <pre class="prettyprint lang-config">Header set mon-en-tête "%D %t"</pre>
<p>le résultat est l'ajout à la réponse d'un en-tête du type :</p>
du problème</a>) en remplaçant <var>https:</var> par
<var>http:</var> dans l'en-tête <var>Destination</var> :
- <pre class="prettyprint lang-config"> RequestHeader edit Destination ^https: http: early</pre>
+ <pre class="prettyprint lang-config">RequestHeader edit Destination ^https: http: early</pre>
</li>
<li>
Définit un cookie de test si et seulement si le client n'envoie
pas de cookie
- <pre class="prettyprint lang-config"> Header set Set-Cookie testcookie "expr=-z %{req:Cookie}"</pre>
+ <pre class="prettyprint lang-config">Header set Set-Cookie testcookie "expr=-z %{req:Cookie}"</pre>
</li>
</ol>
address will usually correspond to a configured <code class="directive"><a href="../mod/mod_heartbeat.html#heartbeataddress">HeartbeatAddress</a></code> on an origin server.
</p>
- <pre class="prettyprint lang-config"> HeartbeatListen 239.0.0.1:27999</pre>
+ <pre class="prettyprint lang-config">HeartbeatListen 239.0.0.1:27999</pre>
<p> This module is inactive until this directive is used.</p>
<code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> <code>Options</code>
is set):</p>
- <pre class="prettyprint lang-config"> Options +Includes</pre>
+ <pre class="prettyprint lang-config">Options +Includes</pre>
<p>For backwards compatibility, the <code>server-parsed</code>
<p>This directive changes the string that <code class="module"><a href="../mod/mod_include.html">mod_include</a></code>
looks for to mark the end of an include element.</p>
- <pre class="prettyprint lang-config"> SSIEndTag "%>"</pre>
+ <pre class="prettyprint lang-config">SSIEndTag "%>"</pre>
<p>This directive has the same effect as the <code><!--#config
errmsg=<var>message</var> --></code> element.</p>
- <pre class="prettyprint lang-config"> SSIErrorMsg "<!-- Error -->"</pre>
+ <pre class="prettyprint lang-config">SSIErrorMsg "<!-- Error -->"</pre>
</div>
output of a file each processing different commands (possibly at
different times).</p>
- <pre class="prettyprint lang-config"> SSIStartTag "<%"<br />
+ <pre class="prettyprint lang-config">SSIStartTag "<%"<br />
SSIEndTag "%>"</pre>
<p>This directive has the same effect as the <code><!--#config
timefmt=<var>formatstring</var> --></code> element.</p>
- <pre class="prettyprint lang-config"> SSITimeFormat "%R, %B %d, %Y"</pre>
+ <pre class="prettyprint lang-config">SSITimeFormat "%R, %B %d, %Y"</pre>
<p>The above directive would cause times to be displayed in the
<p>This directive changes the string that <code class="module"><a href="../mod/mod_include.html">mod_include</a></code>
displays when a variable is not set and "echoed".</p>
- <pre class="prettyprint lang-config"> SSIUndefinedEcho "<!-- undef -->"</pre>
+ <pre class="prettyprint lang-config">SSIUndefinedEcho "<!-- undef -->"</pre>
</div>
it to them with their file extensions. To enable any .dll file to be
processed as an ISAPI extension, edit the httpd.conf file and add the
following line:</p>
- <pre class="prettyprint lang-config"> AddHandler isapi-handler .dll</pre>
+ <pre class="prettyprint lang-config">AddHandler isapi-handler .dll</pre>
<div class="note">In older versions of the Apache server,
requested module loaded. However, you may preload and keep a
specific module loaded by using the following syntax in your
httpd.conf:</p>
- <pre class="prettyprint lang-config"> ISAPICacheFile c:/WebWork/Scripts/ISAPI/mytest.dll</pre>
+ <pre class="prettyprint lang-config">ISAPICacheFile c:/WebWork/Scripts/ISAPI/mytest.dll</pre>
<p>Whether or not you have preloaded an ISAPI extension, all
to define another nickname. Note that the nickname should not contain
percent signs (<code>%</code>).</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost_common</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost_common</pre>
</div>
<li>
Log message if an IPv6 client causes a request timeout:
- <pre class="prettyprint lang-config"> LogMessage "IPv6 timeout from %{REMOTE_ADDR}" "expr=-T %{IPV6} && %{REQUEST_STATUS} = 408"</pre>
+ <pre class="prettyprint lang-config">LogMessage "IPv6 timeout from %{REMOTE_ADDR}" "expr=-T %{IPV6} && %{REQUEST_STATUS} = 408"</pre>
Note the placing of the double quotes for the <code>expr=</code> argument.
</li>
<p>The basic module loading directive is</p>
-<pre class="prettyprint lang-config"> LoadModule lua_module modules/mod_lua.so</pre>
+<pre class="prettyprint lang-config">LoadModule lua_module modules/mod_lua.so</pre>
<p>
To utilize <code class="module"><a href="../mod/mod_dbd.html">mod_dbd</a></code>, specify <code>mod_dbd</code>
as the database type, or leave the field blank:
</p>
- <pre class="prettyprint lang-lua"> local database = r:dbacquire("mod_dbd")</pre>
+ <pre class="prettyprint lang-lua">local database = r:dbacquire("mod_dbd")</pre>
<h3><a name="database_object" id="database_object">Database object and contained functions</a></h3>
<p>Like <code class="directive">LuaHookTranslateName</code> but executed at the
map-to-storage phase of a request. Modules like mod_cache run at this phase,
which makes for an interesting example on what to do here:</p>
- <pre class="prettyprint lang-config"> LuaHookMapToStorage /path/to/lua/script.lua check_cache</pre>
+ <pre class="prettyprint lang-config">LuaHookMapToStorage /path/to/lua/script.lua check_cache</pre>
<pre class="prettyprint lang-lua">require"apache2"
cached_files = {}
This phase is where requests are assigned a content type and a handler, and thus can
be used to modify the type and handler based on input:
</p>
- <pre class="prettyprint lang-config"> LuaHookTypeChecker /path/to/lua/script.lua type_checker</pre>
+ <pre class="prettyprint lang-config">LuaHookTypeChecker /path/to/lua/script.lua type_checker</pre>
<pre class="prettyprint lang-lua"> function type_checker(r)
if r.uri:match("%.to_gif$") then -- match foo.png.to_gif
match groups into both the file path and the function name.
Be careful writing your regular expressions to avoid security
issues.</p>
- <div class="example"><h3>Examples:</h3><pre class="prettyprint lang-config"> LuaMapHandler /(\w+)/(\w+) /scripts/$1.lua handle_$2</pre>
+ <div class="example"><h3>Examples:</h3><pre class="prettyprint lang-config">LuaMapHandler /(\w+)/(\w+) /scripts/$1.lua handle_$2</pre>
</div>
<p>This would match uri's such as /photos/show?id=9
to the file /scripts/photos.lua and invoke the
handler function handle_show on the lua vm after
loading that file.</p>
-<pre class="prettyprint lang-config"> LuaMapHandler /bingo /scripts/wombat.lua</pre>
+<pre class="prettyprint lang-config">LuaMapHandler /bingo /scripts/wombat.lua</pre>
<p>This would invoke the "handle" function, which
is the default if no specific function name is
<p>La directive de base pour le chargement du module est</p>
-<pre class="prettyprint lang-config"> LoadModule lua_module modules/mod_lua.so</pre>
+<pre class="prettyprint lang-config">LoadModule lua_module modules/mod_lua.so</pre>
<p>
<code>mod_dbd</code> comme type de base de données, ou laissez le champ
vide :
</p>
- <pre class="prettyprint lang-lua"> local database = r:dbacquire("mod_dbd")</pre>
+ <pre class="prettyprint lang-lua">local database = r:dbacquire("mod_dbd")</pre>
<h3><a name="database_object" id="database_object">L'objet database et ses méthodes</a></h3>
phase map-to-storage du traitement de la requête. Les modules comme
mod_cache agissent pendant cette phase, ce qui permet de présenter
un exemple intéressant de ce que l'on peut faire ici :</p>
- <pre class="prettyprint lang-config"> LuaHookMapToStorage /path/to/lua/script.lua check_cache</pre>
+ <pre class="prettyprint lang-config">LuaHookMapToStorage /path/to/lua/script.lua check_cache</pre>
<pre class="prettyprint lang-lua">require"apache2"
cached_files = {}
d'interpolation dans le chemin du fichier et le nom de la fonction.
Prenez garde aux problèmes de sécurité en écrivant vos expressions
rationnelles.</p>
- <div class="example"><h3>Exemples :</h3><pre class="prettyprint lang-config"> LuaMapHandler /(\w+)/(\w+) /scripts/$1.lua handle_$2</pre>
+ <div class="example"><h3>Exemples :</h3><pre class="prettyprint lang-config">LuaMapHandler /(\w+)/(\w+) /scripts/$1.lua handle_$2</pre>
</div>
<p>Cette directive va faire correspondre des uri comme
/photos/show?id=9 au fichier /scripts/photos.lua, et invoquera la
fonction de gestionnaire handle_show au niveau de la vm lua
après chargement de ce fichier.</p>
-<pre class="prettyprint lang-config"> LuaMapHandler /bingo /scripts/wombat.lua</pre>
+<pre class="prettyprint lang-config">LuaMapHandler /bingo /scripts/wombat.lua</pre>
<p>Cette directive invoquera la fonction "handle" qui est la
valeur par défaut si aucun nom de fonction spécifique n'est
activate CGI scripts with the file extension <code>.cgi</code>, you
might use:</p>
- <pre class="prettyprint lang-config"> AddHandler cgi-script .cgi</pre>
+ <pre class="prettyprint lang-config">AddHandler cgi-script .cgi</pre>
<p>Once that has been put into your httpd.conf file, any file containing
<code>.shtml</code> files for server-side includes and will then
compress the output using <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code>.</p>
- <pre class="prettyprint lang-config"> AddOutputFilter INCLUDES;DEFLATE shtml</pre>
+ <pre class="prettyprint lang-config">AddOutputFilter INCLUDES;DEFLATE shtml</pre>
<p>If more than one filter is specified, they must be separated
<code class="directive"><a href="#typesconfig">TypesConfig</a></code> file.
</div>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> AddType image/gif .gif</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">AddType image/gif .gif</pre>
</div>
<p>Or, to specify multiple file extensions in one directive:</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> AddType image/jpeg jpeg jpg jpe</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">AddType image/jpeg jpeg jpg jpe</pre>
</div>
<p>The <var>extension</var> argument is case-insensitive and can
can be achieved by qualifying a <var>media-type</var> with
<code>qs</code>:</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> AddType application/rss+xml;qs=0.8 .xml</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">AddType application/rss+xml;qs=0.8 .xml</pre>
</div>
<p>This is useful in situations, <em>e.g.</em> when a client
by <code class="directive"><a href="#addlanguage">AddLanguage</a></code>, then no
Content-Language header field will be generated.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> DefaultLanguage en</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">DefaultLanguage en</pre>
</div>
<h3>See also</h3>
<p>This directive is recommended when you have a virtual filesystem.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> ModMimeUsePathInfo On</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">ModMimeUsePathInfo On</pre>
</div>
<p>If you have a request for <code>/index.php/foo.shtml</code>
and filters to participate in Multviews, but will exclude unknown
files:</p>
- <pre class="prettyprint lang-config"> MultiviewsMatch Handlers Filters</pre>
+ <pre class="prettyprint lang-config">MultiviewsMatch Handlers Filters</pre>
<p><code class="directive">MultiviewsMatch</code> is not allowed in a
<p>The <var>extension</var> argument is case-insensitive and can
be specified with or without a leading dot.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> RemoveCharset .html .shtml</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">RemoveCharset .html .shtml</pre>
</div>
</div>
associations inherited from parent directories or the server
config files. An example of its use might be:</p>
- <div class="example"><h3>/foo/.htaccess:</h3><pre class="prettyprint lang-config"> AddHandler server-parsed .html</pre>
+ <div class="example"><h3>/foo/.htaccess:</h3><pre class="prettyprint lang-config">AddHandler server-parsed .html</pre>
</div>
- <div class="example"><h3>/foo/bar/.htaccess:</h3><pre class="prettyprint lang-config"> RemoveHandler .html</pre>
+ <div class="example"><h3>/foo/bar/.htaccess:</h3><pre class="prettyprint lang-config">RemoveHandler .html</pre>
</div>
<p>This has the effect of returning <code>.html</code> files in
<p>The <var>extension</var> argument is case-insensitive and can
be specified with or without a leading dot.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> RemoveOutputFilter shtml</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">RemoveOutputFilter shtml</pre>
</div>
<h3>See also</h3>
directories or the server config files. An example of its use
might be:</p>
- <div class="example"><h3>/foo/.htaccess:</h3><pre class="prettyprint lang-config"> RemoveType .cgi</pre>
+ <div class="example"><h3>/foo/.htaccess:</h3><pre class="prettyprint lang-config">RemoveType .cgi</pre>
</div>
<p>This will remove any special handling of <code>.cgi</code>
used, in which case the more specific setting overrides the main
server's file.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> MimeMagicFile conf/magic</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">MimeMagicFile conf/magic</pre>
</div>
</div>
and the <code>.var</code> file should be associated with the
<code>type-map</code> handler with an <code class="directive"><a href="../mod/mod_mime.html#addhandler">AddHandler</a></code> directive:</p>
- <pre class="prettyprint lang-config"> AddHandler type-map .var</pre>
+ <pre class="prettyprint lang-config">AddHandler type-map .var</pre>
<p>A request for <code>document.html.var</code> in this directory will
express a preference, when handling a Multiviews request. The list
of <var>MIME-lang</var> are in order of decreasing preference.</p>
- <pre class="prettyprint lang-config"> LanguagePriority en fr de</pre>
+ <pre class="prettyprint lang-config">LanguagePriority en fr de</pre>
<p>For a request for <code>foo.html</code>, where
et le fichier <code>.var</code> doit être associé au gestionnaire
<code>type-map</code> via une directive <code class="directive"><a href="../mod/mod_mime.html#addhandler">AddHandler</a></code> :</p>
- <pre class="prettyprint lang-config"> AddHandler type-map .var</pre>
+ <pre class="prettyprint lang-config">AddHandler type-map .var</pre>
<p>A l'arrivée d'une requête pour la ressource
<var>langages-MIME</var> dans un ordre de préférences
décroissantes.</p>
- <pre class="prettyprint lang-config"> LanguagePriority en fr de</pre>
+ <pre class="prettyprint lang-config">LanguagePriority en fr de</pre>
<p>Dans le cas d'une requête pour <code>foo.html</code>, si
<code class="directive"><a href="#proxypassmatch">ProxyPassMatch</a></code> when used
for a reverse proxy:</p>
- <pre class="prettyprint lang-config"> ProxyPass /example http://backend.example.com connectiontimeout=5 timeout=30</pre>
+ <pre class="prettyprint lang-config">ProxyPass /example http://backend.example.com connectiontimeout=5 timeout=30</pre>
<p>This will create a worker associated with the origin server URL
values. When used in a forward proxy, workers are usually defined
via the <code class="directive"><a href="#proxyset">ProxySet</a></code> directive:</p>
- <pre class="prettyprint lang-config"> ProxySet http://backend.example.com connectiontimeout=5 timeout=30</pre>
+ <pre class="prettyprint lang-config">ProxySet http://backend.example.com connectiontimeout=5 timeout=30</pre>
<p>or alternatively using <code class="directive"><a href="#proxy">Proxy</a></code>
<p>Note that the DNS lookups may slow down the startup time of the
server.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> ProxyBlock news.example.com auctions.example.com friends.example.com</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">ProxyBlock news.example.com auctions.example.com friends.example.com</pre>
</div>
<p>Note that <code>example</code> would also be sufficient to match any
<p>Note also that</p>
- <pre class="prettyprint lang-config"> ProxyBlock *</pre>
+ <pre class="prettyprint lang-config">ProxyBlock *</pre>
<p>blocks connections to all sites.</p>
<code>Max-Forwards</code> header supplied with the request. This may
be set to prevent infinite proxy loops, or a DoS attack.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> ProxyMaxForwards 15</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">ProxyMaxForwards 15</pre>
</div>
<p>Note that setting <code class="directive">ProxyMaxForwards</code> is a
the below syntax is that it allows for dynamic control via the
<a href="mod_proxy_balancer.html#balancer_manager">Balancer Manager</a> interface:</p>
- <pre class="prettyprint lang-config"> ProxyPass /mirror/foo/ http://backend.example.com/</pre>
+ <pre class="prettyprint lang-config">ProxyPass /mirror/foo/ http://backend.example.com/</pre>
<div class="warning">
among all child processes, except when only one child process is allowed
by configuration or MPM design.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> ProxyPass /example http://backend.example.com max=20 ttl=120 retry=300</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">ProxyPass /example http://backend.example.com max=20 ttl=120 retry=300</pre>
</div>
<table class="bordered"><tr><th>BalancerMember parameters</th></tr></table>
<p>Suppose the local server has address <code>http://example.com/</code>;
then</p>
- <pre class="prettyprint lang-config"> ProxyPassMatch ^(/.*\.gif)$ http://backend.example.com$1</pre>
+ <pre class="prettyprint lang-config">ProxyPassMatch ^(/.*\.gif)$ http://backend.example.com$1</pre>
<p>will cause a local request for
<p>The URL argument must be parsable as a URL <em>before</em> regexp
substitutions (as well as after). This limits the matches you can use.
For instance, if we had used</p>
- <pre class="prettyprint lang-config"> ProxyPassMatch ^(/.*\.gif)$ http://backend.example.com:8000$1</pre>
+ <pre class="prettyprint lang-config">ProxyPassMatch ^(/.*\.gif)$ http://backend.example.com:8000$1</pre>
<p>in our previous example, it would fail with a syntax error
at server startup. This is a bug (PR 46665 in the ASF bugzilla),
and the workaround is to reformulate the match:</p>
- <pre class="prettyprint lang-config"> ProxyPassMatch ^/(.*\.gif)$ http://backend.example.com:8000/$1</pre>
+ <pre class="prettyprint lang-config">ProxyPassMatch ^/(.*\.gif)$ http://backend.example.com:8000/$1</pre>
</div>
<p>The <code>!</code> directive is useful in situations where you don't want
In the example given with
<code class="directive"><a href="#proxypassreverse">ProxyPassReverse</a></code>, the directive:
</p>
- <pre class="prettyprint lang-config"> ProxyPassReverseCookiePath / /mirror/foo/</pre>
+ <pre class="prettyprint lang-config">ProxyPassReverseCookiePath / /mirror/foo/</pre>
<p>
will rewrite a cookie with backend path <code>/</code> (or
to <code>0</code> to indicate that the system's default buffer size should
be used.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> ProxyReceiveBufferSize 2048</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">ProxyReceiveBufferSize 2048</pre>
</div>
</div>
</Proxy></pre>
- <pre class="prettyprint lang-config"> ProxySet balancer://foo lbmethod=bytraffic timeout=15</pre>
+ <pre class="prettyprint lang-config">ProxySet balancer://foo lbmethod=bytraffic timeout=15</pre>
- <pre class="prettyprint lang-config"> ProxySet ajp://backend:7001 timeout=15</pre>
+ <pre class="prettyprint lang-config">ProxySet ajp://backend:7001 timeout=15</pre>
<div class="warning"><h3>Warning</h3>
Ils sont en général définis via les directives <code class="directive"><a href="#proxypass">ProxyPass</a></code> ou <code class="directive"><a href="#proxypassmatch">ProxyPassMatch</a></code> lorsqu'on les
utilise dans le cadre d'un mandataire inverse :</p>
- <div class="example"><pre class="prettyprint lang-config"> ProxyPass /example http://backend.example.com connectiontimeout=5 timeout=30</pre>
+ <div class="example"><pre class="prettyprint lang-config">ProxyPass /example http://backend.example.com connectiontimeout=5 timeout=30</pre>
</div>
d'un mandataire direct, les workers sont en général définis via la
directive <code class="directive"><a href="#proxyset">ProxySet</a></code>,</p>
- <div class="example"><pre class="prettyprint lang-config"> ProxySet http://backend.example.com connectiontimeout=5 timeout=30</pre>
+ <div class="example"><pre class="prettyprint lang-config">ProxySet http://backend.example.com connectiontimeout=5 timeout=30</pre>
</div>
<p>Notez que les recherches DNS peuvent ralentir le processus de
démarrage du serveur.</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> ProxyBlock news.example.com auctions.example.com friends.example.com</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">ProxyBlock news.example.com auctions.example.com friends.example.com</pre>
</div>
<p>Notez qu'<code>example</code> suffirait aussi pour atteindre
<p>Notez aussi que</p>
- <pre class="prettyprint lang-config"> ProxyBlock *</pre>
+ <pre class="prettyprint lang-config">ProxyBlock *</pre>
<p>bloque les connexions vers tous les sites.</p>
contre les boucles infinies de mandataires ou contre les attaques de
type déni de service.</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> ProxyMaxForwards 15</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">ProxyMaxForwards 15</pre>
</div>
<p>Notez que la définition de la directive
présente en très grand nombre. Elle possède l'avantage de
permettre un contrôle dynamique via l'interface <a href="mod_proxy_balancer.html#balancer_manager">Balancer Manager</a> :</p>
- <pre class="prettyprint lang-config"> ProxyPass /miroir/foo/ http://backend.example.com/</pre>
+ <pre class="prettyprint lang-config">ProxyPass /miroir/foo/ http://backend.example.com/</pre>
<div class="warning">
enfants, sauf si un seul processus enfant est autorisé par la
configuration ou la conception du module multi-processus (MPM).</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> ProxyPass /example http://backend.example.com max=20 ttl=120 retry=300</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">ProxyPass /example http://backend.example.com max=20 ttl=120 retry=300</pre>
</div>
<table class="bordered"><tr><th>Paramètres de BalancerMember</th></tr></table>
<p>Supposons que le serveur local a pour adresse
<code>http://example.com/</code> ; alors</p>
- <pre class="prettyprint lang-config"> ProxyPassMatch ^(/.*\.gif)$ http://backend.example.com$1</pre>
+ <pre class="prettyprint lang-config">ProxyPassMatch ^(/.*\.gif)$ http://backend.example.com$1</pre>
<p>va provoquer la conversion interne de la requête locale
<em>avant</em> les substitutions d'expressions rationnelles (et
doit aussi l'être après). Ceci limite les correspondances que vous
pouvez utiliser. Par exemple, si l'on avait utilisé</p>
- <pre class="prettyprint lang-config"> ProxyPassMatch ^(/.*\.gif)$ http://backend.example.com:8000$1</pre>
+ <pre class="prettyprint lang-config">ProxyPassMatch ^(/.*\.gif)$ http://backend.example.com:8000$1</pre>
<p>dans l'exemple précédent, nous aurions provoqué une erreur de
syntaxe au démarrage du serveur. C'est une bogue (PR 46665 dans
ASF bugzilla), et il est possible de la contourner en reformulant
la correspondance :</p>
- <pre class="prettyprint lang-config"> ProxyPassMatch ^/(.*\.gif)$ http://backend.example.com:8000/$1</pre>
+ <pre class="prettyprint lang-config">ProxyPassMatch ^/(.*\.gif)$ http://backend.example.com:8000/$1</pre>
</div>
</p><p>
Dans l'exemple fourni avec la directive <code class="directive"><a href="#proxypassreverse">ProxyPassReverse</a></code>, la directive :
</p>
- <pre class="prettyprint lang-config"> ProxyPassReverseCookiePath / /mirror/foo/</pre>
+ <pre class="prettyprint lang-config">ProxyPassReverseCookiePath / /mirror/foo/</pre>
<p>
va réécrire un cookie possédant un chemin d'arrière-plan <code>/</code>
<code>0</code> pour indiquer que la taille de tampon par défaut du
système doit être utilisée.</p>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> ProxyReceiveBufferSize 2048</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">ProxyReceiveBufferSize 2048</pre>
</div>
</div>
</Proxy></pre>
- <pre class="prettyprint lang-config"> ProxySet balancer://foo lbmethod=bytraffic timeout=15</pre>
+ <pre class="prettyprint lang-config">ProxySet balancer://foo lbmethod=bytraffic timeout=15</pre>
- <pre class="prettyprint lang-config"> ProxySet ajp://backend:7001 timeout=15</pre>
+ <pre class="prettyprint lang-config">ProxySet ajp://backend:7001 timeout=15</pre>
<div class="warning"><h3>Avertissement</h3>
(e.g. Apache Tomcat) using the AJP13 protocol. The usage is similar to
an HTTP reverse proxy, but uses the <code>ajp://</code> prefix:</p>
- <div class="example"><h3>Simple Reverse Proxy</h3><pre class="prettyprint lang-config"> ProxyPass /app ajp://backend.example.com:8009/app</pre>
+ <div class="example"><h3>Simple Reverse Proxy</h3><pre class="prettyprint lang-config">ProxyPass /app ajp://backend.example.com:8009/app</pre>
</div>
<p>Balancers may also be used:</p>
<p>Remember, in order to make the following examples work, you have to
enable <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> and <code class="module"><a href="../mod/mod_proxy_fcgi.html">mod_proxy_fcgi</a></code>.</p>
- <div class="example"><h3>Single application instance</h3><pre class="prettyprint lang-config"> ProxyPass /myapp/ fcgi://localhost:4000/</pre>
+ <div class="example"><h3>Single application instance</h3><pre class="prettyprint lang-config">ProxyPass /myapp/ fcgi://localhost:4000/</pre>
</div>
<p>This application should be able to handle multiple concurrent
reuse on the <code class="directive">ProxyPass</code> directive, as shown in
the following example:</p>
- <div class="example"><h3>Single application instance, no connection reuse</h3><pre class="prettyprint lang-config"> ProxyPass /myapp/ fcgi://localhost:4000/ disablereuse=on</pre>
+ <div class="example"><h3>Single application instance, no connection reuse</h3><pre class="prettyprint lang-config">ProxyPass /myapp/ fcgi://localhost:4000/ disablereuse=on</pre>
</div>
<p>The balanced gateway needs <code class="module"><a href="../mod/mod_proxy_balancer.html">mod_proxy_balancer</a></code> and
<p>Remember, in order to make the following examples work, you have to
enable <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> and <code class="module"><a href="../mod/mod_proxy_scgi.html">mod_proxy_scgi</a></code>.</p>
- <div class="example"><h3>Simple gateway</h3><pre class="prettyprint lang-config"> ProxyPass /scgi-bin/ scgi://localhost:4000/</pre>
+ <div class="example"><h3>Simple gateway</h3><pre class="prettyprint lang-config">ProxyPass /scgi-bin/ scgi://localhost:4000/</pre>
</div>
<p>The balanced gateway needs <code class="module"><a href="../mod/mod_proxy_balancer.html">mod_proxy_balancer</a></code> and
<code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code> in this regard, except that you can turn off the
feature.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> ProxySCGIInternalRedirect Off</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">ProxySCGIInternalRedirect Off</pre>
</div>
</div>
other directives are used, <code class="module"><a href="../mod/mod_remoteip.html">mod_remoteip</a></code> will trust all
hosts presenting a <code class="directive">RemoteIPHeader</code> IP value.</p>
- <div class="example"><h3>Internal (Load Balancer) Example</h3><pre class="prettyprint lang-config"> RemoteIPHeader X-Client-IP</pre>
+ <div class="example"><h3>Internal (Load Balancer) Example</h3><pre class="prettyprint lang-config">RemoteIPHeader X-Client-IP</pre>
</div>
- <div class="example"><h3>Proxy Example</h3><pre class="prettyprint lang-config"> RemoteIPHeader X-Forwarded-For</pre>
+ <div class="example"><h3>Proxy Example</h3><pre class="prettyprint lang-config">RemoteIPHeader X-Forwarded-For</pre>
</div>
</div>
<code class="directive">RemoteIPHeader</code> comme hôte de confiance.</p>
<div class="example"><h3>Exemple à usage interne (répartiteur de
- charge)</h3><pre class="prettyprint lang-config"> RemoteIPHeader X-Client-IP</pre>
+ charge)</h3><pre class="prettyprint lang-config">RemoteIPHeader X-Client-IP</pre>
</div>
- <div class="example"><h3>Exemple dans le cas d'un mandataire</h3><pre class="prettyprint lang-config"> RemoteIPHeader X-Forwarded-For</pre>
+ <div class="example"><h3>Exemple dans le cas d'un mandataire</h3><pre class="prettyprint lang-config">RemoteIPHeader X-Forwarded-For</pre>
</div>
</div>
Allow 10 seconds to receive the request including the headers and
30 seconds for receiving the request body:
- <pre class="prettyprint lang-config"> RequestReadTimeout header=10 body=30</pre>
+ <pre class="prettyprint lang-config">RequestReadTimeout header=10 body=30</pre>
</li>
the limit given indirectly by
<code class="directive"><a href="../mod/core.html#limitrequestbody">LimitRequestBody</a></code>):
- <pre class="prettyprint lang-config"> RequestReadTimeout body=10,MinRate=1000</pre>
+ <pre class="prettyprint lang-config">RequestReadTimeout body=10,MinRate=1000</pre>
</li>
500 bytes received. But do not allow more than 30 seconds for the
request including the headers:
- <pre class="prettyprint lang-config"> RequestReadTimeout header=10-30,MinRate=500</pre>
+ <pre class="prettyprint lang-config">RequestReadTimeout header=10-30,MinRate=500</pre>
</li>
If a common configuration is used for http and https virtual hosts, the
timeouts should not be set too low:
- <pre class="prettyprint lang-config"> RequestReadTimeout header=20-40,MinRate=500 body=20,MinRate=500</pre>
+ <pre class="prettyprint lang-config">RequestReadTimeout header=20-40,MinRate=500 body=20,MinRate=500</pre>
</li>
level higher than <code>trace2</code> only for debugging!
</div>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> LogLevel alert rewrite:trace3</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">LogLevel alert rewrite:trace3</pre>
</div>
<div class="note"><h3>RewriteLog</h3>
to block unwanted hotlinking.
</p>
- <pre class="prettyprint lang-config"> RewriteCond expr "! %{HTTP_REFERER} -strmatch '*://%{HTTP_HOST}/*'"<br />
+ <pre class="prettyprint lang-config">RewriteCond expr "! %{HTTP_REFERER} -strmatch '*://%{HTTP_HOST}/*'"<br />
RewriteRule ^/images - [F]</pre>
</li>
<p>For example, you might define a
<code class="directive">RewriteMap</code> as:</p>
- <pre class="prettyprint lang-config"> RewriteMap examplemap txt:/path/to/file/map.txt</pre>
+ <pre class="prettyprint lang-config">RewriteMap examplemap txt:/path/to/file/map.txt</pre>
<p>You would then be able to use this map in a
<code class="directive">RewriteRule</code> as follows:</p>
- <pre class="prettyprint lang-config"> RewriteRule ^/ex/(.*) ${examplemap:$1}</pre>
+ <pre class="prettyprint lang-config">RewriteRule ^/ex/(.*) ${examplemap:$1}</pre>
<p>The following combinations for <em>MapType</em> and
supérieur à <code>trace2</code> qu'à des fins de débogage !
</div>
- <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config"> LogLevel alert rewrite:trace3</pre>
+ <div class="example"><h3>Exemple</h3><pre class="prettyprint lang-config">LogLevel alert rewrite:trace3</pre>
</div>
<div class="note"><h3>RewriteLog</h3>
non désiré.
</p>
- <pre class="prettyprint lang-config"> RewriteCond expr "! %{HTTP_REFERER} -strmatch '*://%{HTTP_HOST}/*'"<br />
+ <pre class="prettyprint lang-config">RewriteCond expr "! %{HTTP_REFERER} -strmatch '*://%{HTTP_HOST}/*'"<br />
RewriteRule ^/images - [F]</pre>
</li>
<p>Par exemple, vous pouvez définir une directive
<code class="directive">RewriteMap</code> comme suit </p>
- <pre class="prettyprint lang-config"> RewriteMap map-exemple txt:/chemin/vers/fichier/map.txt</pre>
+ <pre class="prettyprint lang-config">RewriteMap map-exemple txt:/chemin/vers/fichier/map.txt</pre>
<p>Vous pourrez ensuite utiliser cette table dans une
directive <code class="directive">RewriteRule</code> comme suit :</p>
- <pre class="prettyprint lang-config"> RewriteRule ^/ex/(.*) ${map-exemple:$1}</pre>
+ <pre class="prettyprint lang-config">RewriteRule ^/ex/(.*) ${map-exemple:$1}</pre>
<p>Les combinaisons suivantes pour <em>type de correspondance</em>
<p>The <var>NSS</var> crypto driver requires some parameters for configuration,
which are specified as parameters with optional values after the driver name.</p>
- <div class="example"><h3>NSS without a certificate database</h3><pre class="prettyprint lang-config"> SessionCryptoDriver nss</pre>
+ <div class="example"><h3>NSS without a certificate database</h3><pre class="prettyprint lang-config">SessionCryptoDriver nss</pre>
</div>
- <div class="example"><h3>NSS with certificate database</h3><pre class="prettyprint lang-config"> SessionCryptoDriver nss dir=certs</pre>
+ <div class="example"><h3>NSS with certificate database</h3><pre class="prettyprint lang-config">SessionCryptoDriver nss dir=certs</pre>
</div>
- <div class="example"><h3>NSS with certificate database and parameters</h3><pre class="prettyprint lang-config"> SessionCryptoDriver nss dir=certs key3=key3.db cert7=cert7.db secmod=secmod</pre>
+ <div class="example"><h3>NSS with certificate database and parameters</h3><pre class="prettyprint lang-config">SessionCryptoDriver nss dir=certs key3=key3.db cert7=cert7.db secmod=secmod</pre>
</div>
- <div class="example"><h3>NSS with paths containing spaces</h3><pre class="prettyprint lang-config"> SessionCryptoDriver nss "dir=My Certs" key3=key3.db cert7=cert7.db secmod=secmod</pre>
+ <div class="example"><h3>NSS with paths containing spaces</h3><pre class="prettyprint lang-config">SessionCryptoDriver nss "dir=My Certs" key3=key3.db cert7=cert7.db secmod=secmod</pre>
</div>
<p>The <var>NSS</var> crypto driver might have already been
existing configuration will have taken affect. To avoid this
warning, use the noinit parameter as follows.</p>
- <div class="example"><h3>NSS with certificate database</h3><pre class="prettyprint lang-config"> SessionCryptoDriver nss noinit</pre>
+ <div class="example"><h3>NSS with certificate database</h3><pre class="prettyprint lang-config">SessionCryptoDriver nss noinit</pre>
</div>
<p>To prevent confusion, ensure that all modules requiring NSS are configured with
<p>The <var>openssl</var> crypto driver supports an optional parameter to specify
the engine to be used for encryption.</p>
- <div class="example"><h3>OpenSSL with engine support</h3><pre class="prettyprint lang-config"> SessionCryptoDriver openssl engine=name</pre>
+ <div class="example"><h3>OpenSSL with engine support</h3><pre class="prettyprint lang-config">SessionCryptoDriver openssl engine=name</pre>
</div>
<code>ap_expr</code>. These expressions will be evaluated at runtime,
and applied <em>env-variable</em> in the same fashion as <code class="directive">SetEnvIf</code>.</p>
-<pre class="prettyprint lang-config"> SetEnvIfExpr "tolower(req('X-Sendfile')) == 'd:\images\very_big.iso')" iso_delivered</pre>
+<pre class="prettyprint lang-config">SetEnvIfExpr "tolower(req('X-Sendfile')) == 'd:\images\very_big.iso')" iso_delivered</pre>
<p>This would set the environment variable <code>iso_delivered</code>
<p>A more useful example would be to set the variable rfc1918 if the
remote IP address is a private address according to RFC 1918:</p>
-<pre class="prettyprint lang-config"> SetEnvIfExpr "-R '10.0.0.0/8' || -R '172.16.0.0/12' || -R '192.168.0.0/16'" rfc1918</pre>
+<pre class="prettyprint lang-config">SetEnvIfExpr "-R '10.0.0.0/8' || -R '172.16.0.0/12' || -R '192.168.0.0/16'" rfc1918</pre>
<h3>See also</h3>
the <code class="directive"><a href="#setenvif">SetEnvIf</a></code> directive,
and differs only in that the regular expression matching is
performed in a case-insensitive manner. For example:</p>
-<pre class="prettyprint lang-config"> SetEnvIfNoCase Host Example\.Org site=example</pre>
+<pre class="prettyprint lang-config">SetEnvIfNoCase Host Example\.Org site=example</pre>
<p>This will cause the <code>site</code> environment variable
d'environnement <em>env-variable</em> de la même manière que la
directive <code class="directive">SetEnvIf</code>.</p>
-<pre class="prettyprint lang-config"> SetEnvIfExpr "tolower(req('X-Sendfile')) == 'd:\images\very_big.iso')" iso_delivered</pre>
+<pre class="prettyprint lang-config">SetEnvIfExpr "tolower(req('X-Sendfile')) == 'd:\images\very_big.iso')" iso_delivered</pre>
<p>Dans cet exemple, la variable d'environnement
l'adresse IP distante est une adresse privée au sens de la RFC 1918
:</p>
-<pre class="prettyprint lang-config"> SetEnvIfExpr "-R '10.0.0.0/8' || -R '172.16.0.0/12' || -R '192.168.0.0/16'" rfc1918</pre>
+<pre class="prettyprint lang-config">SetEnvIfExpr "-R '10.0.0.0/8' || -R '172.16.0.0/12' || -R '192.168.0.0/16'" rfc1918</pre>
<h3>Voir aussi</h3>
d'un point de vue sémantique à la directive <code class="directive"><a href="#setenvif">SetEnvIf</a></code>, et ne s'en distingue que
par le fait que la comparaison des expressions rationnelles est
effectuée sans tenir compte de la casse. Par exemple :</p>
-<pre class="prettyprint lang-config"> SetEnvIfNoCase Host Example\.Org site=apache</pre>
+<pre class="prettyprint lang-config">SetEnvIfNoCase Host Example\.Org site=apache</pre>
<p>Cette ligne va définir la variable d'environnement
<code>module</code> in the file, and is listed as the <a href="module-dict.html#ModuleIdentifier">Module Identifier</a>
in the module documentation. Example:</p>
- <pre class="prettyprint lang-config"> LoadModule status_module modules/mod_status.so</pre>
+ <pre class="prettyprint lang-config">LoadModule status_module modules/mod_status.so</pre>
<p>loads the named module from the modules subdirectory of the
<code>module</code> dans le fichier, et est référencé comme <a href="module-dict.html#ModuleIdentifier">Identificateur de
module</a> dans la documentation des modules. Exemple :</p>
- <pre class="prettyprint lang-config"> LoadModule status_module modules/mod_status.so</pre>
+ <pre class="prettyprint lang-config">LoadModule status_module modules/mod_status.so</pre>
<p>charge le module spécifié depuis le sous-répertoire des modules
encrypted with SSL. This is similar to the
<code class="directive">SSLRequireSSL</code> directive.</p>
- <pre class="prettyprint lang-config"> Require ssl</pre>
+ <pre class="prettyprint lang-config">Require ssl</pre>
<p>The following example grants access if the user is authenticated
either with a client certificate or by username and password.</p>
- <pre class="prettyprint lang-config"> Require ssl-verify-client<br />
+ <pre class="prettyprint lang-config">Require ssl-verify-client<br />
Require valid-user</pre>
to specify a user and group for CGI programs to run as. Non-CGI
requests are still processed with the user specified in the <code class="directive"><a href="../mod/mod_unixd.html#user">User</a></code> directive.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> SuexecUserGroup nobody nogroup</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">SuexecUserGroup nobody nogroup</pre>
</div>
<p>In Apache httpd 2.3.9 and later, startup will fail if this
<dd>Refers to a group by its number.</dd>
</dl>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> Group www-group</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">Group www-group</pre>
</div>
<p>It is recommended that you set up a new group specifically for
<p>To allow most users to have <code>UserDir</code> directories, but
deny this to a few, use the following:</p>
- <pre class="prettyprint lang-config"> UserDir disabled user4 user5 user6</pre>
+ <pre class="prettyprint lang-config">UserDir disabled user4 user5 user6</pre>
<p>It is also possible to specify alternative user directories.
If you use a command like:</p>
- <pre class="prettyprint lang-config"> UserDir public_html /usr/web http://www.example.com/</pre>
+ <pre class="prettyprint lang-config">UserDir public_html /usr/web http://www.example.com/</pre>
<p>With a request for
level domain (for example <code>.example.co.uk</code>).
</div>
- <pre class="prettyprint lang-config"> CookieDomain .example.com</pre>
+ <pre class="prettyprint lang-config">CookieDomain .example.com</pre>
</div>
<p>If this directive is not used, cookies last only for the
current browser session.</p>
- <pre class="prettyprint lang-config"> CookieExpires "3 weeks"</pre>
+ <pre class="prettyprint lang-config">CookieExpires "3 weeks"</pre>
</div>
unpredictable if you use a name containing unusual characters.
Valid characters include A-Z, a-z, 0-9, "_", and "-".</p>
- <pre class="prettyprint lang-config"> CookieName clicktrack</pre>
+ <pre class="prettyprint lang-config">CookieName clicktrack</pre>
</div>
three of these formats, with <code>Cookie2</code> being the
preferred format.</p>
- <pre class="prettyprint lang-config"> CookieStyle Cookie2</pre>
+ <pre class="prettyprint lang-config">CookieStyle Cookie2</pre>
</div>
<code class="module"><a href="../mod/mod_usertrack.html">mod_usertrack</a></code> will <strong>not</strong>
activate cookies. </p>
- <pre class="prettyprint lang-config"> CookieTracking on</pre>
+ <pre class="prettyprint lang-config">CookieTracking on</pre>
<p>A more even spread of files can be achieved by hashing from the
end of the name, for example: </p>
-<pre class="prettyprint lang-config"> VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.-1/%2.-2/%2.-3/%2</pre>
+<pre class="prettyprint lang-config">VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.-1/%2.-2/%2.-3/%2</pre>
<p>The example request would come from
<p>Alternatively you might use: </p>
-<pre class="prettyprint lang-config"> VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.1/%2.2/%2.3/%2.4+</pre>
+<pre class="prettyprint lang-config">VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.1/%2.2/%2.3/%2.4+</pre>
<p>The example request would come from
to the hostname. As such, one can make a configuration that will direct all first, second
or third level subdomains to the same directory:
</p>
-<pre class="prettyprint lang-config"> VirtualDocumentRoot "/usr/local/apache/vhosts/%-2.0.%-1.0"</pre>
+<pre class="prettyprint lang-config">VirtualDocumentRoot "/usr/local/apache/vhosts/%-2.0.%-1.0"</pre>
<p>
In the example above, both <code>www.example.com</code> as well as <code>www.sub.example.com</code>
a <code>%</code> directive, you can work around the problem in
the following way:</p>
-<pre class="prettyprint lang-config"> VirtualDocumentRoot /usr/local/apache/vhosts/%2.0.%3.0</pre>
+<pre class="prettyprint lang-config">VirtualDocumentRoot /usr/local/apache/vhosts/%2.0.%3.0</pre>
<p>A request for
<p>IPv6 addresses must be surrounded in square brackets, as in the
following example:</p>
- <pre class="prettyprint lang-config"> Listen [2001:db8::a00:20ff:fea7:ccea]:80</pre>
+ <pre class="prettyprint lang-config">Listen [2001:db8::a00:20ff:fea7:ccea]:80</pre>
<p>The optional <var>protocol</var> argument is not required for most
<p>You only need to set the protocol if you are running on non-standard
ports. For example, running an <code>https</code> site on port 8443:</p>
- <pre class="prettyprint lang-config"> Listen 192.170.2.1:8443 https</pre>
+ <pre class="prettyprint lang-config">Listen 192.170.2.1:8443 https</pre>
<div class="note"><h3>Error condition</h3>
filename is not absolute then it is assumed to be relative to the
<code class="directive"><a href="../mod/core.html#defaultruntimedir">DefaultRuntimeDir</a></code>.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> PidFile /var/run/apache.pid</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">PidFile /var/run/apache.pid</pre>
</div>
<p>It is often useful to be able to send the server a signal,
will be relative to the value of
<code class="directive"><a href="../mod/core.html#defaultruntimedir">DefaultRuntimeDir</a></code>.</p>
- <div class="example"><h3>Example</h3><pre class="prettyprint lang-config"> ScoreBoardFile /var/run/apache_runtime_status</pre>
+ <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">ScoreBoardFile /var/run/apache_runtime_status</pre>
</div>
<p>File-based shared memory is useful for third-party applications
module, use the following (in addition to the status-activating
directives in <code>access.conf</code>):</p>
- <pre class="prettyprint lang-config"> LoadModule status_module modules/mod_status.so</pre>
+ <pre class="prettyprint lang-config">LoadModule status_module modules/mod_status.so</pre>
<p>Information on <a href="../mod/mod_so.html#creating">creating
(Arcane and error prone procedures may work around the restriction
on mapped drive letters, but this is not recommended.)</p>
- <div class="example"><h3>Example DocumentRoot with UNC path</h3><pre class="prettyprint lang-config"> DocumentRoot //dochost/www/html/</pre>
+ <div class="example"><h3>Example DocumentRoot with UNC path</h3><pre class="prettyprint lang-config">DocumentRoot //dochost/www/html/</pre>
</div>
- <div class="example"><h3>Example DocumentRoot with IP address in UNC path</h3><pre class="prettyprint lang-config"> DocumentRoot //192.168.1.50/docs/</pre>
+ <div class="example"><h3>Example DocumentRoot with IP address in UNC path</h3><pre class="prettyprint lang-config">DocumentRoot //192.168.1.50/docs/</pre>
</div>
<div class="example"><h3>Example Alias and corresponding Directory with UNC path</h3><pre class="prettyprint lang-config">Alias /images/ //imagehost/www/images/
This should really be accomplished with Redirect or RedirectMatch
directives:
- <pre class="prettyprint lang-config"> RedirectMatch ^/(puppies|canines)/(.*) /dogs/$2</pre>
+ <pre class="prettyprint lang-config">RedirectMatch ^/(puppies|canines)/(.*) /dogs/$2</pre>
</dd>
</dl>
you must make sure to put the non-SSL port number on the NameVirtualHost
directive, e.g.</p>
- <pre class="prettyprint lang-config"> NameVirtualHost 192.168.1.1:80</pre>
+ <pre class="prettyprint lang-config">NameVirtualHost 192.168.1.1:80</pre>
<p>Other workaround solutions include: </p>
(sur le port 443). Mais dans ce cas, vous devez définir le numéro de port
non-SSL à l'aide de la directive NameVirtualHost dans ce style :</p>
- <pre class="prettyprint lang-config"> NameVirtualHost 192.168.1.1:80</pre>
+ <pre class="prettyprint lang-config">NameVirtualHost 192.168.1.1:80</pre>
<p>il existe d'autres solutions alternatives comme :</p>
only?</a></h3>
<p>The following enables only the strongest ciphers:</p>
- <pre class="prettyprint lang-config"> SSLCipherSuite HIGH:!aNULL:!MD5</pre>
+ <pre class="prettyprint lang-config">SSLCipherSuite HIGH:!aNULL:!MD5</pre>
<p>While with the following configuration you specify a preference
<p>Les directives suivantes ne permettent que les
chiffrements de plus haut niveau :</p>
- <pre class="prettyprint lang-config"> SSLCipherSuite HIGH:!aNULL:!MD5</pre>
+ <pre class="prettyprint lang-config">SSLCipherSuite HIGH:!aNULL:!MD5</pre>
<div class="example"><h3>2.2 configuration:</h3><pre class="prettyprint lang-config">Order deny,allow
Deny from all</pre>
</div>
- <div class="example"><h3>2.4 configuration:</h3><pre class="prettyprint lang-config"> Require all denied</pre>
+ <div class="example"><h3>2.4 configuration:</h3><pre class="prettyprint lang-config">Require all denied</pre>
</div>
<p>In this example, all requests are allowed.</p>
<div class="example"><h3>2.2 configuration:</h3><pre class="prettyprint lang-config">Order allow,deny
Allow from all</pre>
</div>
- <div class="example"><h3>2.4 configuration:</h3><pre class="prettyprint lang-config"> Require all granted</pre>
+ <div class="example"><h3>2.4 configuration:</h3><pre class="prettyprint lang-config">Require all granted</pre>
</div>
<p>In the following example, all hosts in the example.org domain
Deny from all
Allow from example.org</pre>
</div>
- <div class="example"><h3>2.4 configuration:</h3><pre class="prettyprint lang-config"> Require host example.org</pre>
+ <div class="example"><h3>2.4 configuration:</h3><pre class="prettyprint lang-config">Require host example.org</pre>
</div>
<div class="example"><h3>version 2.2 :</h3><pre class="prettyprint lang-config">Order deny,allow
Deny from all</pre>
</div>
- <div class="example"><h3>version 2.4 :</h3><pre class="prettyprint lang-config"> Require all denied</pre>
+ <div class="example"><h3>version 2.4 :</h3><pre class="prettyprint lang-config">Require all denied</pre>
</div>
<p>Dans cet exemple, toutes les requêtes sont acceptées :</p>
<div class="example"><h3>version 2.2 :</h3><pre class="prettyprint lang-config">Order allow,deny
Allow from all</pre>
</div>
- <div class="example"><h3>version 2.4 :</h3><pre class="prettyprint lang-config"> Require all granted</pre>
+ <div class="example"><h3>version 2.4 :</h3><pre class="prettyprint lang-config">Require all granted</pre>
</div>
<p>Dans l'exemple suivant, tous les hôtes du domaine example.org
Deny from all
Allow from example.org</pre>
</div>
- <div class="example"><h3>version 2.4 :</h3><pre class="prettyprint lang-config"> Require host example.org</pre>
+ <div class="example"><h3>version 2.4 :</h3><pre class="prettyprint lang-config">Require host example.org</pre>
</div>
expression</a> based matching and substitution. For
example,</p>
- <pre class="prettyprint lang-config"> ScriptAliasMatch ^/~([a-zA-Z0-9]+)/cgi-bin/(.+) /home/$1/cgi-bin/$2</pre>
+ <pre class="prettyprint lang-config">ScriptAliasMatch ^/~([a-zA-Z0-9]+)/cgi-bin/(.+) /home/$1/cgi-bin/$2</pre>
<p>will map a request to
<code>/home/user/public_html/file.html</code>, use the following
<code>AliasMatch</code> directive:</p>
- <pre class="prettyprint lang-config"> AliasMatch ^/upages/([a-zA-Z0-9]+)(/(.*))?$ /home/$1/public_html/$3</pre>
+ <pre class="prettyprint lang-config">AliasMatch ^/upages/([a-zA-Z0-9]+)(/(.*))?$ /home/$1/public_html/$3</pre>
</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
<div class="section">
to the new directory <code>/bar/</code>, you can instruct clients
to request the content at the new location as follows:</p>
- <pre class="prettyprint lang-config"> Redirect permanent /foo/ http://www.example.com/bar/</pre>
+ <pre class="prettyprint lang-config">Redirect permanent /foo/ http://www.example.com/bar/</pre>
<p>This will redirect any URL-Path starting in
for the site home page to a different site, but leave all other
requests alone, use the following configuration:</p>
- <pre class="prettyprint lang-config"> RedirectMatch permanent ^/$ http://www.example.com/startpage.html</pre>
+ <pre class="prettyprint lang-config">RedirectMatch permanent ^/$ http://www.example.com/startpage.html</pre>
<p>Alternatively, to temporarily redirect all pages on one site
to a particular page on another site, use the following:</p>
- <pre class="prettyprint lang-config"> RedirectMatch temp .* http://othersite.example.com/startpage.html</pre>
+ <pre class="prettyprint lang-config">RedirectMatch temp .* http://othersite.example.com/startpage.html</pre>
</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
<div class="section">
sur les <a class="glossarylink" href="./glossary.html#regex" title="voir glossaire">expressions rationnelles</a>.
Par exemple,</p>
-<pre class="prettyprint lang-config"> ScriptAliasMatch ^/~([a-zA-Z0-9]+)/cgi-bin/(.+) /home/$1/cgi-bin/$2</pre>
+<pre class="prettyprint lang-config">ScriptAliasMatch ^/~([a-zA-Z0-9]+)/cgi-bin/(.+) /home/$1/cgi-bin/$2</pre>
<p>fera correspondre une requête du style
<code>/home/user/public_html/file.html</code>, utilisez la directive
<code>AliasMatch</code> suivante :</p>
-<pre class="prettyprint lang-config"> AliasMatch ^/upages/([a-zA-Z0-9]+)(/(.*))?$ /home/$1/public_html/$3</pre>
+<pre class="prettyprint lang-config">AliasMatch ^/upages/([a-zA-Z0-9]+)(/(.*))?$ /home/$1/public_html/$3</pre>
</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
<div class="section">
nouveau répertoire <code>/bar/</code>, vous pouvez demander aux clients
de le requérir à sa nouvelle localisation comme suit :</p>
-<pre class="prettyprint lang-config"> Redirect permanent /foo/ http://www.example.com/bar/</pre>
+<pre class="prettyprint lang-config">Redirect permanent /foo/ http://www.example.com/bar/</pre>
<p>Ceci aura pour effet de rediriger tout chemin d'URL commençant par
laisser toutes les autres requêtes inchangées, utilisez la
configuration suivante :</p>
-<pre class="prettyprint lang-config"> RedirectMatch permanent ^/$ http://www.example.com/startpage.html</pre>
+<pre class="prettyprint lang-config">RedirectMatch permanent ^/$ http://www.example.com/startpage.html</pre>
<p>De même, pour rediriger temporairement toutes les pages d'un site
vers une page particulière d'un autre site, utilisez ce qui suit :</p>
-<pre class="prettyprint lang-config"> RedirectMatch temp .* http://othersite.example.com/startpage.html</pre>
+<pre class="prettyprint lang-config">RedirectMatch temp .* http://othersite.example.com/startpage.html</pre>
</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
<div class="section">
configuration file to select which IP address (or virtual host)
that daemon services. e.g.</p>
- <pre class="prettyprint lang-config"> Listen 192.0.2.100:80</pre>
+ <pre class="prettyprint lang-config">Listen 192.0.2.100:80</pre>
<p>It is recommended that you use an IP address instead of a
de configuration pour définir l'adresse IP (ou serveur virtuel)
que le processus résident doit gérer. Par exemple :</p>
- <pre class="prettyprint lang-config"> Listen 192.0.2.100:80</pre>
+ <pre class="prettyprint lang-config">Listen 192.0.2.100:80</pre>
<p>Il est recommandé d'utiliser une adresse IP plutôt qu'un nom
the listed names are other names which people can use to see that same
web site:</p>
- <pre class="prettyprint lang-config"> ServerAlias example.com *.example.com</pre>
+ <pre class="prettyprint lang-config">ServerAlias example.com *.example.com</pre>
<p>then requests for all hosts in the <code>example.com</code> domain will
indique aux utilisateurs les autres noms permis pour accéder au
même site Web :</p>
- <pre class="prettyprint lang-config"> ServerAlias example.com *.example.com</pre>
+ <pre class="prettyprint lang-config">ServerAlias example.com *.example.com</pre>
<p>ainsi, toutes les requêtes portant sur un domaine
projects / apache / commitdiff