1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
|
# Forwarding specification for Internet Junkbuster 2.0
#
# Copyright 1997-8 Junkbusters Corp. For distribution, modification and use
# under the GNU General Public License. These files come with NO WARRANTY.
# See http://www.junkbusters.com/ht/en/gpl.html or README file for details.
#
# This feature allows routing of HTTP requests via multiple proxies.
# It can be used to better protect privacy and confidentiality when
# accessing specific domains by routing requests to those domains
# to a special purpose filtering proxy such as lpwa.com
#
# It can also be used in an environmnent with multiple networks to route
# requests via multiple gateways allowing transparent access to multiple
# networks without having to modify browser configurations.
#
# Also specified here are special gateway protocols such as SOCKS.
# The syntax of each line is
#
# target_domain[:port][/path] forwarding_domain[:port] gateway_type gateway_domain[:port]
#
# A '.' in the forwarding domain/port means that requests made to the
# target domain are not forwarded but are made directly by the proxy
# (though the proxy may still use a gateway to contact the server)
#
# Lines are checked in turn, and the last match wins.
#
# There is an implicit line equivalent to the following, which specifies that
# anything not finding a match on the list is to go out without forwarding
# or gateway protocol; like so:
#
# * . . . # implicit
# In this fictitious example, everything goes via an ISP's caching proxy,
# except requests to that ISP:
#
# * caching.myisp.net:8000 . .
# myisp.net . . .
# In this example direct connections are made to all "internal" domains,
# but everything else goes through Lucent's LPWA by way of the company's
# SOCKS gateway to the Internet.
#
# * lpwa.com:8000 socks argyle.my_company.com:1080
# my_company.com . . .
# This is how you could set up a site that always uses SOCKS but no forwarders
#
# * . socks knee.my_company.com:1080
# An advanced example for network administrators.
#
# If you're in a situation where you have links to multiple
# ISP's that provide various special content to their subscribers
# you can configure forwarding to pass requests to the specific
# host that's connected to that ISP so that everybody can see
# all of the content on all of the ISP's.
# (whew! how's that for a run-on sentence?)
#
# This is tricky, but here's a sample:
#
# host-a has a PPP connection to isp-a.com
# host-b has a PPP connection to isp-b.com
# host-a can run an Internet Junkbusters with forwarding like this:
#
# / . . .
# isp-b.com host-b:8000 . .
#
# host-b can run an Internet Junkbusters with forwarding like this:
# / . . .
# isp-a.com host-a:8000 . .
#
# Now, *anyone* on the Internet (including users on host-a and host-b)
# can set their browser's proxy to *either* host-a or host-b and
# be able to browse the content on isp-a or isp-b.
|
