sırasında sunucunun <a href="mod/module-dict.html#Status">temel</a> bir
modül kümesi içermesi sağlanır. Eğer sunucu <a href="dso.html">devingen
yüklenen</a> modülleri kullanmak üzere yapılandırılarak derlenirse modüller
- ayrı olarak derlenip gerektiği zaman <code class="directive"><a href="./mod/mod_so.html# loadmodule">
+ ayrı olarak derlenip gerektiği zaman <code class="directive"><a href="./mod/mod_so.html#loadmodule">
LoadModule</a></code> yönergesi kullanılarak yüklenebilir. Aksi takdirde,
ek modülleri yükleyebilmek veya kaldırabilmek için httpd’nin yeniden
derlenmesi gerekir. Yapılandırma yönergeleri belli bir modülün varlığına
<p>Starting with version 2.4, Apache is more strict about how HTTP
- headers are converted to environment variables in <code class="module"><a href="./mod/mod_cgi .html">mod_cgi
+ headers are converted to environment variables in <code class="module"><a href="./mod/mod_cgi.html">mod_cgi
</a></code> and other modules: Previously any invalid characters
in header names were simply translated to underscores. This allowed
for some potential cross-site-scripting attacks via header injection
Unusual Web Bugs</a>, slide 19/20).</p>
<p>If you have to support a client which sends broken headers and
- which can't be fixed, a simple workaround involving <code class="module"><a href="./mod/mod_setenvif .html">mod_setenvif
+ which can't be fixed, a simple workaround involving <code class="module"><a href="./mod/mod_setenvif.html">mod_setenvif
</a></code> and <code class="module"><a href="./mod/mod_header.html">mod_header</a></code> allows you to still accept
these headers:</p>
other than who they are. Something such as where they are
coming from.</p>
- <p>The authorization providers <code class="directive"><a href="../mod/mod_authz_host.html# all">
- all</a></code>, <code class="directive"><a href="../mod/mod_authz_host.html# env">
- env</a></code>, <code class="directive"><a href="../mod/mod_authz_host.html# host">
- host</a></code> and <code class="directive"><a href="../mod/mod_authz_host.html# ip">
+ <p>The authorization providers <code class="directive"><a href="../mod/mod_authz_host.html#all">
+ all</a></code>, <code class="directive"><a href="../mod/mod_authz_host.html#env">
+ env</a></code>, <code class="directive"><a href="../mod/mod_authz_host.html#host">
+ host</a></code> and <code class="directive"><a href="../mod/mod_authz_host.html#ip">
ip</a></code> let you allow or deny access based other host based
criteria such as host name or ip address of the machine requesting
a document.</p>
basé sur leur identité ; il peut dépendre, par exemple de leur
provenance.</p>
- <p>Les fournisseurs d'autorisation <code class="directive"><a href="../mod/mod_authz_host.html# all">
- all</a></code>, <code class="directive"><a href="../mod/mod_authz_host.html# env">
- env</a></code>, <code class="directive"><a href="../mod/mod_authz_host.html# host">
- host</a></code> et <code class="directive"><a href="../mod/mod_authz_host.html# ip">
+ <p>Les fournisseurs d'autorisation <code class="directive"><a href="../mod/mod_authz_host.html#all">
+ all</a></code>, <code class="directive"><a href="../mod/mod_authz_host.html#env">
+ env</a></code>, <code class="directive"><a href="../mod/mod_authz_host.html#host">
+ host</a></code> et <code class="directive"><a href="../mod/mod_authz_host.html#ip">
ip</a></code> vous permettent d'accorder ou refuser l'accès en
fonction de critères tels que le nom d'hôte ou l'adresse
IP de la machine qui effectue la requête.</p>
<a href="../mod/mod_authz_core.html#logic">Yetkilendirme
Taşıyıcıları</a> bölümüne bakınız.</p>
- <p>Öntanımlı olarak tüm <code class="directive"><a href="../mod/mod_authz_core.html# require">
+ <p>Öntanımlı olarak tüm <code class="directive"><a href="../mod/mod_authz_core.html#require">
Require</a></code> yönergeleri, <code class="directive"><a href="../mod/mod_authz_core.html#requireany"><RequireAny></a></code>
taşıyıcı yönergesinin içine konur. Başka bir deyişle eğer
belirtilen kimlik doğrulama yöntemlerinden herhangi biri başarılı
</pre>
- <p>In the example above <code class="directive"><a href="#allowoverride ">AllowOverride
+ <p>In the example above <code class="directive"><a href="#allowoverride">AllowOverride
</a></code> grants permission to the <code>AuthConfig</code>
directive grouping and <code class="directive">AllowOverrideList</code> grants
permission to only two directives from the <code>FileInfo</code> directive
</pre>
- <p>Yukarıdaki örnekte <code class="directive"><a href="#allowoverride ">AllowOverride
+ <p>Yukarıdaki örnekte <code class="directive"><a href="#allowoverride">AllowOverride
</a></code> yönergesi <code>AuthConfig</code> yönerge grubuna izin
verirken <code class="directive">AllowOverrideList</code> yönergesi
<code>FileInfo</code> yönerge grubundan yalnız iki yönergeye izin
<dd>まず <code class="directive"><a href="#allow">Allow</a></code>
ディレクティブが適用されます。どれにもマッチしなかった場合、この時点で
- リクエストは拒否されます。次に、全ての <code class="directive"><a href="# deny">
+ リクエストは拒否されます。次に、全ての <code class="directive"><a href="#deny">
Deny</a></code> ディレクティブが適用されます。どれか一つでもマッチした場合は、
リクエストは拒否されます。
最後に、 <code class="directive"><a href="#allow">Allow</a></code> にも <code class="directive"><a href="#deny">Deny</a></code> にもマッチしなかったリクエストは
<p><code><AuthnProviderAlias></code> and
<code></AuthnProviderAlias></code> are used to enclose a group of
authentication directives that can be referenced by the alias name
- using one of the directives <code class="directive"><a href="../mod/mod_auth_basic.html# authbasicprovider">
- AuthBasicProvider</a></code> or <code class="directive"><a href="../mod/mod_auth_digest.html# authdigestprovider">
+ using one of the directives <code class="directive"><a href="../mod/mod_auth_basic.html#authbasicprovider">
+ AuthBasicProvider</a></code> or <code class="directive"><a href="../mod/mod_auth_digest.html#authdigestprovider">
AuthDigestProvider</a></code>.</p>
authorization checks use comparisons.</p>
<p>This directive only has effect on the comparisons performed during
- nested group processing when <code class="directive"><a href="# authldapsearchasuser">
+ nested group processing when <code class="directive"><a href="#authldapsearchasuser">
AuthLDAPSearchAsUser</a></code> is also enabled.</p>
<p> This directive should only be used when your LDAP server doesn't
search.</p>
<p> If the verbatim username can't directly bind, but needs some
- cosmetic transformation, see <code class="directive"><a href="# authldapinitialbindpattern">
+ cosmetic transformation, see <code class="directive"><a href="#authldapinitialbindpattern">
AuthLDAPInitialBindPattern</a></code>.</p>
<p> This directive should only be used when your LDAP server doesn't
checks use searches.</p>
<p>This directive only has effect on the comparisons performed during
- nested group processing when <code class="directive"><a href="# authldapcompareasuser">
+ nested group processing when <code class="directive"><a href="#authldapcompareasuser">
AuthLDAPCompareAsUser</a></code> is also enabled.</p>
<p> This directive should only be used when your LDAP server doesn't
circumstances, an administrator is often forced to place independent reverse
proxy servers either behind or in front of the caching server to achieve this.</p>
- <p>To solve this problem the <code class="directive"><a href="#cachequickhandler ">CacheQuickHandler
+ <p>To solve this problem the <code class="directive"><a href="#cachequickhandler">CacheQuickHandler
</a></code> directive can be set to <strong>off</strong>, and the server will
process all phases normally handled by a non-cached request, including the
<strong>authentication and authorisation</strong> phases.</p>
işleme yönergelerinden sonra işleme sokulur. Eğer atadığınız ortam değişkeni,
bir <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> yönergesindeki
gibi erken işlem aşamalarına girdi sağlıyorsa, bu durumda ortam değişkenini
- <code class="directive"><a href="../mod/mod_setenvif.html# setenvif"> SetEnvIf</a></code> ile atamalısınız.</p>
+ <code class="directive"><a href="../mod/mod_setenvif.html#setenvif"> SetEnvIf</a></code> ile atamalısınız.</p>
</div>
<h2><a name="usingssltls" id="usingssltls">Utiliser SSL/TLS</a></h2>
<p>La possibilité de créer des connexions SSL et TLS avec un serveur
- LDAP est définie par les directives <code class="directive"><a href="# ldaptrustedglobalcert">
- LDAPTrustedGlobalCert</a></code>, <code class="directive"><a href="# ldaptrustedclientcert">
- LDAPTrustedClientCert</a></code> et <code class="directive"><a href="# ldaptrustedmode">
+ LDAP est définie par les directives <code class="directive"><a href="#ldaptrustedglobalcert">
+ LDAPTrustedGlobalCert</a></code>, <code class="directive"><a href="#ldaptrustedclientcert">
+ LDAPTrustedClientCert</a></code> et <code class="directive"><a href="#ldaptrustedmode">
LDAPTrustedMode</a></code>. Ces directives permettent de spécifier
l'autorité de certification (CA), les certificats clients éventuels,
ainsi que le type de chiffrement à utiliser pour la connexion (none,
<?xml version="1.0"?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.fr.xsl"?>
-<!-- English Revision: 1560082 -->
+<!-- English Revision: 1560082:1562174 (outdated) -->
<!-- French translation: Fabien Coelho -->
<!-- Updated by Lucien Gentis -->
<a href="../fr/mod/mod_proxy.html" title="Français"> fr </a> |
<a href="../ja/mod/mod_proxy.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a></p>
</div>
-<div class="outofdate">Cette traduction peut être périmée. Vérifiez la version
- anglaise pour les changements récents.</div>
<table class="module"><tr><th><a href="module-dict.html#Description">Description:</a></th><td>Serveur mandataire/passerelle multi-protocole</td></tr>
<tr><th><a href="module-dict.html#Status">Statut:</a></th><td>Extension</td></tr>
<tr><th><a href="module-dict.html#ModuleIdentifier">Identificateur de Module:</a></th><td>proxy_module</td></tr>
</pre>
+ <div class="note"><h3>Différences avec la section de configuration Location</h3>
+ <p>Une URL d'arrière-plan sera concernée par le conteneur Proxy si
+ elle commence par la <var>url-avec-jokers</var>, même si le
+ dernier segment de chemin de la directive ne correspond qu'à un
+ préfixe de segment dee chemin de l'URL d'arrière-plan. Par exemple, <Proxy
+ http://example.com/foo> correspondra entre autres aux URLs
+ http://example.com/foo, http://example.com/foo/bar, et
+ http://example.com/foobar. La correspondance de l'URL finale
+ diffère du comportement de la section <code class="directive"><a href="../mod/core.html#location"><Location></a></code> qui, pour le cas de cette note,
+ traitera le segment de chemin final comme s'il se terminait par un
+ slash.</p>
+ <p>Pour un contrôle plus fin de la correspondance des URL, voir la
+ directive <code class="directive"><ProxyMatch></code>.</p>
+ </div>
+
<h3>Voir aussi</h3>
<ul>
<strong>off</strong> lorsqu'on utilise la directive
<code class="directive">ProxyPass</code>.</div>
+ <p>Le support des sockets de style Unix est fourni ; il suffit pour
+ cela d'utiliser une URL cible préfixée par
+ <code>unix:/path/lis.sock|</code>. Par exemple, pour mandater HTTP
+ et cibler l'UDS /home/www/socket, vous devez utiliser
+ <code>unix:/home/www.socket|http://localhost/whatever/</code>.</p>
+
+ <div class="note"><strong>Note :</strong>Le chemin associé à l'URL
+ <code>unix:</code> tient compte de la directive
+ <code class="directive">DefaultRuntimeDir</code>.</div>
+
<p>Supposons que le serveur local a pour adresse
<code>http://example.com/</code> ; alors la ligne</p>
<variants>
<variant>en</variant>
- <variant outdated="yes">fr</variant>
+ <variant>fr</variant>
<variant outdated="yes">ja</variant>
</variants>
</metafile>
<p>Pour contrôler votre configuration, regardez tout d'abord si
l'abonnement est à base de cookie ou de codage d'URL. L'étape
suivante consiste à enregistrer certaines données dans le journal
- des accès en utilisant un <code class="directive"><a href="../mod/mod_log_config.html#format de journalisation">format
+ des accès en utilisant un <code class="directive"><a href="../mod/mod_log_config.html#format de journalisation">format
de journalisation</a></code> personnalisé. Les champs intéressants
sont les suivants :</p>
<dl>
</p>
<div class="warning"><h3>Security warning</h3>
<p>If this directive is enabled, all of the certificates in the file will be
-trusted as if they were also in <code class="directive"><a href="# sslproxycacertificatefile">
+trusted as if they were also in <code class="directive"><a href="#sslproxycacertificatefile">
SSLProxyCACertificateFile</a></code>.</p>
</div>
<div class="example"><h3>Example</h3><pre class="prettyprint lang-config">
<code class="directive"><a href="#threadsperchild">ThreadsPerChild</a></code>
settings require more than 16 server processes (default). Do not set
the value of this directive any higher than the number of server
- processes required by what you may want for <code class="directive"><a href="#maxrequestworkers
">MaxRequestWorkers </a></code> and <code class="directive"><a href="#threadsperchild">ThreadsPerChild</a></code>.</p>
+ processes required by what you may want for <code class="directive"><a href="#maxrequestworkers">MaxRequestWorkers </a></code> and <code class="directive"><a href="#threadsperchild">ThreadsPerChild</a></code>.</p>
<div class="note"><h3>Note</h3>
<p>There is a hard limit of <code>ServerLimit 20000</code> compiled
16 processus serveurs (valeur par défaut). N'affectez pas à la
directive <code class="directive"><a href="#serverlimit">ServerLimit</a></code> une
valeur supérieure au nombre de processus requis pour la définition
- des directives <code class="directive"><a href="#maxrequestworkers ">MaxRequestWorkers
+ des directives <code class="directive"><a href="#maxrequestworkers">MaxRequestWorkers
</a></code> et <code class="directive"><a href="#threadsperchild">ThreadsPerChild</a></code>.</p>
<div class="note"><h3>Note</h3>
<code class="directive"><a href="#threadsperchild">ThreadsPerChild</a></code>
の設定で 16 サーバプロセス (デフォルト)
以上必要になる場合にのみ使用してください。希望の
- <code class="directive"><a href="#maxclients ">MaxClients </a></code> と
+ <code class="directive"><a href="#maxclients">MaxClients </a></code> と
<code class="directive"><a href="#threadsperchild">ThreadsPerChild</a></code>
とくらべて、必要となるサーバプロセス数以上に大きな値を
設定することは避けてください。</p>
<code class="directive"><a href="../mod/mpm_common.html#maxrequestworkers">MaxRequestWorkers</a></code> directive.
The maximum number of active child processes is determined by
the <code class="directive"><a href="../mod/mpm_common.html#maxrequestworkers">MaxRequestWorkers</a></code>
- directive divided by the <code class="directive"><a href="../mod/mpm_common.html# threadsperchild">
+ directive divided by the <code class="directive"><a href="../mod/mpm_common.html#threadsperchild">
ThreadsPerChild</a></code> directive.</p>
<p>Two directives set hard limits on the number of active child
processes and the number of server threads in a child process,
and can only be changed by fully stopping the server and then
- starting it again. <code class="directive"><a href="../mod/mpm_common.html#serverlimit ">ServerLimit
+ starting it again. <code class="directive"><a href="../mod/mpm_common.html#serverlimit">ServerLimit
</a></code> is a hard limit on the number of active child
processes, and must be greater than or equal to the
<code class="directive"><a href="../mod/mpm_common.html#maxrequestworkers">MaxRequestWorkers</a></code>
- directive divided by the <code class="directive"><a href="../mod/mpm_common.html# threadsperchild">
+ directive divided by the <code class="directive"><a href="../mod/mpm_common.html#threadsperchild">
ThreadsPerChild</a></code> directive.
<code class="directive"><a href="../mod/mpm_common.html#threadlimit">ThreadLimit</a></code> is a hard
limit of the number of server threads, and must be greater than
the following:</p>
<ul>
- <li>set the value of <code class="directive"><a href="../mod/mpm_common.html# maxconnectionsperchild">
+ <li>set the value of <code class="directive"><a href="../mod/mpm_common.html#maxconnectionsperchild">
MaxConnectionsPerChild</a></code> to zero</li>
- <li>set the value of <code class="directive"><a href="../mod/mpm_common.html# maxsparethreads">
+ <li>set the value of <code class="directive"><a href="../mod/mpm_common.html#maxsparethreads">
MaxSpareThreads</a></code> to the same value as
<code class="directive"><a href="../mod/mpm_common.html#maxrequestworkers">MaxRequestWorkers</a></code></li>
</ul>
<code class="directive"><a href="../mod/mpm_common.html#maxrequestworkers">MaxRequestWorkers</a></code>. Le nombre
maximum de processus enfants actifs est défini par la valeur de la
directive <code class="directive"><a href="../mod/mpm_common.html#maxrequestworkers">MaxRequestWorkers</a></code>
- divisée par la valeur de la directive <code class="directive"><a href="../mod/mpm_common.html# threadsperchild">
+ divisée par la valeur de la directive <code class="directive"><a href="../mod/mpm_common.html#threadsperchild">
ThreadsPerChild</a></code>.</p>
<p>Deux directives permettent de fixer des limites absolues pour le
La valeur de la directive <code class="directive"><a href="../mod/mpm_common.html#serverlimit">ServerLimit</a></code> constitue une limite
absolue pour le nombre de processus enfants actifs, et doit être
supérieure ou égale à la valeur de la directive <code class="directive"><a href="../mod/mpm_common.html#maxrequestworkers">MaxRequestWorkers</a></code> divisée par la valeur de
- la directive <code class="directive"><a href="../mod/mpm_common.html# threadsperchild">
+ la directive <code class="directive"><a href="../mod/mpm_common.html#threadsperchild">
ThreadsPerChild</a></code>. La valeur de la directive <code class="directive"><a href="../mod/mpm_common.html#threadlimit">ThreadLimit</a></code> constitue une limite
absolue pour le nombre de threads par processus enfant, et doit être
supérieure ou égale à la valeur de la directive <code class="directive"><a href="../mod/mpm_common.html#threadsperchild">ThreadsPerChild</a></code>.</p>
processus enfants individuels de la manière suivante :</p>
<ul>
- <li>définir la valeur de <code class="directive"><a href="../mod/mpm_common.html# maxconnectionsperchild">
+ <li>définir la valeur de <code class="directive"><a href="../mod/mpm_common.html#maxconnectionsperchild">
MaxConnectionsPerChild</a></code> à zéro</li>
- <li>Définir la valeur de <code class="directive"><a href="../mod/mpm_common.html# maxsparethreads">
+ <li>Définir la valeur de <code class="directive"><a href="../mod/mpm_common.html#maxsparethreads">
MaxSpareThreads</a></code> à la même valeur que <code class="directive"><a href="../mod/mpm_common.html#maxrequestworkers">MaxRequestWorkers</a></code></li>
</ul>
<p>活動中の子プロセスの数と子プロセス中のサーバスレッドの数の越えられない
上限を設定するディレクティブが二つあります。これらはサーバを
完全に停止して、再起動することでしか変更することはできません。
- <code class="directive"><a href="../mod/mpm_common.html#serverlimit ">ServerLimit
+ <code class="directive"><a href="../mod/mpm_common.html#serverlimit">ServerLimit
</a></code> は活動中の子プロセスの越えられない上限を設定し、
<code class="directive"><a href="../mod/mpm_common.html#maxclients">MaxClients</a></code> ディレクティブ
- の値を <code class="directive"><a href="../mod/mpm_common.html# threadsperchild">
+ の値を <code class="directive"><a href="../mod/mpm_common.html#threadsperchild">
ThreadsPerChild</a></code> の値で割った値以上である
必要があります。<code class="directive"><a href="../mod/mpm_common.html#threadlimit">ThreadLimit</a></code> は
サーバスレッドの越えられない上限で、<code class="directive"><a href="../mod/mpm_common.html#threadsperchild">ThreadsPerChild</a></code> ディレクティブの
これは以下の様にして実現できます。</p>
<ul>
- <li><code class="directive"><a href="../mod/mpm_common.html# maxrequestsperchild">
+ <li><code class="directive"><a href="../mod/mpm_common.html#maxrequestsperchild">
MaxRequestsPerChild</a></code> の値を 0 に設定する</li>
- <li><code class="directive"><a href="../mod/mpm_common.html# maxsparethreads">
+ <li><code class="directive"><a href="../mod/mpm_common.html#maxsparethreads">
MaxSpareThreads</a></code> の値を
<code class="directive"><a href="../mod/mpm_common.html#maxclients">MaxClients</a></code>
と同じ値にする</li>
will replace A with B everywhere in a request, and will continue doing
so until there are no more As to be replaced.
</p>
-
<pre class="prettyprint lang-config">RewriteRule (.*)A(.*) $1B$2 [N]</pre>
-
<p>You can think of this as a <code>while</code> loop: While this
pattern still matches (i.e., while the URI still contains an
<code>A</code>), perform this substitution (i.e., replace the
<code>A</code> with a <code>B</code>).</p>
+<p>In 2.4.8 and later, this module returns an error after 32,000 iterations to
+protect against unintended looping. An alternative maximum number of
+iterations can be specified by adding to the N flag. </p>
+<pre class="prettyprint lang-config">
+# Be willing to replace 1 character in each pass of the loop
+RewriteRule (.+)[><;]$ $1 [N=64000]
+# ... or, give up if after 10 loops
+RewriteRule (.+)[><;]$ $1 [N=10]
+</pre>
+
+
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="flag_nc" id="flag_nc">NC|nocase</a></h2>
<h2><a name="flag_s" id="flag_s">S|skip</a></h2>
<p>The [S] flag is used to skip rules that you don't want to run. The
syntax of the skip flag is [S=<em>N</em>], where <em>N</em> signifies
-the number of rules to skip (provided the <code class="directive"><a href="../mod/mod_rewrite.html# rewriterule">
+the number of rules to skip (provided the <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">
RewriteRule</a></code> matches). This can be thought of as a <code>goto</code>
statement in your rewrite ruleset. In the following example, we only want
to run the <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> if the
<p><span>Langues Disponibles: </span><a href="../en/rewrite/flags.html" hreflang="en" rel="alternate" title="English"> en </a> |
<a href="../fr/rewrite/flags.html" title="Français"> fr </a></p>
</div>
+<div class="outofdate">Cette traduction peut être périmée. Vérifiez la version
+ anglaise pour les changements récents.</div>
<p>Ce document décrit les drapeaux disponibles dans la directive
<code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code>, en fournissant
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.fr.xsl"?>
-<!-- English Revision: 1460931 -->
+<!-- English Revision: 1460931:1562174 (outdated) -->
<!-- French translation : Lucien GENTIS -->
<!-- Reviewed by : Vincent Deffontaines -->
<variants>
<variant>en</variant>
- <variant>fr</variant>
+ <variant outdated="yes">fr</variant>
</variants>
</metafile>
</pre>
- <p>Diğer yandan <code class="directive"><a href="./mod/mod_alias.html#takma adlar"><Takma
+ <p>Diğer yandan <code class="directive"><a href="./mod/mod_alias.html#takma adlar"><Takma
adlar></a></code> tam tersi eşlenir:</p>
<pre class="prettyprint lang-config">
<li><code class="module"><a href="./mod/mod_ssl.html">mod_ssl</a></code>: The default format of the <code>*_DN</code>
variables has changed. The old format can still be used with the new
<code>LegacyDNStringFormat</code> argument to <code class="directive"><a href="./mod/mod_ssl.html#ssloptions">SSLOptions</a></code>. The SSLv2 protocol is
- no longer supported. <code class="directive"><a href="./mod/mod_ssl.html#sslproxycheckpeercn 	 ">SSLProxyCheckPeerCN
- </a></code> and <code class="directive"><a href="./mod/mod_ssl.html#sslproxycheckpeerexpire 	 ">SSLProxyCheckPeerExpire
+ no longer supported. <code class="directive"><a href="./mod/mod_ssl.html#sslproxycheckpeercn">SSLProxyCheckPeerCN
+ </a></code> and <code class="directive"><a href="./mod/mod_ssl.html#sslproxycheckpeerexpire">SSLProxyCheckPeerExpire
</a></code> now default to On, causing proxy requests to HTTPS hosts
with bad or outdated certificates to fail with a 502 status code (Bad
gateway)</li>
accomplished in the following manner.</p>
<p>First, you will need to add the virtual host information to the log
-entries. This can be done using the <code class="directive"><a href="../mod/mod_log_config.html# logformat">
+entries. This can be done using the <code class="directive"><a href="../mod/mod_log_config.html#logformat">
LogFormat</a></code>
directive, and the <code>%v</code> variable. Add this to the beginning
of your log format string:</p>
<p>Tout d'abord, vous devez ajouter le nom du serveur virtuel à chaque
entrée du journal. Ceci se paramètre au moyen de la directive
-<code class="directive"><a href="../mod/mod_log_config.html# logformat"> LogFormat</a></code> et de la
+<code class="directive"><a href="../mod/mod_log_config.html#logformat"> LogFormat</a></code> et de la
variable <code>%v</code>. Ajoutez cette variable au début de la chaîne
de définition du format de journalisations :</p>
journalisation au format standard (CLF : 'Common Log Format'), mais dont
chaque ligne débutera par le nom canonique du serveur virtuel (spécifié
par la directive <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>).
-(Voir <code class="directive"><a href="../mod/mod_log_config.html#formats de journalisation personnalisés">Formats de journalisation
+(Voir <code class="directive"><a href="../mod/mod_log_config.html#formats de journalisation personnalisés">Formats de journalisation
personnalisés</a></code> pour d'autres informations sur la
personnalisation des fichiers journaux.)</p>
projects / apache / commitdiff