0N/A<!
DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
0N/A<
TITLE>Apache module mod_proxy</
TITLE>
157N/A<!-- Background white, links blue (unvisited), navy (visited), red (active) --> 0N/A<
blockquote><
strong>Warning:</
strong>
0N/AThis document has been updated to take into account changes
0N/Amade in the 2.0 version of the Apache HTTP Server. Some of the
0N/Ainformation may still be inaccurate, please use it
0N/A<
H1 ALIGN="CENTER">Apache module mod_proxy</
H1>
0N/A<
p>This module provides for an <
STRONG>HTTP 1.1</
STRONG> proxy / gateway
0N/A><
STRONG>Status:</
STRONG></
A> Extension
0N/A><
STRONG>Module Identifier:</
STRONG></
A> proxy_module
0N/A><
STRONG>Compatibility:</
STRONG></
A> Available in Apache 1.1 and later.
0N/Aproxying capability for
0N/A<
CODE>CONNECT</
CODE> (for SSL),
0N/AThe module can be configured to connect to other proxy modules for these
0N/A<
P>This module was experimental in Apache
1.1.x. Improvements and bugfixes
0N/Awere made in Apache
v1.2.x and Apache
v1.3.x, then the module underwent a major
0N/Aoverhaul for Apache v2.0. The protocol support was upgraded to
HTTP/
1.1,
0N/Aand filter support was enabled.
0N/A<
P>Please note that the <
STRONG>caching</
STRONG> function present in mod_proxy up to Apache
0N/Av1.3.x has been <
STRONG>removed</
STRONG> from mod_proxy and will be incorporated
0N/Ainto a new module, mod_cache.
0N/A<
LI><
A HREF="#proxyrequests">ProxyRequests</
A>
0N/A<
LI><
A HREF="#proxyremote">ProxyRemote</
A>
0N/A<
LI><
A HREF="#proxypass">ProxyPass</
A>
0N/A<
LI><
A HREF="#proxypassreverse">ProxyPassReverse</
A>
0N/A<
LI><
A HREF="#proxyblock">ProxyBlock</
A>
0N/A<
LI><
A HREF="#allowconnect">AllowCONNECT</
A>
0N/A<
LI><
A HREF="#proxyreceivebuffersize">ProxyReceiveBufferSize</
A>
0N/A<
LI><
A HREF="#proxymaxforwards">ProxyMaxForwards</
A>
0N/A<
LI><
A HREF="#noproxy">NoProxy</
A>
0N/A<
LI><
A HREF="#proxydomain">ProxyDomain</
A>
0N/A<
LI><
A HREF="#proxyvia">ProxyVia</
A>
0N/A<
LI><
A HREF="#proxyerroroverride">ProxyErrorOverride</
A>
0N/A<
H2><
A NAME="configs">Common configuration topics</
A></
H2>
0N/A<
LI><
A HREF="#forwardreverse">Forward and Reverse Proxies</
A>
0N/A<
LI><
A HREF="#access">Controlling access to your proxy</
A>
0N/A<
LI><
A HREF="#shortname">Using Netscape hostname shortcuts</
A>
0N/A<
LI><
A HREF="#mimetypes">Why doesn't file type <
EM>xxx</
EM> download via FTP?</
A>
0N/A<
LI><
A HREF="#startup">Why does Apache start more slowly when using the
0N/A<!--<LI><A HREF="#socks">Can I use the Apache proxy module with my SOCKS proxy?</A>--> 0N/A<
LI><
A HREF="#intranet">What other functions are useful for an intranet proxy server?</
A>
0N/A<
H2><
A NAME="forwardreverse">Forward and Reverse Proxies</
A></
H2>
0N/AApache can be configured in both a <
EM>forward</
EM> and <
EM>reverse</
EM>
0N/A<
P>A <
EM>forward proxy</
EM> is an intermediate system that enables a browser to connect to a
0N/Aremote network to which it normally does not have access. A forward proxy
0N/Acan also be used to cache data, reducing load on the networks between the
0N/Aforward proxy and the remote webserver.
0N/A<
P>Apache's mod_proxy can be figured to
0N/Abehave like a forward proxy using the <
A HREF="#proxyremote">ProxyRemote</
A>
0N/Adirective. In addition, caching of data can be achieved by configuring
0N/AApache mod_cache. Other dedicated forward proxy packages include
0N/A<
P>A <
EM>reverse proxy</
EM> is a webserver system that is capable of serving webpages
0N/Asourced from other webservers - in addition to webpages on disk or generated
0N/Adynamically by CGI - making these pages look like they originated at the
0N/A<
P>When configured with the mod_cache module the reverse
0N/Aproxy can act as a cache for slower backend webservers. The reverse proxy
0N/Acan also enable advanced URL strategies and management techniques, allowing
0N/Awebpages served using different webserver systems or architectures to
0N/Acoexist inside the same URL space. Reverse proxy systems are also ideal for
0N/Aimplementing centralised logging websites with many or diverse website
0N/Abackends. Complex multi-tier webserver systems can be constructed using an
0N/AApache mod_proxy frontend and any number of backend webservers.
0N/A<
P>The reverse proxy is configured using the
0N/A<
A HREF="#proxypass">ProxyPass</
A> and <
A 0N/AHREF="#proxypassreverse">ProxyPassReverse</
A> directives. Caching can be
0N/Aenabled using mod_cache as with the forward proxy.
0N/A<
H2><
A NAME="access">Controlling access to your proxy</
A></
H2>
0N/AYou can control who can access your proxy via the normal <Directory>
0N/Acontrol block using the following example:<
P>
0N/A<Directory proxy:*>
0N/ADeny from [machines you'd like *not* to allow by IP address or name]
0N/AAllow from [machines you'd like to allow by IP address or name]
0N/AA <Files> block will also work, and is the only method known to work
0N/Afor all possible URLs in Apache versions earlier than 1.2b10.<
P>
0N/AWhen configuring a reverse proxy, access control takes on the attributes of
0N/Athe normal server <
Directory> configuration.
0N/A<!--<H2><A NAME="shortname">Using Netscape hostname shortcuts</A></H2> 0N/AThere is an optional patch to the proxy module to allow Netscape-like 0N/Ahostname shortcuts to be used. It's available from the 0N/A<
H2><
A NAME="mimetypes">Why doesn't file type <
EM>xxx</
EM> download via FTP?</
A></
H2>
0N/AYou probably don't have that particular file type defined as
0N/Afile. A useful line can be<
P>
0N/A<
H2><
A NAME="type">How can I force an FTP ASCII download of File <
EM>xxx</
EM>?</
A></
H2>
0N/AIn the rare situation where you must download a specific file using the FTP
0N/A<
STRONG>ASCII</
STRONG> transfer method (while the default transfer is in
0N/A<
STRONG>binary</
STRONG> mode), you can override mod_proxy's default by
0N/Asuffixing the request with <
SAMP>;type=a</
SAMP> to force an ASCII transfer.<
P>
0N/A<
H2><
A NAME="startup">Why does Apache start more slowly when using the
0N/A proxy module?</
A></
H2>
0N/AIf you're using the <
CODE>ProxyBlock</
CODE>
0N/Adirective, hostnames' IP addresses are looked up and cached during
0N/Astartup for later match test. This may take a few seconds (or more)
0N/Adepending on the speed with which the hostname lookups occur.<
P>
0N/A<!--<H2><A NAME="socks">Can I use the Apache proxy module with my SOCKS proxy?</A></H2> 0N/AYes. Just build Apache with the rule <CODE>SOCKS4=yes</CODE> in your 0N/A<EM>Configuration</EM> file, and follow the instructions there. SOCKS5 0N/Acapability can be added in a similar way (there's no <CODE>SOCKS5</CODE> 0N/Arule yet), so use the <CODE>EXTRA_LDFLAGS</CODE> definition, or build Apache 0N/Anormally and run it with the <EM>runsocks</EM> wrapper provided with SOCKS5, 0N/Aif your OS supports dynamically linked libraries.<P> 0N/ASome users have reported problems when using SOCKS version 4.2 on Solaris. 0N/AThe problem was solved by upgrading to SOCKS 4.3.<P> 0N/ARemember that you'll also have to grant access to your Apache proxy machine by 0N/Apermitting connections on the appropriate ports in your SOCKS daemon's 0N/A<
H2><
A NAME="intranet">What other functions are useful for an intranet proxy server?</
A></
H2>
0N/A<
P>An Apache proxy server situated in an intranet needs to forward external
0N/Arequests through the company's firewall. However, when it has to access
0N/Aresources within the intranet, it can bypass the firewall when accessing
0N/Ahosts. The <
A HREF="#noproxy">NoProxy</
A> directive is useful for specifying
0N/Awhich hosts belong to the intranet and should be accessed directly.</
P>
0N/A<
P>Users within an intranet tend to omit the local domain name from their
0N/Aaway with this and simply serve the request, implying a configured
0N/Alocal domain. When the <
A HREF="#proxydomain">ProxyDomain</
A> directive
0N/Ais used and the server is <
A HREF="#proxyrequests">configured for
0N/Aproxy service</
A>, Apache can return a redirect response and send the client
0N/Ato the correct, fully qualified, server address. This is the preferred method
0N/Asince the user's bookmark files will then contain fully qualified hosts.</
P>
0N/A<
H2><
A NAME="proxyrequests">ProxyRequests</
A> directive</
H2>
0N/A><
STRONG>Syntax:</
STRONG></
A> ProxyRequests on|off<
BR>
0N/A><
STRONG>Default:</
STRONG></
A> <
CODE>ProxyRequests Off</
CODE><
BR>
0N/A><
STRONG>Context:</
STRONG></
A> server config, virtual host<
BR>
0N/A><
STRONG>Override:</
STRONG></
A> <
EM>Not applicable</
EM><
BR>
0N/A><
STRONG>Status:</
STRONG></
A> Base<
BR>
0N/A><
STRONG>Module:</
STRONG></
A> mod_proxy<
BR>
0N/A><
STRONG>Compatibility:</
STRONG></
A> ProxyRequests is only available in
0N/AApache 1.1 and later.<
P>
0N/AThis allows or prevents Apache from functioning as a forward proxy
0N/Aserver. (Setting ProxyRequests to 'off' does not disable use of the <
A 0N/AHREF="#proxypass">ProxyPass</
A> directive.)
0N/A<
P>In a typical reverse proxy configuration, this option should be set to
0N/A<
H2><
A NAME="proxyremote">ProxyRemote</
A> directive</
H2>
0N/A><
STRONG>Syntax:</
STRONG></
A> ProxyRemote <
EM>match remote-server</
EM><
BR>
0N/A><
STRONG>Default:</
STRONG></
A> <
EM>None</
EM><
BR>
0N/A><
STRONG>Context:</
STRONG></
A> server config, virtual host<
BR>
0N/A><
STRONG>Override:</
STRONG></
A> <
EM>Not applicable</
EM><
BR>
0N/A><
STRONG>Status:</
STRONG></
A> Base<
BR>
0N/A><
STRONG>Module:</
STRONG></
A> mod_proxy<
BR>
0N/A><
STRONG>Compatibility:</
STRONG></
A> ProxyRemote is only available in
0N/AApache 1.1 and later.<
P>
0N/AThis defines remote proxies to this proxy. <
em>match</
em> is either the
0N/Aname of a URL-scheme that the remote server supports, or a partial URL
0N/Afor which the remote server should be used, or '*' to indicate the
0N/Aserver should be contacted for all requests. <
em>remote-server</
em> is a
0N/Apartial URL for the remote server. Syntax:
0N/A remote-server = protocol://hostname[:port]
0N/A<
em>protocol</
em> is the protocol that should be used to communicate
0N/Awith the remote server; only "http" is supported by this module.
0N/AIn the last example, the proxy will forward FTP requests, encapsulated
0N/Aas yet another HTTP proxy request, to another proxy which can handle
0N/A<
P>This option also supports reverse proxy configuration - a backend webserver
0N/Acan be embedded within a virtualhost URL space even if that server is hidden
0N/Aby another forward proxy.
0N/A<
H2><
A NAME="proxypass">ProxyPass</
A> directive</
H2>
0N/A><
STRONG>Syntax:</
STRONG></
A> ProxyPass <
EM>path url</
EM><
BR>
0N/Aor: ProxyPass <
EM>url</
EM> when placed in a <location> directive <
em>(Apache 2.0 only)</
EM><
br>
0N/Aor: ProxyPass <
EM>path !</
EM> to exclude a path from being proxied.
0N/A><
STRONG>Default:</
STRONG></
A> <
EM>None</
EM><
BR>
0N/A><
STRONG>Context:</
STRONG></
A> server config, virtual host<
BR>
0N/A><
STRONG>Override:</
STRONG></
A> <
EM>Not applicable</
EM><
BR>
0N/A><
STRONG>Status:</
STRONG></
A> Base<
BR>
0N/A><
STRONG>Module:</
STRONG></
A> mod_proxy<
BR>
0N/A><
STRONG>Compatibility:</
STRONG></
A> ProxyPass is only available in
0N/AApache 1.1 and later.<
P>
0N/AThis directive allows remote servers to be mapped into the space of the local
0N/Aserver; the local server does not act as a proxy in the conventional sense,
0N/Abut appears to be a mirror of the remote server. <
em>path</
em> is the name of
0N/Aa local virtual path; <
em>url</
em> is a partial URL for the remote server.
0N/Awill cause a local request for the
0N/Ainternally converted into a proxy request to
0N/AThe ! directive is usefull in situations where you don't want to reverse-proxy
0N/A<
H2><
A NAME="proxypassreverse">ProxyPassReverse</
A> directive</
H2>
0N/A><
STRONG>Syntax:</
STRONG></
A> ProxyPassReverse <
EM>path url</
EM><
BR>
0N/Aor: ProxyPassReverse <
EM>url</
EM> when placed in a <location> directive <
em>(Apache 2.0 only)</
em><
br>
0N/A><
STRONG>Default:</
STRONG></
A> <
EM>None</
EM><
BR>
0N/A><
STRONG>Context:</
STRONG></
A> server config, virtual host<
BR>
0N/A><
STRONG>Override:</
STRONG></
A> <
EM>Not applicable</
EM><
BR>
0N/A><
STRONG>Status:</
STRONG></
A> Base<
BR>
0N/A><
STRONG>Module:</
STRONG></
A> mod_proxy<
BR>
0N/A><
STRONG>Compatibility:</
STRONG></
A> ProxyPassReverse is only available in
0N/AApache 1.3b6 and later.<
P>
0N/AThis directive lets Apache adjust the URL in the <
TT>Location</
TT>,
0N/A<
TT>Content-Location</
TT> and <
TT>URI</
TT> headers on
0N/AHTTP redirect responses. This is essential when Apache is used as
0N/Aa reverse proxy to avoid by-passing the reverse proxy because of HTTP
0N/Aredirects on the backend servers which stay behind the reverse proxy.
0N/A<
em>path</
em> is the name of a local virtual path.<
BR>
0N/A<
em>url</
em> is a partial URL for the remote server - the same way they are
0N/Aused for the <
TT>ProxyPass</
TT> directive.
0N/Awill not only cause a local request for the
0N/Afunctionality <
SAMP>ProxyPass</
SAMP> provides here). It also takes care of
0N/Aredirect response to the client.
0N/ANote that this <
SAMP>ProxyPassReverse</
SAMP> directive can also be used in
0N/Aconjunction with the proxy pass-through feature ("<
SAMP>RewriteRule ...
0N/A><
TT>mod_rewrite</
TT></
A> because its doesn't depend on a corresponding
0N/A<
SAMP>ProxyPass</
SAMP> directive.
0N/A<
H2><
A NAME="allowconnect">AllowCONNECT</
A> directive</
H2>
0N/A><
STRONG>Syntax:</
STRONG></
A> AllowCONNECT <
EM>port</
EM>
0N/A [<
em>port</
em>] ...<
BR>
0N/A><
STRONG>Default:</
STRONG></
A> <
EM><
SAMP>AllowCONNECT</
SAMP> 443 563</
EM><
BR>
0N/A><
STRONG>Context:</
STRONG></
A> server config, virtual host<
BR>
0N/A><
STRONG>Override:</
STRONG></
A> <
EM>Not applicable</
EM><
BR>
0N/A><
STRONG>Status:</
STRONG></
A> Base<
BR>
0N/A><
STRONG>Module:</
STRONG></
A> mod_proxy<
BR>
0N/A><
STRONG>Compatibility:</
STRONG></
A> <
SAMP>AllowCONNECT</
SAMP> is only
0N/Aavailable in Apache 1.3.2 and later.<
P>
0N/AThe <
SAMP>AllowCONNECT</
SAMP> directive specifies a list of port numbers
0N/Ato which the proxy <
SAMP>CONNECT</
SAMP> method may connect.
0N/AToday's browsers use this method when a <
EM>https</
EM> connection
0N/Ais requested and proxy tunneling over <
EM>http</
EM> is in effect.<
BR>
0N/ABy default, only the default https port (443) and the default
0N/Asnews port (563) are enabled. Use the <
SAMP>AllowCONNECT</
SAMP>
0N/Adirective to overrride this default and allow connections to the
0N/A<
H2><
A NAME="proxyblock">ProxyBlock</
A> directive</
H2>
0N/A><
STRONG>Syntax:</
STRONG></
A> ProxyBlock *|<
EM>word|host|domain</
EM>
0N/A [<
em>word|host|domain</
em>] ...<
BR>
0N/A><
STRONG>Default:</
STRONG></
A> <
EM>None</
EM><
BR>
0N/A><
STRONG>Context:</
STRONG></
A> server config, virtual host<
BR>
0N/A><
STRONG>Override:</
STRONG></
A> <
EM>Not applicable</
EM><
BR>
0N/A><
STRONG>Status:</
STRONG></
A> Base<
BR>
0N/A><
STRONG>Module:</
STRONG></
A> mod_proxy<
BR>
0N/A><
STRONG>Compatibility:</
STRONG></
A> ProxyBlock is only available in
0N/AApache 1.2 and later.<
P>
0N/AThe ProxyBlock directive specifies a list of words, hosts
and/
or domains,
0N/Aseparated by spaces. HTTP, HTTPS, and FTP document requests to sites whose
0N/Anames contain matched words, hosts or domains are <
EM>blocked</
EM> by the
0N/Aproxy server. The proxy module will also attempt to determine IP addresses of
0N/Alist items which may be hostnames during startup, and cache them for match
0N/Atest as well. Example:
Note that 'wotsamattau' would also be sufficient to match '
wotsamattau.edu'.<
P>
blocks connections to all sites.
<
H2><
A NAME="proxyreceivebuffersize">ProxyReceiveBufferSize</
A> directive</
H2>
><
STRONG>Syntax:</
STRONG></
A> ProxyReceiveBufferSize <
EM>bytes</
EM><
BR>
><
STRONG>Default:</
STRONG></
A> <
EM>None</
EM><
BR>
><
STRONG>Context:</
STRONG></
A> server config, virtual host<
BR>
><
STRONG>Override:</
STRONG></
A> <
EM>Not applicable</
EM><
BR>
><
STRONG>Status:</
STRONG></
A> Base<
BR>
><
STRONG>Module:</
STRONG></
A> mod_proxy<
BR>
><
STRONG>Compatibility:</
STRONG></
A> ProxyReceiveBufferSize is only available in
The ProxyReceiveBufferSize directive specifies an explicit network buffer size
for outgoing HTTP and FTP connections, for increased throughput. It has to be
greater than 512 or set to 0 to indicate that the system's default buffer size
ProxyReceiveBufferSize 2048
<
H2><
A NAME="proxymaxforwards">ProxyMaxForwards</
A> directive</
H2>
><
STRONG>Syntax:</
STRONG></
A> ProxyMaxForwards <
EM>bytes</
EM><
BR>
><
STRONG>Default:</
STRONG></
A> <
EM>10</
EM><
BR>
><
STRONG>Context:</
STRONG></
A> server config, virtual host<
BR>
><
STRONG>Override:</
STRONG></
A> <
EM>Not applicable</
EM><
BR>
><
STRONG>Status:</
STRONG></
A> Base<
BR>
><
STRONG>Module:</
STRONG></
A> mod_proxy<
BR>
><
STRONG>Compatibility:</
STRONG></
A> ProxyMaxForwards is only available in
The ProxyMaxForwards directive specifies the maximum number of proxies
through which a request may pass. This is set to prevent infinite proxy
<
H2><
A NAME="noproxy">NoProxy</
A> directive</
H2>
><
STRONG>Syntax:</
STRONG></
A> NoProxy
<
A HREF="#domain"><
EM>Domain</
EM></
A>|<
A HREF="#subnet"><
EM>SubNet</
EM></
A>|<
A HREF="#ipaddr"><
EM>IpAddr</
EM></
A>|<
A HREF="#hostname"><
EM>Hostname</
EM></
A>
[<
A HREF="#domain"><
EM>Domain</
EM></
A>|<
A HREF="#subnet"><
EM>SubNet</
EM></
A>|<
A HREF="#ipaddr"><
EM>IpAddr</
EM></
A>|<
A HREF="#hostname"><
EM>Hostname</
EM></
A>] ...<
BR>
><
STRONG>Default:</
STRONG></
A> <
EM>None</
EM><
BR>
><
STRONG>Context:</
STRONG></
A> server config, virtual host<
BR>
><
STRONG>Override:</
STRONG></
A> <
EM>Not applicable</
EM><
BR>
><
STRONG>Status:</
STRONG></
A> Base<
BR>
><
STRONG>Module:</
STRONG></
A> mod_proxy<
BR>
><
STRONG>Compatibility:</
STRONG></
A> NoProxy is only available in
This directive is only useful for Apache proxy servers within intranets.
The NoProxy directive specifies a list of subnets, IP addresses, hosts
and/
or domains, separated by spaces. A request to a host which matches
one or more of these is always served directly, without forwarding to
the configured ProxyRemote proxy server(s).
The arguments to the NoProxy directive are one of the following type list:
<!-- ===================== Domain ======================= --> <
DD>A <
EM>Domain</
EM> is a partially qualified DNS domain name, preceded
It represents a list of hosts which logically belong to the same DNS
domain or zone (<
EM>
i.e.</
EM>, the suffixes of the hostnames are all ending in
To distinguish <
EM>Domain</
EM>s from <
A HREF="#hostname"><
EM>Hostname</
EM></
A>s (both
syntactically and semantically; a DNS domain can have a DNS A record,
too!), <
EM>Domain</
EM>s are always written
with a leading period.<
BR>
Note: Domain name comparisons are done without regard to the case,
and <
EM>Domain</
EM>s are always assumed to be anchored in the root
of the DNS tree, therefore two domains <
SAMP>
.MyDomain.com</
SAMP> and
considered equal. Since a domain comparison does not involve a DNS
lookup, it is much more efficient than subnet comparison.
<!-- ===================== SubNet ======================= --> <
DD>A <
EM>SubNet</
EM> is a partially qualified internet address in
numeric (dotted quad) form, optionally followed by a slash and the
netmask, specified as the number of significant bits in the
<
EM>SubNet</
EM>. It is used to represent a subnet of hosts which can
be reached over a common network interface. In the absence of the
explicit net mask it is assumed that omitted (or zero valued)
trailing digits specify the mask. (In this case, the netmask can
only be multiples of 8 bits wide.)<
BR>
<
DT><
SAMP>192.168</
SAMP> or <
SAMP>192.168.0.0</
SAMP>
<
DD>the subnet 192.168.0.0 with an implied netmask of 16 valid bits
(sometimes used in the netmask form <
SAMP>255.255.0.0</
SAMP>)
valid bits (also used in the form 255.255.248.0)
As a degenerate case, a <
EM>SubNet</
EM> with 32 valid bits is the
equivalent to an <
EM>IPAddr</
EM>, while a <
EM>SubNet</
EM> with zero
valid bits (<
EM>
e.g.</
EM>, 0.0.0.0/0) is the same as the constant
<
EM>_Default_</
EM>, matching any IP address.
<!-- ===================== IPAddr ======================= --> <
DD>A <
EM>IPAddr</
EM> represents a fully qualified internet address in
numeric (dotted quad) form. Usually, this address represents a
host, but there need not necessarily be a DNS domain name
connected with the address.<
BR>
Example: 192.168.123.7<
BR>
Note: An <
EM>IPAddr</
EM> does not need to be resolved by the DNS
system, so it can result in more effective apache performance.
<
P><
STRONG>See Also:</
STRONG>
<!-- ===================== Hostname ======================= --> <
DT><
EM>Hostname</
EM></
A>
<
DD>A <
EM>Hostname</
EM> is a fully qualified DNS domain name which can
be resolved to one or more <
A HREF="#ipaddr"><
EM>IPAddrs</
EM></
A> via the DNS domain name service.
It represents a logical host (in contrast to
<
A HREF="#domain"><
EM>Domain</
EM></
A>s, see
above) and must be resolvable to at least one <
A HREF="#ipaddr"><
EM>IPAddr</
EM></
A> (or often to a list of hosts
with different <
A HREF="#ipaddr"><
EM>IPAddr</
EM></
A>'s).<
BR>
Note: In many situations, it is more effective to specify an
<
A HREF="#ipaddr"><
EM>IPAddr</
EM></
A> in place of a
<
EM>Hostname</
EM> since a DNS lookup
can be avoided. Name resolution in Apache can take a remarkable deal
of time when the connection to the name server uses a slow PPP
Note: <
EM>Hostname</
EM> comparisons are done without regard to the case,
and <
EM>Hostname</
EM>s are always assumed to be anchored in the root
<
P><
STRONG>See Also:</
STRONG>
<
H2><
A NAME="proxydomain">ProxyDomain</
A> directive</
H2>
><
STRONG>Syntax:</
STRONG></
A> ProxyDomain <
EM>Domain</
EM><
BR>
><
STRONG>Default:</
STRONG></
A> <
EM>None</
EM><
BR>
><
STRONG>Context:</
STRONG></
A> server config, virtual host<
BR>
><
STRONG>Override:</
STRONG></
A> <
EM>Not applicable</
EM><
BR>
><
STRONG>Status:</
STRONG></
A> Base<
BR>
><
STRONG>Module:</
STRONG></
A> mod_proxy<
BR>
><
STRONG>Compatibility:</
STRONG></
A> ProxyDomain is only available in
This directive is only useful for Apache proxy servers within intranets.
The ProxyDomain directive specifies the default domain which the apache
proxy server will belong to. If a request to a host without a domain name
is encountered, a redirection response to the same host
with the configured <
EM>Domain</
EM> appended will be generated.
<
H2><
A NAME="proxyvia">ProxyVia</
A> directive</
H2>
><
STRONG>Syntax:</
STRONG></
A> ProxyVia on|off|full|block<
BR>
><
STRONG>Default:</
STRONG></
A> <
EM>ProxyVia off</
EM><
BR>
><
STRONG>Context:</
STRONG></
A> server config, virtual host<
BR>
><
STRONG>Override:</
STRONG></
A> <
EM>Not applicable</
EM><
BR>
><
STRONG>Status:</
STRONG></
A> Base<
BR>
><
STRONG>Module:</
STRONG></
A> mod_proxy<
BR>
><
STRONG>Compatibility:</
STRONG></
A> ProxyVia is only available in
Apache 1.3.2 and later.<
P>
This directive controls the use of the <
SAMP>Via:</
SAMP> HTTP header
by the proxy. Its intended use is to control the flow of of proxy
requests along a chain of proxy servers.
See RFC2068 (
HTTP/
1.1) for an explanation of <
SAMP>Via:</
SAMP> header lines.<
UL>
<
LI>If set to <
EM>off</
EM>, which is the default, no special
processing is performed. If a request or reply contains a <
SAMP>Via:</
SAMP> header,
it is passed through unchanged.
<
LI>If set to <
EM>on</
EM>, each request and reply will get a <
SAMP>Via:</
SAMP> header
line added for the current host.
<
LI>If set to <
EM>full</
EM>, each generated <
SAMP>Via:</
SAMP> header line will
additionally have the Apache server version shown as a <
SAMP>Via:</
SAMP> comment field.
<
LI>If set to <
EM>block</
EM>, every proxy request will have all its
<
SAMP>Via:</
SAMP> header lines removed. No new <
SAMP>Via:</
SAMP> header will be generated.
<
H2><
A NAME="proxyerroroverride">ProxyErrorOverride</
A> directive</
H2>
><
STRONG>Syntax:</
STRONG></
A> ProxyErrorOverride<
EM>on</
EM><
BR>
><
STRONG>Default:</
STRONG></
A> <
EM>off</
EM><
BR>
><
STRONG>Context:</
STRONG></
A> server config, virtual host<
BR>
><
STRONG>Override:</
STRONG></
A> <
EM>Not applicable</
EM><
BR>
><
STRONG>Status:</
STRONG></
A> Base<
BR>
><
STRONG>Module:</
STRONG></
A> mod_proxy<
BR>
><
STRONG>Compatibility:</
STRONG></
A> ProxyErrorOverride
This directive is usefull for reverse-proxy setups, where you wan't to
have a common look and feel on the error pages seen by the end user.
This also allows for included files (via mod_include's SSI) to get
the error code and act accordingly. (default behavior would display
the error page of the proxied server, turning this on shows the SSI