[EMAIL PROTECTED] wrote:
+
+ <p>If, for example, your configuration permits access to a resource by IP
+ address you should ensure that this content is not cached. You can do
this by
+ using the <directive module="mod_cache">CacheDisable</directive>
+ directive, or <module>mod_expires</module>. Left unchecked,
+ <module>mod_cache</module> - very much like a reverse proxy - would cache
+ the content when served and then serve it to any client, on any IP
+ address.</p>
You don't mean reverse proxy, you mean forward proxy (e.g. AOL or other
intermediate ISP proxies.) To this, you can add the point
This is no different than a user requesting a resource from this server
through a proxy such as AOL, and having the next user to request it also
be served the same content, if cache controls are not employed.
Speaking of which, why recommend mod_cache instead of promoting the HTTP
protocol itself to solve this problem correctly?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
