mod_proxy.c
file, and
is not compiled in by default. It provides for a caching proxy server.
This module is experimental. Use at your own risk.
FTP
,
HTTP/0.9
, and
HTTP/1.0
.
The module can be configured to connect to other proxy modules for these
and other protocols.
ProxyRequests Off
This allows or prevents Apache from functioning as a proxy server. Setting ProxyRequests to 'off' does not disable use of the ProxyPass directive.
This defines remote proxies to this proxy.
<remote-server> = <protocol>://<hostname>[:port]<protocol> is the protocol that should be used to communicate with the remote server; only "http" is supported by this module. Example:
ProxyRemote ftp http://ftpproxy.mydomain.com:8080 ProxyRemote http://goodguys.com/ http://mirrorguys.com:8000 ProxyRemote * http://cleversite.com
This directive allows remote servers to be mapped into the space of the local
server; the local server does not act as a proxy in the conventional sense,
but appears to be a mirror of the remote server.
ProxyPass /mirror/foo http://foo.comWill cause a local request for the http://wibble.org/mirror/foo/bar to be internally converted into a proxy request to http://foo.com/bar
Sets the name of the directory to contain cache files; this must be writable by the httpd server.
CacheSize 5
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.
Check the cache every <time> hours, and delete files if the space usage is greater than that set by CacheSize.
Cachable HTTP documents will be retained for at most <time> hours without checking the origin server. Thus documents can be at most <time> hours out of date. This restriction is enforced even if an expiry date was supplied with the document.
If the origin HTTP server did not supply an expiry date for the document, then estimate on using the formula
expiry-period = time-since-last-modification * <factor>For example, if the document was last modified 10 hours ago, and <factor> is 0.1, then the expiry period wil be set to 10*0.1 = 1 hour.
If the expiry-period would be longer than that set by CacheMaxExpire, then the latter takes precedence.
If the document is fetched via a protocol that does not support expirytimes, then use <time> as the expiry time. CacheMaxExpire does not override.
The NoCache directive specifies a list of hosts and/or domains, separated by spaces. HTTP documents from hosts or domains in the list are not cached by the proxy server. Example:
NoCache joes.garage.com some.host.co.uk wotsamattau.edu