www/apache
1
0
Fork 0
mirror of https://github.com/apache/httpd.git synced 2025-08-08 15:02:10 +03:00
Code Activity

s/the the/the/g

Browse Source 
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1690120 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Rich Bowen
2015-07-09 16:01:56 +00:00
parent eb1a60e0dc
commit 85f20cb5d2
14 changed files with 14 additions and 230 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/manual/misc/perf-scaling.xml
View File

@@ -1086,7 +1086,7 @@ CustomLog "|/usr/local/apache2/bin/rotatelogs /var/log/access_log 86400" common
</code> </code>
the equivalent is <code>limit the equivalent is <code>limit
</code> </code>
and works analogous the the Bourne-like <code>ulimit and works analogous to the Bourne-like <code>ulimit
</code> </code>
: :
</p> </p>

216
docs/manual/mod/mod_log_forensic.html.fr
View File

@@ -1,216 +0,0 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="fr" xml:lang="fr"><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" />
<!--
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
This file is generated from xml source: DO NOT EDIT
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-->
<title>mod_log_forensic - Serveur Apache HTTP Version 2.5</title>
<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
<script src="../style/scripts/prettify.min.js" type="text/javascript">
</script>
<link href="../images/favicon.ico" rel="shortcut icon" /></head>
<body>
<div id="page-header">
<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/quickreference.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossaire</a> | <a href="../sitemap.html">Plan du site</a></p>
<p class="apache">Serveur Apache HTTP Version 2.5</p>
<img alt="" src="../images/feather.gif" /></div>
<div class="up"><a href="./"><img title="&lt;-" alt="&lt;-" src="../images/left.gif" /></a></div>
<div id="path">
<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://httpd.apache.org/">Serveur HTTP</a> &gt; <a href="http://httpd.apache.org/docs/">Documentation</a> &gt; <a href="../">Version 2.5</a> &gt; <a href="./">Modules</a></div>
<div id="page-content">
<div id="preamble"><h1>Module Apache mod_log_forensic</h1>
<div class="toplang">
<p><span>Langues Disponibles: </span><a href="../en/mod/mod_log_forensic.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
<a href="../fr/mod/mod_log_forensic.html" title="Fran<61>ais">&nbsp;fr&nbsp;</a> |
<a href="../ja/mod/mod_log_forensic.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
<a href="../tr/mod/mod_log_forensic.html" hreflang="tr" rel="alternate" title="T<>rk<72>e">&nbsp;tr&nbsp;</a></p>
</div>
<table class="module"><tr><th><a href="module-dict.html#Description">Description:</a></th><td>Journalisation l<>gale des requ<71>tes envoy<6F>es au
serveur</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<75>de<64>Module:</a></th><td>log_forensic_module</td></tr>
<tr><th><a href="module-dict.html#SourceFile">Fichier<65>Source:</a></th><td>mod_log_forensic.c</td></tr></table>
<h3>Sommaire</h3>
<p>Ce module permet la journalisation l<>gale des requ<71>tes client. La
journalisation s'effectuant avant et apr<70>s le traitement de la
requ<71>te, le journal l<>gal contient deux lignes pour chaque requ<71>te.
Le processus de journalisation l<>gale est tr<74>s strict, <20> savoir
:</p>
<ul>
<li>Le format est fig<69>. Vous ne pouvez pas modifier le format du
journal <20> l'ex<65>cution.</li>
<li>S'il ne peut pas enregistrer ses donn<6E>es, le processus enfant se
termine aussit<69>t, et peut <20>ventuellement enregistrer un vidage
m<>moire (selon la d<>finition de la directive <code class="directive"><a href="../mod/mpm_common.html#coredumpdirectory">CoreDumpDirectory</a></code>).</li>
</ul>
<p>Pour interpr<70>ter les donn<6E>es du journal l<>gal, vous pouvez vous
aider du script <code>check_forensic</code> qui se trouve dans le
r<>pertoire support de la distribution.</p>
<div class="note">Note de traduction : le terme "l<>gal" utilis<69> dans le pr<70>sent document ne sugg<67>re aucunement que
ce module apporte une valeur juridique aux journaux. Il est <20> comprendre dans le contexte
similaire <20> ce que l'on trouve en analyse medico-l<>gale. En d'autres termes, la finalit<69> de ce module
est de simplifier les op<6F>rations d'investigation autour du traitement des requ<71>tes par le serveur.</div>
</div>
<div id="quickview"><h3>Sujets</h3>
<ul id="topics">
<li><img alt="" src="../images/down.gif" /> <a href="#formats">Format du journal Forensic</a></li>
<li><img alt="" src="../images/down.gif" /> <a href="#security">Consid<69>rations <20> propos de
s<EFBFBD>curit<EFBFBD></a></li>
</ul><h3 class="directives">Directives</h3>
<ul id="toc">
<li><img alt="" src="../images/down.gif" /> <a href="#forensiclog">ForensicLog</a></li>
</ul>
<h3>Voir aussi</h3>
<ul class="seealso">
<li><a href="../logs.html">Les fichiers journaux
d'Apache</a></li>
<li><code class="module"><a href="../mod/mod_log_config.html">mod_log_config</a></code></li>
</ul><ul class="seealso"><li><a href="#comments_section">Commentaires</a></li></ul></div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="formats" id="formats">Format du journal Forensic</a></h2>
<p>Chaque requ<71>te fait l'objet d'une double journalisation. La
requ<71>te est journalis<69>e une premi<6D>re fois avant son traitement
(c'est <20> dire apr<70>s la r<>ception des en-t<>tes). La deuxi<78>me entr<74>e
du journal est <20>crite <em>apr<70>s</em> le traitement de la requ<71>te, en
fait au moment de la journalisation habituelle.</p>
<p>Un identifiant unique est attribu<62> <20> chaque requ<71>te afin de
pouvoir l'identifier. Cette identifiant l<>gal peut faire l'objet
d'un enregistrement dans le journal standard en utilisant l'<27>l<EFBFBD>ment
de cha<68>ne de format <code>%{forensic-id}n</code>. Si vous utilisez
<code class="module"><a href="../mod/mod_unique_id.html">mod_unique_id</a></code>, c'est l'identifiant qu'il g<>n<EFBFBD>re qui
sera utilis<69>.</p>
<p>La premi<6D>re partie de la journalisation de la requ<71>te enregistre
l'identifiant l<>gal, la ligne de la requ<71>te et tous les en-t<>tes
re<72>us s<>par<61>s par des caract<63>res pipe (<code>|</code>). Voici <20>
titre d'exemple <20> quoi pourrait ressembler une telle entr<74>e (tout
<20>tant rassembl<62> sur une seule ligne) :</p>
<div class="example"><p><code>
+yQtJf8CoAB4AAFNXBIEAAAAA|GET /manual/de/images/down.gif
HTTP/1.1|Host:localhost%3a8080|User-Agent:Mozilla/5.0 (X11;
U; Linux i686; en-US; rv%3a1.6) Gecko/20040216
Firefox/0.8|Accept:image/png, <var>etc...</var>
</code></p></div>
<p>Le caract<63>re plus ('+') de d<>but indique qu'il s'agit de la
premi<6D>re entr<74>e de journal pour cette requ<71>te. La seconde entr<74>e ne
contiendra qu'un caract<63>re moins ('-') suivi de l'identifiant :</p>
<div class="example"><p><code>
-yQtJf8CoAB4AAFNXBIEAAAAA
</code></p></div>
<p>Le script <code>check_forensic</code> prend comme argument le nom
du fichier journal. Il recherche ces paires d'identifiants
<code>+</code>/<code>-</code> et affiche un message d'erreur si la
journalisation d'une requ<71>te n'est pas compl<70>te.</p>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="security" id="security">Consid<69>rations <20> propos de
s<EFBFBD>curit<EFBFBD></a></h2>
<p>Voir le document <a href="../misc/security_tips.html#serverroot">conseils en mati<74>re de
s<>curit<69></a> pour des d<>tails sur les raisons pour lesquelles votre
s<>curit<69> pourrait <20>tre compromise si le r<>pertoire dans lequel les
fichiers journaux sont stock<63>s sont inscriptibles par tout autre
utilisateur que celui qui d<>marre le serveur.</p>
<p>Les fichiers journaux peuvent contenir des donn<6E>es sensibles
comme le contenu des en-t<>tes <code>Authorization:</code> (qui
peuvent contenir des mots de passe) ; ils ne doivent donc <20>tre
lisibles que par l'utilisateur qui d<>marre le serveur.</p>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="directive-section"><h2><a name="forensiclog" id="forensiclog">Directive</a> <a name="ForensicLog" id="ForensicLog">ForensicLog</a></h2>
<table class="directive">
<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>D<>finit le nom de fichier du journal l<>gal</td></tr>
<tr><th><a href="directive-dict.html#Syntax">Syntaxe:</a></th><td><code>ForensicLog <var>nom-fichier</var>|<var>pipe</var></code></td></tr>
<tr><th><a href="directive-dict.html#Context">Contexte:</a></th><td>configuration du serveur, serveur virtuel</td></tr>
<tr><th><a href="directive-dict.html#Status">Statut:</a></th><td>Extension</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_log_forensic</td></tr>
</table>
<p>La directive <code class="directive">ForensicLog</code> permet de
contr<74>ler la journalisation des requ<71>tes <20> des fins d'analyse
l<>gale. Chaque entr<74>e du journal se voit assigner un identifiant
unique qui peut <20>tre associ<63> <20> la requ<71>te en utilisant la directive
<code class="directive"><a href="../mod/mod_log_config.html#customlog">CustomLog</a></code> habituelle.
<code class="module"><a href="../mod/mod_log_forensic.html">mod_log_forensic</a></code> cr<63>e un <20>l<EFBFBD>ment nomm<6D>
<code>forensic-id</code>, qui peut <20>tre ajout<75> au journal standard
en utilisant l'<27>l<EFBFBD>ment de format <code>%{forensic-id}n</code>.</p>
<p>L'argument, qui permet de sp<73>cifier l'emplacement vers lequel le
journal l<>gal sera <20>crit, peut contenir les deux types de valeurs
suivants :</p>
<dl>
<dt><var>nom-fichier</var></dt>
<dd>Un nom de fichier relatif au r<>pertoire d<>fini par la
directive <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>.</dd>
<dt><var>pipe</var></dt>
<dd>Le caract<63>re pipe "<code>|</code>", suivi du chemin vers un
programme qui recevra les informations de la journalisation sur
son entr<74>e standard. Le nom du programme peut <20>tre relatif au
r<>pertoire d<>fini par la directive <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>.
<div class="warning"><h3>S<>curit<69> :</h3>
<p>Si les journaux sont redirig<69>s vers un programme, ce dernier
s'ex<65>cutera sous l'utilisateur qui a d<>marr<72>
<code class="program"><a href="../programs/httpd.html">httpd</a></code>. Ce sera l'utilisateur root si le serveur
a <20>t<EFBFBD> d<>marr<72> par root ; v<>rifiez que le programme est
s<>curis<69> ou passe sous le contr<74>le d'un utilisateur poss<73>dant des
droits restreints.</p>
</div>
<div class="note"><h3>Note</h3>
<p>Lors de la sp<73>cification d'un chemin de fichier sur les
plate-formes non-Unix, il faut prendre soin de ne pas oublier
que seuls les slashes directs doivent <20>tre utilis<69>s, m<>me si la
plate-forme autorise l'emploi d'anti-slashes. D'une mani<6E>re
g<>n<EFBFBD>rale, c'est une bonne id<69>e que de n'utiliser que des slashes
directs dans les fichiers de configuration.</p>
</div></dd>
</dl>
</div>
</div>
<div class="bottomlang">
<p><span>Langues Disponibles: </span><a href="../en/mod/mod_log_forensic.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
<a href="../fr/mod/mod_log_forensic.html" title="Fran<61>ais">&nbsp;fr&nbsp;</a> |
<a href="../ja/mod/mod_log_forensic.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
<a href="../tr/mod/mod_log_forensic.html" hreflang="tr" rel="alternate" title="T<>rk<72>e">&nbsp;tr&nbsp;</a></p>
</div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Commentaires</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&amp;A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div>
<script type="text/javascript"><!--//--><![CDATA[//><!--
var comments_shortname = 'httpd';
var comments_identifier = 'http://httpd.apache.org/docs/trunk/mod/mod_log_forensic.html';
(function(w, d) {
if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
d.write('<div id="comments_thread"><\/div>');
var s = d.createElement('script');
s.type = 'text/javascript';
s.async = true;
s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
(d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
}
else {
d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
}
})(window, document);
//--><!]]></script></div><div id="footer">
<p class="apache">Copyright 2015 The Apache Software Foundation.<br />Autoris<69> sous <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/quickreference.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossaire</a> | <a href="../sitemap.html">Plan du site</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
if (typeof(prettyPrint) !== 'undefined') {
prettyPrint();
}
//--><!]]></script>
</body></html>

