You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by ma...@hyperreal.org on 1998/06/08 21:05:16 UTC
cvs commit: apache-1.3/htdocs/manual/mod mod_proxy.html
martin 98/06/08 12:05:15
Modified: htdocs/manual/mod mod_proxy.html
Log:
Add some more background info about mod_proxy's behaviour;
e.g., that CacheRoot effectively enables cacheing
Revision Changes Path
1.39 +18 -4 apache-1.3/htdocs/manual/mod/mod_proxy.html
Index: mod_proxy.html
===================================================================
RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/mod_proxy.html,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -u -r1.38 -r1.39
--- mod_proxy.html 1998/03/20 11:11:04 1.38
+++ mod_proxy.html 1998/06/08 19:05:15 1.39
@@ -583,8 +583,11 @@
Apache 1.1 and later.<P>
Sets the name of the directory to contain cache files; this must be
-writable
-by the httpd server.
+writable by the httpd server.<BR>
+Setting <CODE>CacheRoot</CODE> enables proxy cacheing; without defining
+a <CODE>CacheRoot</CODE>, proxy functionality will be available
+if <CODE>ProxyRequests</CODE> are set to <CODE>On</CODE>, but no
+cacheing will be available.
<HR>
@@ -621,7 +624,9 @@
Sets the desired space usage of the cache, in KB (1024-byte units). Although
usage may grow above this setting, the garbage collection will delete files
-until the usage is at or below this setting.
+until the usage is at or below this setting.<BR>
+Depending on the expected proxy traffic volume and <CODE>CacheGcInterval</CODE>,
+use a value which is at least 20 to 40 % lower than the available space.
<HR>
@@ -657,7 +662,16 @@
Apache 1.1 and later.<P>
Check the cache every <time> hours, and delete files if the space
-usage is greater than that set by CacheSize.
+usage is greater than that set by CacheSize. Note that <time> accepts a
+float value, you could for example use <CODE>CacheGcInterval 1.5</CODE> to
+check the cache every 90 minutes. (If unset, no garbage collection will
+be performed, and the cache will grow indefinitely.)
+Note also that the larger the <CODE>CacheGcInterval</CODE>, the more
+extra space beyond the configured <CODE>CacheSize</CODE> will be
+needed for the cache between garbage collections.<BR> <!--
+Note that due to a design flaw, Apache does not automatically force a
+garbage collection when the available space on the file system where
+the cache resides is exhausted. -->
<HR>