From: Igor Galić <igalic@apache.org>
Date: Thu, 22 Apr 2010 12:07:44 +0000 (+0000)
Subject: Adding an cache hit/miss example, regarding PR#48241
X-Git-Tag: 2.3.6~172
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=08a37e75280f51712b27c5d8023f99dcea27e5a2;p=apache

Adding an cache hit/miss example, regarding PR#48241

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@936805 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/logs.html.en b/docs/manual/logs.html.en
index 3fe64e2539..9711bdf680 100644
--- a/docs/manual/logs.html.en
+++ b/docs/manual/logs.html.en
@@ -428,6 +428,21 @@
         CustomLog logs/non_english_log common env=!english
       </code></p></div>
 
+      <p>In a caching scenario one would want to know about
+      the efficiency of the cache. A very simple method to
+      find this out would be:</p>
+
+      <div class="example"><p><code>
+        SetEnv CACHE_MISS 1<br />
+        LogFormat "%h %l %u %t "%r " %&gt;s %b %{CACHE_MISS}e" common-cache
+        CustomLog logs/access_log common-cache
+      </code></p></div>
+
+      <p><code class="module"><a href="./mod/mod_cache.html">mod_cache</a></code> will run before
+      <code class="module"><a href="./mod/mod_env.html">mod_env</a></code> and when successfull will deliver the
+      content without it. In that case a cache hit will log
+      <code>-</code>, while a cache miss will log <code>1</code>.</p>
+
       <p>Although we have just shown that conditional logging is very
       powerful and flexible, it is not the only way to control the
       contents of the logs. Log files are more useful when they
diff --git a/docs/manual/logs.xml b/docs/manual/logs.xml
index 677ab847a6..d85e966c18 100644
--- a/docs/manual/logs.xml
+++ b/docs/manual/logs.xml
@@ -458,6 +458,21 @@
         CustomLog logs/non_english_log common env=!english
       </example>
 
+      <p>In a caching scenario one would want to know about
+      the efficiency of the cache. A very simple method to
+      find this out would be:</p>
+
+      <example>
+        SetEnv CACHE_MISS 1<br />
+        LogFormat "%h %l %u %t "%r " %>s %b %{CACHE_MISS}e" common-cache
+        CustomLog logs/access_log common-cache
+      </example>
+
+      <p><module>mod_cache</module> will run before
+      <module>mod_env</module> and when successfull will deliver the
+      content without it. In that case a cache hit will log
+      <code>-</code>, while a cache miss will log <code>1</code>.</p>
+
       <p>Although we have just shown that conditional logging is very
       powerful and flexible, it is not the only way to control the
       contents of the logs. Log files are more useful when they