On Wed, 22 Aug 2007 20:50:35 +0200 Ruediger Pluem <[EMAIL PROTECTED]> wrote:
Hi folks, > > Maybe a pointer to http://httpd.apache.org/docs/2.2/en/caching.html#inmemory > could help. It has some more detailed explanations. > Skimming through this doc link I found a few typos and Tony asked me to submit it, I thought this is the right enough place to do so: Index: manual/caching.xml =================================================================== --- manual/caching.xml (revision 569150) +++ manual/caching.xml (working copy) @@ -624,14 +624,14 @@ <title>Understanding the Cache-Store</title> <p>To store items in the cache, <module>mod_disk_cache</module> 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.</p> <p>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 <code>xyTGxSMO2b68mBCykqkp1w</code>. 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 <directive module="mod_disk_cache">CacheDirLevels</directive> and <directive module="mod_disk_cache">CacheDirLength</directive> @@ -662,15 +662,15 @@ 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.</p> + URLs per directory.</p> - <p>Each url uses at least two files in the cache-store. Typically + <p>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.</p> <p>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.</p> </section> So long, Igor --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
