From: Chuck Murcko Date: Sun, 5 Jan 1997 09:02:09 +0000 (+0000) Subject: Proxy module documentation update. Add ProxyBlock, expand NoCache and X-Git-Tag: APACHE_1_2b5~11 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=8451d01baaa78aa6cbdb2ff3d37ad828bd31b9d5;p=apache Proxy module documentation update. Add ProxyBlock, expand NoCache and config sections. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@77385 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_proxy.html b/docs/manual/mod/mod_proxy.html index c713bb3b6d..38b1de3caf 100644 --- a/docs/manual/mod/mod_proxy.html +++ b/docs/manual/mod/mod_proxy.html @@ -34,6 +34,7 @@ and other protocols.
  • ProxyRequests
  • ProxyRemote
  • ProxyPass +
  • ProxyBlock
  • CacheRoot
  • CacheSize
  • CacheGcInterval @@ -110,6 +111,36 @@ Suppose the local server has address http://wibble.org; then Will 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 +

    ProxyBlock

    +Syntax: ProxyBlock <word/host/domain list>
    +Context: server config
    +Status: Base
    +Module: mod_proxy
    +Compatibility: ProxyBlock is only available in +Apache 1.2 and later.

    + +The ProxyBlock directive specifies a list of words, hosts and/or domains, +separated by spaces. HTTP, HTTPS, and FTP document requests to matched words, +hosts or domains are blocked by the proxy server. The proxy module +will also attempt to determine IP addresses of list items which may be +hostnames during startup, and cache them for match test as well. Example: + +

    +  ProxyBlock joes_garage.com some_host.co.uk rocky.wotsamattau.edu
    +
    + +'rocky.wotsamattau.edu' would also be matched if referenced by IP address.

    + +Note that 'wotsamattau' would also be sufficient to match 'wotsamattau.edu'.

    + +Note also that + +

    +ProxyBlock *
    +
    + +blocks connections to all sites. +

    CacheRoot

    Syntax: CacheRoot <directory>
    Context: server config
    @@ -195,7 +226,7 @@ then use <time> hours as the expiry time. override.

    NoCache

    -Syntax: NoCache <host/domain list>
    +Syntax: NoCache <word/host/domain list>
    Context: server config
    Status: Base
    Module: mod_proxy
    @@ -203,13 +234,18 @@ override. Apache 1.1 and later.

    The NoCache directive specifies a list of words, hosts and/or domains, separated -by spaces. HTTP documents from matched words, hosts or domains are not -cached by the proxy server. Example: +by spaces. HTTP and non-passworded FTP documents from matched words, hosts or +domains are not cached by the proxy server. The proxy module will +also attempt to determine IP addresses of list items which may be hostnames +during startup, and cache them for match test as well. Example:

    -  NoCache joes.garage.com some.host.co.uk wotsamattau.edu
    +  NoCache joes_garage.com some_host.co.uk bullwinkle.wotsamattau.edu
     
    +'bullwinkle.wotsamattau.edu' would also be matched if referenced by IP +address.

    + Note that 'wotsamattau' would also be sufficient to match 'wotsamattau.edu'.

    Note also that @@ -228,6 +264,9 @@ disables caching completely.

  • Controlling access to your proxy
  • Using Netscape hostname shortcuts
  • Why doesn't file type xxx download via FTP? +
  • Why does Apache start more slowly when using the + proxy module? +
  • Can I use the Apache proxy module with my SOCKS proxy?

    Controlling access to your proxy

    @@ -260,6 +299,27 @@ file. A useful line can be

    application/octet-stream bin dms lha lzh exe class tgz taz +

    Why does Apache start more slowly when using the + proxy module?

    + +If you're using the ProxyBlock or NoCache +directives, hostnames' IP addresses are looked up and cached during +startup for later match test. This may take a few seconds (or more) +depending on the speed with which the hostname lookups occur.

    + +

    Can I use the Apache proxy module with my SOCKS proxy?

    + +Yes. Just build Apache with the rule SOCKS4=yes in your +Configuration file, and follow the instructions there. SOCKS5 +capability can be added in a similar way (there's no SOCKS5 +rule yet, so use the EXTRA_LFLAGS definition, or build Apache +normally and run it with the runsocks wrapper provided with SOCKS5, +if your OS supports dynamically linked libraries.

    + +Remember that you'll also have to grant access to your Apache proxy machine by +permitting connections on the appropriate ports in your SOCKS daemon's +configuration.

    +