Included additional examples of how to configure the upstream proxy

support for more selective proxying.
This commit is contained in:
Robert James Kaes 2003-06-02 21:56:00 +00:00
parent 91e082671a
commit 7f8e4647f7

View File

@ -97,26 +97,31 @@ PidFile "/var/run/tinyproxy.pid"
#
# For example:
# # connection to test domain goes through testproxy
# upstream testproxy:8008 .test.domain.invalid
# upstream testproxy:8008 .our_testbed.example.com
# upstream testproxy:8008 ".test.domain.invalid"
# upstream testproxy:8008 ".our_testbed.example.com"
# upstream testproxy:8008 "192.168.128.0/255.255.254.0"
#
# # no upstream proxy for internal websites and unqualified hosts
# no upstream .internal.example.com
# no upstream www.example.com
# no upstream .
# no upstream ".internal.example.com"
# no upstream "www.example.com"
# no upstream "10.0.0.0/8"
# no upstream "192.168.0.0/255.255.254.0"
# no upstream "."
#
# # connection to these boxes go through their DMZ firewalls
# upstream cust1_firewall:8008 testbed_for_cust1
# upstream cust2_firewall:8008 testbed_for_cust2
# upstream cust1_firewall:8008 "testbed_for_cust1"
# upstream cust2_firewall:8008 "testbed_for_cust2"
#
# # default upstream is internet firewall
# upstream firewall.internal.example.com:80
#
# The LAST matching rule wins the route decision. As you can see, you
# can use a host, or a domain:
# name matches host exactly
# .name matches any host in domain "name"
# . matches any host with no domain (in 'empty' domain)
# name matches host exactly
# .name matches any host in domain "name"
# . matches any host with no domain (in 'empty' domain)
# IP/bits matches network/mask
# IP/mask matches network/mask
#
#Upstream some.remote.proxy:port