2
docs/manual/mod/mod_ssl.xml
View File

@@ -847,7 +847,7 @@ algorithm type.
</p> </p>
<p> <p>
Finally the the end-entity certificate's private key can also be Finally the end-entity certificate's private key can also be
added to the certificate file instead of using a separate added to the certificate file instead of using a separate
<directive module="mod_ssl">SSLCertificateKeyFile</directive> <directive module="mod_ssl">SSLCertificateKeyFile</directive>
directive. This practice is highly discouraged. If it is used, directive. This practice is highly discouraged. If it is used,

4
modules/aaa/mod_authn_core.c
View File

@@ -109,7 +109,7 @@ static authn_status authn_alias_check_password(request_rec *r, const char *user,
const char *password) const char *password)
{ {
/* Look up the provider alias in the alias list */ /* Look up the provider alias in the alias list */
/* Get the the dir_config and call ap_Merge_per_dir_configs() */ /* Get the dir_config and call ap_Merge_per_dir_configs() */
/* Call the real provider->check_password() function */ /* Call the real provider->check_password() function */
/* return the result of the above function call */ /* return the result of the above function call */
@@ -141,7 +141,7 @@ static authn_status authn_alias_get_realm_hash(request_rec *r, const char *user,
const char *realm, char **rethash) const char *realm, char **rethash)
{ {
/* Look up the provider alias in the alias list */ /* Look up the provider alias in the alias list */
/* Get the the dir_config and call ap_Merge_per_dir_configs() */ /* Get the dir_config and call ap_Merge_per_dir_configs() */
/* Call the real provider->get_realm_hash() function */ /* Call the real provider->get_realm_hash() function */
/* return the result of the above function call */ /* return the result of the above function call */

2
modules/aaa/mod_authz_core.c
View File

@@ -196,7 +196,7 @@ static authz_status authz_alias_check_authorization(request_rec *r,
authz_status ret = AUTHZ_DENIED; authz_status ret = AUTHZ_DENIED;
/* Look up the provider alias in the alias list. /* Look up the provider alias in the alias list.
* Get the the dir_config and call ap_Merge_per_dir_configs() * Get the dir_config and call ap_Merge_per_dir_configs()
* Call the real provider->check_authorization() function * Call the real provider->check_authorization() function
* return the result of the above function call * return the result of the above function call
*/ */

2
modules/cache/cache_util.h vendored
View File

@@ -264,7 +264,7 @@ int cache_check_freshness(cache_handle_t *h, cache_request_rec *cache,
* Try obtain a cache wide lock on the given cache key. * Try obtain a cache wide lock on the given cache key.
* *
* If we return APR_SUCCESS, we obtained the lock, and we are clear to * If we return APR_SUCCESS, we obtained the lock, and we are clear to
* proceed to the backend. If we return APR_EEXISTS, the the lock is * proceed to the backend. If we return APR_EEXISTS, then the lock is
* already locked, someone else has gone to refresh the backend data * already locked, someone else has gone to refresh the backend data
* already, so we must return stale data with a warning in the mean * already, so we must return stale data with a warning in the mean
* time. If we return anything else, then something has gone pear * time. If we return anything else, then something has gone pear

2
modules/filters/mod_charset_lite.c
View File

@@ -1026,7 +1026,7 @@ static apr_status_t xlate_in_filter(ap_filter_t *f, apr_bucket_brigade *bb,
* Content-Length can't be unset here because that would break * Content-Length can't be unset here because that would break
* being able to read the request body. * being able to read the request body.
* Processing of chunked request bodies is not impacted by this * Processing of chunked request bodies is not impacted by this
* filter since the the length was not declared anyway. * filter since the length was not declared anyway.
*/ */
ap_log_rerror(APLOG_MARK, APLOG_TRACE1, 0, f->r, ap_log_rerror(APLOG_MARK, APLOG_TRACE1, 0, f->r,
"Request body length may change, resulting in " "Request body length may change, resulting in "

2
modules/filters/mod_ext_filter.c
View File

@@ -635,7 +635,7 @@ static apr_status_t init_filter_instance(ap_filter_t *f)
/* drain_available_output(): /* drain_available_output():
* *
* if any data is available from the filter, read it and append it * if any data is available from the filter, read it and append it
* to the the bucket brigade * to the bucket brigade
*/ */
static apr_status_t drain_available_output(ap_filter_t *f, static apr_status_t drain_available_output(ap_filter_t *f,
apr_bucket_brigade *bb) apr_bucket_brigade *bb)

2
modules/filters/mod_sed.c
View File

@@ -312,7 +312,7 @@ static apr_status_t sed_response_filter(ap_filter_t *f,
* evaluation is allocated on request's pool so it will be cleared once * evaluation is allocated on request's pool so it will be cleared once
* request is over. * request is over.
* *
* If flush bucket is found then append the the flush bucket to ctx->bb * If flush bucket is found then append the flush bucket to ctx->bb
* and pass it to next filter. There may be some data which will still be * and pass it to next filter. There may be some data which will still be
* in sed's internal buffer which can't be flushed until new line * in sed's internal buffer which can't be flushed until new line
* character is arrived. * character is arrived.

2
modules/http2/mod_h2/h2_response.h
View File

@@ -16,7 +16,7 @@
#ifndef __mod_h2__h2_response__ #ifndef __mod_h2__h2_response__
#define __mod_h2__h2_response__ #define __mod_h2__h2_response__
/* h2_response is just the data belonging the the head of a HTTP response, /* h2_response is just the data belonging to the head of a HTTP response,
* suitable prepared to be fed to nghttp2 for response submit. * suitable prepared to be fed to nghttp2 for response submit.
*/ */
typedef struct h2_headers { typedef struct h2_headers {

2
modules/http2/sandbox/httpd/mod_ssl-alpn/ssl_engine_kernel.c
View File

@@ -1737,7 +1737,7 @@ SSL_SESSION *ssl_callback_GetSessionCacheEntry(SSL *ssl,
/* /*
* This callback function is executed by OpenSSL whenever a * This callback function is executed by OpenSSL whenever a
* SSL_SESSION is removed from the the internal OpenSSL cache. * SSL_SESSION is removed from the internal OpenSSL cache.
* We use this to remove the SSL_SESSION in the inter-process * We use this to remove the SSL_SESSION in the inter-process
* disk-cache, too. * disk-cache, too.
*/ */

2
modules/ssl/ssl_engine_kernel.c
View File

@@ -1769,7 +1769,7 @@ SSL_SESSION *ssl_callback_GetSessionCacheEntry(SSL *ssl,
/* /*
* This callback function is executed by OpenSSL whenever a * This callback function is executed by OpenSSL whenever a
* SSL_SESSION is removed from the the internal OpenSSL cache. * SSL_SESSION is removed from the internal OpenSSL cache.
* We use this to remove the SSL_SESSION in the inter-process * We use this to remove the SSL_SESSION in the inter-process
* disk-cache, too. * disk-cache, too.
*/ */

2
server/core.c
View File

@@ -1130,7 +1130,7 @@ AP_DECLARE(apr_off_t) ap_get_limit_req_body(const request_rec *r)
/***************************************************************** /*****************************************************************
* *
* Commands... this module handles almost all of the NCSA httpd.conf * Commands... this module handles almost all of the NCSA httpd.conf
* commands, but most of the old srm.conf is in the the modules. * commands, but most of the old srm.conf is in the modules.
*/ */

2
server/mpm/netware/mpm_netware.c
View File

@@ -1203,7 +1203,7 @@ static int CommandLineInterpreter(scr_t screenID, const char *commandLine)
ActivateScreen (getscreenhandle()); ActivateScreen (getscreenhandle());
/* If an instance id was not given but the nlm is loaded in /* If an instance id was not given but the nlm is loaded in
protected space, then the the command belongs to the protected space, then the command belongs to the
OS address space instance to pass it on. */ OS address space instance to pass it on. */
pID = strstr (szcommandLine, "-p"); pID = strstr (szcommandLine, "-p");
if ((pID == NULL) && nlmisloadedprotected()) if ((pID == NULL) && nlmisloadedprotected())