Использование локального прокси со списком заблокированных сайтов

8.4. Patterns
As mentioned, Privoxy uses "patterns" to determine what actions might apply to which sites and pages your browser attempts to access. These "patterns" use wild card type pattern matching to achieve a high degree of flexibility. This allows one expression to be expanded and potentially match against many similar patterns.
Generally, an URL pattern has the form <host><port>/<path>, where the <host>, the <port> and the <path> are optional. (This is why the special / pattern matches all URLs). Note that the protocol portion of the URL pattern (e.g. http://) should not be included in the pattern. This is assumed already!
The pattern matching syntax is different for the host and path parts of the URL. The host part uses a simple globbing type matching technique, while the path part uses more flexible "Regular Expressions" (POSIX 1003.2).
The port part of a pattern is a decimal port number preceded by a colon (:). If the host part contains a numerical IPv6 address, it has to be put into angle brackets (<, >).
www.example.com/
is a host-only pattern and will match any request to www.example.com, regardless of which document on that server is requested. So ALL pages in this domain would be covered by the scope of this action. Note that a simple example.com is different and would NOT match.
www.example.com
means exactly the same. For host-only patterns, the trailing / may be omitted.
www.example.com/index.html
matches all the documents on www.example.com whose name starts with /index.html.
www.example.com/index.html$
matches only the single document /index.html on www.example.com.
/index.html$
matches the document /index.html, regardless of the domain, i.e. on any web server anywhere.
/
Matches any URL because there's no requirement for either the domain or the path to match anything.
:8000/
Matches any URL pointing to TCP port 8000.
10.0.0.1/
Matches any URL with the host address 10.0.0.1. (Note that the real URL uses plain brackets, not angle brackets.)
<2001:db8::1>/
Matches any URL with the host address 2001:db8::1. (Note that the real URL uses plain brackets, not angle brackets.)
index.html
matches nothing, since it would be interpreted as a domain name and there is no top-level domain called .html. So its a mistake.
8.4.1. The Host Pattern
The matching of the host part offers some flexible options: if the host pattern starts or ends with a dot, it becomes unanchored at that end. The host pattern is often referred to as domain pattern as it is usually used to match domain names and not IP addresses. For example:
.example.com
matches any domain with first-level domain com and second-level domain example. For example www.example.com, example.com and foo.bar.baz.example.com. Note that it wouldn't match if the second-level domain was another-example.
www.
matches any domain that STARTS with www. (It also matches the domain www but most of the time that doesn't matter.)
.example.
matches any domain that CONTAINS .example.. And, by the way, also included would be any files or documents that exist within that domain since no path limitations are specified. (Correctly speaking: It matches any FQDN that contains example as a domain.) This might be www.example.com, news.example.de, or www.example.net/cgi/testing.pl for instance. All these cases are matched.
Additionally, there are wild-cards that you can use in the domain names themselves. These work similarly to shell globbing type wild-cards: "*" represents zero or more arbitrary characters (this is equivalent to the "Regular Expression" based syntax of ".*"), "?" represents any single character (this is equivalent to the regular expression syntax of a simple "."), and you can define "character classes" in square brackets which is similar to the same regular expression technique. All of this can be freely mixed:
ad*.example.com
matches "adserver.example.com", "ads.example.com", etc but not "sfads.example.com"
*ad*.example.com
matches all of the above, and then some.
.?pix.com
matches www.ipix.com, pictures.epix.com, a.b.c.d.e.upix.com etc.
www[1-9a-ez].example.c*
matches www1.example.com, www4.example.cc, wwwd.example.cy, wwwz.example.com etc., but not wwww.example.com.
While flexible, this is not the sophistication of full regular expression based syntax.
When compiled with FEATURE_PCRE_HOST_PATTERNS patterns can be prefixed with "PCRE-HOST-PATTERN:" in which case full regular expression (PCRE) can be used for the host pattern as well.
8.4.2. The Path Pattern
Privoxy uses "modern" POSIX 1003.2 "Regular Expressions" for matching the path portion (after the slash), and is thus more flexible.
There is an Appendix with a brief quick-start into regular expressions, you also might want to have a look at your operating system's documentation on regular expressions (try man re_format).
Note that the path pattern is automatically left-anchored at the "/", i.e. it matches as if it would start with a "^" (regular expression speak for the beginning of a line).
Please also note that matching in the path is CASE INSENSITIVE by default, but you can switch to case sensitive at any point in the pattern by using the "(?-i)" switch: www.example.com/(?-i)PaTtErN.* will match only documents whose path starts with PaTtErN in exactly this capitalization.
.example.com/.*
Is equivalent to just ".example.com", since any documents within that domain are matched with or without the ".*" regular expression. This is redundant
.example.com/.*/index.html$
Will match any page in the domain of "example.com" that is named "index.html", and that is part of some path. For example, it matches "www.example.com/testing/index.html" but NOT "www.example.com/index.html" because the regular expression called for at least two "/'s", thus the path requirement. It also would match "www.example.com/testing/index_html", because of the special meta-character ".".
.example.com/(.*/)?index\.html$
This regular expression is conditional so it will match any page named "index.html" regardless of path which in this case can have one or more "/'s". And this one must contain exactly ".html" (and end with that!).
.example.com/(.*/)(ads|banners?|junk)
This regular expression will match any path of "example.com" that contains any of the words "ads", "banner", "banners" (because of the "?") or "junk". The path does not have to end in these words, just contain them. The path has to contain at least two slashes (including the one at the beginning).
.example.com/(.*/)(ads|banners?|junk)/.*\.(jpe?g|gif|png)$
This is very much the same as above, except now it must end in either ".jpg", ".jpeg", ".gif" or ".png". So this one is limited to common image formats.
There are many, many good examples to be found in default.action, and more tutorials below in Appendix on regular expressions.