From bb11c3b202b7336ccef3b4e4417fd60823d00fad Mon Sep 17 00:00:00 2001 From: Tony Stevenson Date: Fri, 24 Aug 2007 00:42:35 +0000 Subject: [PATCH] =?utf8?q?Updated=20as=20per=20Igor=20Gali=C4=87=20(a.k.a.?= =?utf8?q?=20#Apache=20jmcg)=20=20docs@=20email.?= MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit nobomb set in Cream/WinVim git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@569202 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/caching.html.en | 12 ++++++------ docs/manual/caching.xml | 12 ++++++------ 2 files changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/manual/caching.html.en b/docs/manual/caching.html.en index cdb973de19..b1ee00e128 100644 --- a/docs/manual/caching.html.en +++ b/docs/manual/caching.html.en @@ -564,14 +564,14 @@ CacheDirLength 1

To store items in the cache, mod_disk_cache creates - a 22 character hash of the url being requested. Thie hash incorporates + a 22 character hash of the URL being requested. This hash incorporates the hostname, protocol, port, path and any CGI arguments to the URL, to ensure that multiple URLs do not collide.

Each character may be any one of 64-different characters, which mean that overall there are 22^64 possible hashes. For example, a URL might be hashed to xyTGxSMO2b68mBCykqkp1w. This hash is used - as a prefix for the naming of the files specific to that url within + as a prefix for the naming of the files specific to that URL within the cache, however first it is split up into directories as per the CacheDirLevels and CacheDirLength @@ -602,15 +602,15 @@ CacheDirLength 1 With the setting of "2" used in the above example, a grand total of 4096 subdirectories can ultimately be created. With 1 million files cached, this works out at roughly 245 cached - urls per directory.

+ URLs per directory.

-

Each url uses at least two files in the cache-store. Typically +

Each URL uses at least two files in the cache-store. Typically there is a ".header" file, which includes meta-information about - the url, such as when it is due to expire and a ".data" file + the URL, such as when it is due to expire and a ".data" file which is a verbatim copy of the content to be served.

In the case of a content negotiated via the "Vary" header, a - ".vary" directory will be created for the url in question. This + ".vary" directory will be created for the URL in question. This directory will have multiple ".data" files corresponding to the differently negotiated content.

diff --git a/docs/manual/caching.xml b/docs/manual/caching.xml index 1348ffacf2..c88c8aaa2b 100644 --- a/docs/manual/caching.xml +++ b/docs/manual/caching.xml @@ -624,14 +624,14 @@ CacheDirLength 1 Understanding the Cache-Store

To store items in the cache, mod_disk_cache creates - a 22 character hash of the url being requested. Thie hash incorporates + a 22 character hash of the URL being requested. This hash incorporates the hostname, protocol, port, path and any CGI arguments to the URL, to ensure that multiple URLs do not collide.

Each character may be any one of 64-different characters, which mean that overall there are 22^64 possible hashes. For example, a URL might be hashed to xyTGxSMO2b68mBCykqkp1w. This hash is used - as a prefix for the naming of the files specific to that url within + as a prefix for the naming of the files specific to that URL within the cache, however first it is split up into directories as per the CacheDirLevels and CacheDirLength @@ -662,15 +662,15 @@ CacheDirLength 1 With the setting of "2" used in the above example, a grand total of 4096 subdirectories can ultimately be created. With 1 million files cached, this works out at roughly 245 cached - urls per directory.

+ URLs per directory.

-

Each url uses at least two files in the cache-store. Typically +

Each URL uses at least two files in the cache-store. Typically there is a ".header" file, which includes meta-information about - the url, such as when it is due to expire and a ".data" file + the URL, such as when it is due to expire and a ".data" file which is a verbatim copy of the content to be served.

In the case of a content negotiated via the "Vary" header, a - ".vary" directory will be created for the url in question. This + ".vary" directory will be created for the URL in question. This directory will have multiple ".data" files corresponding to the differently negotiated content.

-- 2.49.0