1 ######################################################################
5 # Purpose : Trustfiles are an experimental feature and can be used
6 # to build "whitelists" (versus the usual "blacklists"
9 # Copyright : Written by and Copyright
10 # Privoxy team. https://www.privoxy.org/
12 # Based on the Internet Junkbuster originally written
13 # by and Copyright (C) 1997 Anonymous Coders and
14 # Junkbusters Corporation. http://www.junkbusters.com
16 # We value your feedback. However, to provide you with the best support,
19 # * Use the support forum to get help:
20 # https://sourceforge.net/p/ijbswa/support-requests/
21 # * Submit bugs only thru our bug forum:
22 # https://sourceforge.net/p/ijbswa/bugs/
23 # Make sure that the bug has not already been submitted. Please try
24 # to verify that it is a Privoxy bug, and not a browser or site
25 # bug first. If you are using your own custom configuration, please
26 # try the stock configs to see if the problem is a configuration
27 # related bug. And if not using the latest development snapshot,
28 # please try the latest one. Or even better, git sources.
29 # * Submit feature requests only thru our feature request tracker:
30 # https://sourceforge.net/p/ijbswa/feature-requests/
32 # For any other issues, feel free to use the mailing lists.
33 # Anyone interested in actively participating in development and related
34 # discussions can join the appropriate mailing list here:
35 # https://lists.privoxy.org/mailman/listinfo. Archives are available
38 ######################################################################
40 # Sample Trustfile for Privoxy
42 # For this file to have any effect, the line in the main config file beginning
43 # with "trustfile" must be uncommented, with the name of this file following the
46 # Trustfiles are an experimental feature used for building "whitelists"
47 # of "trusted" sites (versus the usual "blacklists" technique). For more
48 # detail, see https://www.privoxy.org/user-manual/config.html#TRUSTFILE.
50 # List trusted domains here. The default is to block any URL that is NOT
51 # referenced. Access to trusted domains includes all paths within that
54 # Preceding a domain with a '+' character will designate that domain
55 # as a "trusted referrer", meaning any requests whose HTTP "Referer" headers
56 # contain an URL from that domain will be allowed, and the previously untrusted
57 # host will be dynamically added to this file. Thus, this builds a "white-list"
58 # of hosts the user is allowed to visit.
60 # Note this means that the file will grow with use!
62 # Also note that you can only trust referrers if you control the user's
63 # system and make sure that there are no programs available that allow
64 # to set arbitrary headers.
66 # Preceding the domain with '~' character allows access to that domain only
67 # (including all paths within that domain), but does not allow access to links
68 # to other, outside domains. Sites that are added dynamically by trusted
69 # referrers will include the '~' character, and thus do not become trusted
70 # referrers themselves.
72 # Example: to allow example.com and to white-list domains that appear to
73 # be reached through links from example.com, uncomment this line:
77 # The next two lines make sure that the user can access Privoxy's
78 # CGI pages, without automatically trusting their links.