diff options
| author | Jim Jagielski <jim@apache.org> | 2006-08-17 21:41:07 +0200 |
|---|---|---|
| committer | Jim Jagielski <jim@apache.org> | 2006-08-17 21:41:07 +0200 |
| commit | a187478d9ed1c0b4b9fbadb24c6c6c937538a838 (patch) | |
| tree | c11d3b63cf1960a62af9afc12b88a202c2115be6 /docs/manual/logs.html.en | |
| parent | Fix context error (diff) | |
| download | apache2-a187478d9ed1c0b4b9fbadb24c6c6c937538a838.tar.xz apache2-a187478d9ed1c0b4b9fbadb24c6c6c937538a838.zip | |
Update docs and transforms
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@432360 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs/manual/logs.html.en')
| -rw-r--r-- | docs/manual/logs.html.en | 122 |
1 files changed, 61 insertions, 61 deletions
diff --git a/docs/manual/logs.html.en b/docs/manual/logs.html.en index 1481de1d08..e8b87de7b0 100644 --- a/docs/manual/logs.html.en +++ b/docs/manual/logs.html.en @@ -6,21 +6,21 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> <title>Log Files - Apache HTTP Server</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 href="./images/favicon.ico" rel="shortcut icon" /></head> +<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 href="../images/favicon.ico" rel="shortcut icon" /></head> <body id="manual-page"><div id="page-header"> -<p class="menu"><a href="./mod/">Modules</a> | <a href="./mod/directives.html">Directives</a> | <a href="./faq/">FAQ</a> | <a href="./glossary.html">Glossary</a> | <a href="./sitemap.html">Sitemap</a></p> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p> <p class="apache">Apache HTTP Server Version 2.3</p> -<img alt="" src="./images/feather.gif" /></div> -<div class="up"><a href="./"><img title="<-" alt="<-" src="./images/left.gif" /></a></div> +<img alt="" src="../images/feather.gif" /></div> +<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div> <div id="path"> -<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="./">Version 2.3</a></div><div id="page-content"><div id="preamble"><h1>Log Files</h1> +<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.3</a></div><div id="page-content"><div id="preamble"><h1>Log Files</h1> <div class="toplang"> -<p><span>Available Languages: </span><a href="./en/logs.html" title="English"> en </a> | -<a href="./ja/logs.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | -<a href="./ko/logs.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +<p><span>Available Languages: </span><a href="../en/./logs.html" title="English"> en </a> | +<a href="../ja/./logs.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/./logs.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> </div> <p>In order to effectively manage a web server, it is necessary @@ -31,15 +31,15 @@ logging capabilities, and how to understand what the logs contain.</p> </div> -<div id="quickview"><ul id="toc"><li><img alt="" src="./images/down.gif" /> <a href="#security">Security Warning</a></li> -<li><img alt="" src="./images/down.gif" /> <a href="#errorlog">Error Log</a></li> -<li><img alt="" src="./images/down.gif" /> <a href="#accesslog">Access Log</a></li> -<li><img alt="" src="./images/down.gif" /> <a href="#rotation">Log Rotation</a></li> -<li><img alt="" src="./images/down.gif" /> <a href="#piped">Piped Logs</a></li> -<li><img alt="" src="./images/down.gif" /> <a href="#virtualhost">Virtual Hosts</a></li> -<li><img alt="" src="./images/down.gif" /> <a href="#other">Other Log Files</a></li> +<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#security">Security Warning</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#errorlog">Error Log</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#accesslog">Access Log</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#rotation">Log Rotation</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#piped">Piped Logs</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#virtualhost">Virtual Hosts</a></li> +<li><img alt="" src="../images/down.gif" /> <a href="#other">Other Log Files</a></li> </ul></div> -<div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></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">Security Warning</a></h2> @@ -57,15 +57,15 @@ possible for malicious clients to insert control-characters in the log files, so care must be taken in dealing with raw logs.</p> - </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="section"> <h2><a name="errorlog" id="errorlog">Error Log</a></h2> - <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td /><td><ul><li><code class="directive"><a href="./mod/core.html#errorlog">ErrorLog</a></code></li><li><code class="directive"><a href="./mod/core.html#loglevel">LogLevel</a></code></li></ul></td></tr></table> + <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td /><td><ul><li><code class="directive"><a href="../mod/core.html#errorlog">ErrorLog</a></code></li><li><code class="directive"><a href="../mod/core.html#loglevel">LogLevel</a></code></li></ul></td></tr></table> <p>The server error log, whose name and location is set by the - <code class="directive"><a href="./mod/core.html#errorlog">ErrorLog</a></code> directive, is the + <code class="directive"><a href="../mod/core.html#errorlog">ErrorLog</a></code> directive, is the most important log file. This is the place where Apache httpd will send diagnostic information and record any errors that it encounters in processing requests. It is the first place to @@ -93,7 +93,7 @@ <p>The first item in the log entry is the date and time of the message. The second entry lists the severity of the error being - reported. The <code class="directive"><a href="./mod/core.html#loglevel">LogLevel</a></code> + reported. The <code class="directive"><a href="../mod/core.html#loglevel">LogLevel</a></code> directive is used to control the types of errors that are sent to the error log by restricting the severity level. The third entry gives the IP address of the client that generated the @@ -123,17 +123,17 @@ <div class="example"><p><code> tail -f error_log </code></p></div> - </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="section"> <h2><a name="accesslog" id="accesslog">Access Log</a></h2> - <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="./mod/mod_log_config.html">mod_log_config</a></code></li><li><code class="module"><a href="./mod/mod_setenvif.html">mod_setenvif</a></code></li></ul></td><td><ul><li><code class="directive"><a href="./mod/mod_log_config.html#customlog">CustomLog</a></code></li><li><code class="directive"><a href="./mod/mod_log_config.html#logformat">LogFormat</a></code></li><li><code class="directive"><a href="./mod/mod_setenvif.html#setenvif">SetEnvIf</a></code></li></ul></td></tr></table> + <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="../mod/mod_log_config.html">mod_log_config</a></code></li><li><code class="module"><a href="../mod/mod_setenvif.html">mod_setenvif</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/mod_log_config.html#customlog">CustomLog</a></code></li><li><code class="directive"><a href="../mod/mod_log_config.html#logformat">LogFormat</a></code></li><li><code class="directive"><a href="../mod/mod_setenvif.html#setenvif">SetEnvIf</a></code></li></ul></td></tr></table> <p>The server access log records all requests processed by the server. The location and content of the access log are - controlled by the <code class="directive"><a href="./mod/mod_log_config.html#customlog">CustomLog</a></code> - directive. The <code class="directive"><a href="./mod/mod_log_config.html#logformat">LogFormat</a></code> + controlled by the <code class="directive"><a href="../mod/mod_log_config.html#customlog">CustomLog</a></code> + directive. The <code class="directive"><a href="../mod/mod_log_config.html#logformat">LogFormat</a></code> directive can be used to simplify the selection of the contents of the logs. This section describes how to configure the server to record information in the access log.</p> @@ -151,14 +151,14 @@ <p>Various versions of Apache httpd have used other modules and directives to control access logging, including mod_log_referer, mod_log_agent, and the - <code>TransferLog</code> directive. The <code class="directive"><a href="./mod/mod_log_config.html#customlog">CustomLog</a></code> directive now subsumes + <code>TransferLog</code> directive. The <code class="directive"><a href="../mod/mod_log_config.html#customlog">CustomLog</a></code> directive now subsumes the functionality of all the older directives.</p> <p>The format of the access log is highly configurable. The format is specified using a format string that looks much like a C-style printf(1) format string. Some examples are presented in the next sections. For a complete list of the possible contents of the - format string, see the <code class="module"><a href="./mod/mod_log_config.html">mod_log_config</a></code> <a href="mod/mod_log_config.html#formats">format strings</a>.</p> + format string, see the <code class="module"><a href="../mod/mod_log_config.html">mod_log_config</a></code> <a href="mod/mod_log_config.html#formats">format strings</a>.</p> <h3><a name="common" id="common">Common Log Format</a></h3> @@ -183,10 +183,10 @@ control characters "<code>\n</code>" for new-line and "<code>\t</code>" for tab.</p> - <p>The <code class="directive"><a href="./mod/mod_log_config.html#customlog">CustomLog</a></code> + <p>The <code class="directive"><a href="../mod/mod_log_config.html#customlog">CustomLog</a></code> directive sets up a new log file using the defined <em>nickname</em>. The filename for the access log is relative to - the <code class="directive"><a href="./mod/core.html#serverroot">ServerRoot</a></code> unless it + the <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> unless it begins with a slash.</p> <p>The above configuration will write log entries in a format @@ -206,12 +206,12 @@ <dt><code>127.0.0.1</code> (<code>%h</code>)</dt> <dd>This is the IP address of the client (remote host) which - made the request to the server. If <code class="directive"><a href="./mod/core.html#hostnamelookups">HostnameLookups</a></code> is + made the request to the server. If <code class="directive"><a href="../mod/core.html#hostnamelookups">HostnameLookups</a></code> is set to <code>On</code>, then the server will try to determine the hostname and log it in place of the IP address. However, this configuration is not recommended since it can significantly slow the server. Instead, it is best to use a - log post-processor such as <code class="program"><a href="./programs/logresolve.html">logresolve</a></code> to determine + log post-processor such as <code class="program"><a href="../programs/logresolve.html">logresolve</a></code> to determine the hostnames. The IP address reported here is not necessarily the address of the machine at which the user is sitting. If a proxy server exists between the user and the @@ -227,7 +227,7 @@ machine. This information is highly unreliable and should almost never be used except on tightly controlled internal networks. Apache httpd will not even attempt to determine - this information unless <code class="directive"><a href="./mod/core.html#identitycheck">IdentityCheck</a></code> is set + this information unless <code class="directive"><a href="../mod/core.html#identitycheck">IdentityCheck</a></code> is set to <code>On</code>.</dd> <dt><code>frank</code> (<code>%u</code>)</dt> @@ -350,12 +350,12 @@ <p>Multiple access logs can be created simply by specifying - multiple <code class="directive"><a href="./mod/mod_log_config.html#customlog">CustomLog</a></code> + multiple <code class="directive"><a href="../mod/mod_log_config.html#customlog">CustomLog</a></code> directives in the configuration file. For example, the following directives will create three access logs. The first contains the basic CLF information, while the second and third contain referer and browser - information. The last two <code class="directive"><a href="./mod/mod_log_config.html#customlog">CustomLog</a></code> lines show how + information. The last two <code class="directive"><a href="../mod/mod_log_config.html#customlog">CustomLog</a></code> lines show how to mimic the effects of the <code>ReferLog</code> and <code>AgentLog</code> directives.</p> <div class="example"><p><code> @@ -366,8 +366,8 @@ </code></p></div> <p>This example also shows that it is not necessary to define a - nickname with the <code class="directive"><a href="./mod/mod_log_config.html#logformat">LogFormat</a></code> directive. Instead, - the log format can be specified directly in the <code class="directive"><a href="./mod/mod_log_config.html#customlog">CustomLog</a></code> directive.</p> + nickname with the <code class="directive"><a href="../mod/mod_log_config.html#logformat">LogFormat</a></code> directive. Instead, + the log format can be specified directly in the <code class="directive"><a href="../mod/mod_log_config.html#customlog">CustomLog</a></code> directive.</p> <h3><a name="conditional" id="conditional">Conditional Logs</a></h3> @@ -378,8 +378,8 @@ client request. This is easily accomplished with the help of <a href="env.html">environment variables</a>. First, an environment variable must be set to indicate that the request meets certain conditions. This is usually accomplished with - <code class="directive"><a href="./mod/mod_setenvif.html#setenvif">SetEnvIf</a></code>. Then the - <code>env=</code> clause of the <code class="directive"><a href="./mod/mod_log_config.html#customlog">CustomLog</a></code> directive is used to + <code class="directive"><a href="../mod/mod_setenvif.html#setenvif">SetEnvIf</a></code>. Then the + <code>env=</code> clause of the <code class="directive"><a href="../mod/mod_log_config.html#customlog">CustomLog</a></code> directive is used to include or exclude requests where the environment variable is set. Some examples:</p> @@ -409,7 +409,7 @@ easier to simply post-process the log files to remove requests that you do not want to consider.</p> - </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="section"> <h2><a name="rotation" id="rotation">Log Rotation</a></h2> @@ -444,7 +444,7 @@ <p>Another way to perform log rotation is using <a href="#piped">piped logs</a> as discussed in the next section.</p> - </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="section"> <h2><a name="piped" id="piped">Piped Logs</a></h2> @@ -468,7 +468,7 @@ <p>One important use of piped logs is to allow log rotation without having to restart the server. The Apache HTTP Server - includes a simple program called <code class="program"><a href="./programs/rotatelogs.html">rotatelogs</a></code> + includes a simple program called <code class="program"><a href="../programs/rotatelogs.html">rotatelogs</a></code> for this purpose. For example, to rotate the logs every 24 hours, you can use:</p> @@ -489,7 +489,7 @@ <p>As with conditional logging, piped logs are a very powerful tool, but they should not be used where a simpler solution like off-line post-processing is available.</p> - </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="section"> <h2><a name="virtualhost" id="virtualhost">Virtual Hosts</a></h2> @@ -498,16 +498,16 @@ hosts</a>, there are several options for dealing with log files. First, it is possible to use logs exactly as in a single-host server. Simply by placing the logging directives - outside the <code class="directive"><a href="./mod/core.html#virtualhost"><VirtualHost></a></code> sections in the + outside the <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> sections in the main server context, it is possible to log all requests in the same access log and error log. This technique does not allow for easy collection of statistics on individual virtual hosts.</p> - <p>If <code class="directive"><a href="./mod/mod_log_config.html#customlog">CustomLog</a></code> - or <code class="directive"><a href="./mod/core.html#errorlog">ErrorLog</a></code> + <p>If <code class="directive"><a href="../mod/mod_log_config.html#customlog">CustomLog</a></code> + or <code class="directive"><a href="../mod/core.html#errorlog">ErrorLog</a></code> directives are placed inside a - <code class="directive"><a href="./mod/core.html#virtualhost"><VirtualHost></a></code> + <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> section, all requests or errors for that virtual host will be logged only to the specified file. Any virtual host which does not have logging directives will still have its requests sent @@ -533,18 +533,18 @@ host that is serving the request. Then a program like <a href="programs/other.html">split-logfile</a> can be used to post-process the access log in order to split it into one file per virtual host.</p> - </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div> + </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div> <div class="section"> <h2><a name="other" id="other">Other Log Files</a></h2> - <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="./mod/mod_logio.html">mod_logio</a></code></li><li><code class="module"><a href="./mod/mod_log_forensic.html">mod_log_forensic</a></code></li><li><code class="module"><a href="./mod/mod_cgi.html">mod_cgi</a></code></li><li><code class="module"><a href="./mod/mod_rewrite.html">mod_rewrite</a></code></li></ul></td><td><ul><li><code class="directive"><a href="./mod/mod_log_config.html#logformat">LogFormat</a></code></li><li><code class="directive"><a href="./mod/mod_log_forensic.html#forensiclog">ForensicLog</a></code></li><li><code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code></li><li><code class="directive"><a href="./mod/mod_rewrite.html#rewritelog">RewriteLog</a></code></li><li><code class="directive"><a href="./mod/mod_rewrite.html#rewriteloglevel">RewriteLogLevel</a></code></li><li><code class="directive"><a href="./mod/mod_cgi.html#scriptlog">ScriptLog</a></code></li><li><code class="directive"><a href="./mod/mod_cgi.html#scriptlogbuffer">ScriptLogBuffer</a></code></li><li><code class="directive"><a href="./mod/mod_cgi.html#scriptloglength">ScriptLogLength</a></code></li></ul></td></tr></table> + <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="../mod/mod_logio.html">mod_logio</a></code></li><li><code class="module"><a href="../mod/mod_log_forensic.html">mod_log_forensic</a></code></li><li><code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code></li><li><code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/mod_log_config.html#logformat">LogFormat</a></code></li><li><code class="directive"><a href="../mod/mod_log_forensic.html#forensiclog">ForensicLog</a></code></li><li><code class="directive"><a href="../mod/mpm_common.html#pidfile">PidFile</a></code></li><li><code class="directive"><a href="../mod/mod_rewrite.html#rewritelog">RewriteLog</a></code></li><li><code class="directive"><a href="../mod/mod_rewrite.html#rewriteloglevel">RewriteLogLevel</a></code></li><li><code class="directive"><a href="../mod/mod_cgi.html#scriptlog">ScriptLog</a></code></li><li><code class="directive"><a href="../mod/mod_cgi.html#scriptlogbuffer">ScriptLogBuffer</a></code></li><li><code class="directive"><a href="../mod/mod_cgi.html#scriptloglength">ScriptLogLength</a></code></li></ul></td></tr></table> <h3>Logging actual bytes sent and recieved</h3> - <p><code class="module"><a href="./mod/mod_logio.html">mod_logio</a></code> adds in two additional - <code class="directive"><a href="./mod/mod_log_config.html#logformat">LogFormat</a></code> fields + <p><code class="module"><a href="../mod/mod_logio.html">mod_logio</a></code> adds in two additional + <code class="directive"><a href="../mod/mod_log_config.html#logformat">LogFormat</a></code> fields (%I and %O) that log the actual number of bytes received and sent on the network.</p> @@ -552,7 +552,7 @@ <h3>Forensic Logging</h3> - <p><code class="module"><a href="./mod/mod_log_forensic.html">mod_log_forensic</a></code> provides for forensic logging of + <p><code class="module"><a href="../mod/mod_log_forensic.html">mod_log_forensic</a></code> provides for forensic logging of client requests. Logging is done before and after processing a request, so the forensic log contains two log lines for each request. The forensic logger is very strict with no customizations. @@ -564,7 +564,7 @@ <p>On startup, Apache httpd saves the process id of the parent httpd process to the file <code>logs/httpd.pid</code>. This - filename can be changed with the <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> directive. The + filename can be changed with the <code class="directive"><a href="../mod/mpm_common.html#pidfile">PidFile</a></code> directive. The process-id is for use by the administrator in restarting and terminating the daemon by sending signals to the parent process; on Windows, use the -k command line option instead. @@ -576,7 +576,7 @@ <p>In order to aid in debugging, the - <code class="directive"><a href="./mod/mod_cgi.html#scriptlog">ScriptLog</a></code> directive + <code class="directive"><a href="../mod/mod_cgi.html#scriptlog">ScriptLog</a></code> directive allows you to record the input to and output from CGI scripts. This should only be used in testing - not for live servers. More information is available in the <a href="mod/mod_cgi.html">mod_cgi</a> documentation.</p> @@ -586,17 +586,17 @@ <p>When using the powerful and complex features of <a href="mod/mod_rewrite.html">mod_rewrite</a>, it is almost - always necessary to use the <code class="directive"><a href="./mod/mod_rewrite.html#rewritelog">RewriteLog</a></code> to help + always necessary to use the <code class="directive"><a href="../mod/mod_rewrite.html#rewritelog">RewriteLog</a></code> to help in debugging. This log file produces a detailed analysis of how the rewriting engine transforms requests. The level of detail - is controlled by the <code class="directive"><a href="./mod/mod_rewrite.html#rewriteloglevel">RewriteLogLevel</a></code> directive.</p> + is controlled by the <code class="directive"><a href="../mod/mod_rewrite.html#rewriteloglevel">RewriteLogLevel</a></code> directive.</p> </div></div> <div class="bottomlang"> -<p><span>Available Languages: </span><a href="./en/logs.html" title="English"> en </a> | -<a href="./ja/logs.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | -<a href="./ko/logs.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> +<p><span>Available Languages: </span><a href="../en/./logs.html" title="English"> en </a> | +<a href="../ja/./logs.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | +<a href="../ko/./logs.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p> </div><div id="footer"> <p class="apache">Copyright 2006 The Apache Software Foundation.<br />Licensed under the <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/directives.html">Directives</a> | <a href="./faq/">FAQ</a> | <a href="./glossary.html">Glossary</a> | <a href="./sitemap.html">Sitemap</a></p></div> +<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div> </body></html>
\ No newline at end of file |