From: oes Date: Fri, 24 May 2002 00:17:26 +0000 (+0000) Subject: generated X-Git-Tag: v_3_0_branchpoint~14 X-Git-Url: http://www.privoxy.org/gitweb/@default-cgi@/faq/%22https:/static/diff?a=commitdiff_plain;h=80b13c5019d561424b3ed8224b6dc4e830e24f67;p=privoxy.git generated --- diff --git a/doc/webserver/user-manual/actions-file.html b/doc/webserver/user-manual/actions-file.html index bc85832d..ca87032f 100644 --- a/doc/webserver/user-manual/actions-file.html +++ b/doc/webserver/user-manual/actions-file.html @@ -4,8 +4,7 @@ >Actions Files

8.1. Finding the Right Mix

8.2. How to Edit

alias" sections which will be discussed later. For now - let's concentrate on regular sections: They have a heading line (often split - up to multiple lines for readability) which consist of a list of actions, - separated by whitespace and enclosed in curly braces. Below that, there - is a list of URL patterns, each on a separate line.

sections which will + be discussed later. For now let's concentrate on regular sections: They have a + heading line (often split up to multiple lines for readability) which consist + of a list of actions, separated by whitespace and enclosed in curly braces. + Below that, there is a list of URL patterns, each on a separate line.

To determine which actions apply to a request, the URL of the request is compared to all patterns in each action file file. Every time it matches, the list of applicable actions for the URL is incrementally updated, using the heading of the section in which the pattern is located. If multiple matches for the same URL set the same action differently, the last match wins. If not, - the effects are aggregated (e.g. a URL might match both the - { + +"+handle-as-image" - and handle-as-image }, + then later another one with just { + +"+block" actions). -

block }, resulting + in both actions to apply.

You can trace this process for any given URL by visiting

8.4.1. The Domain Pattern

8.4.2. The Path Pattern

(regular expression speak for the beginning of a line).

Please also note that matching in the path is case - Please also note that matching in the path is INSENSITIVE by default, but you can switch to case - sensitive at any point in the pattern by using the +>CASE INSENSITIVE + by default, but you can switch to case sensitive at any point in the pattern by using the "(?-i)" switch: - switch: www.example.com/(?-i)PaTtErN.* will match only - documents whose path starts with will match + only documents whose path starts with PaTtErN in @@ -969,10 +971,7 @@ CLASS="SECT3" CLASS="SECT3" >8.5.1. add-header8.5.1. add-header

8.5.2. block8.5.2. block

8.5.3. crunch-incoming-cookies8.5.3. crunch-incoming-cookies

8.5.4. crunch-outgoing-cookies8.5.4. crunch-outgoing-cookies

8.5.5. deanimate-gifs8.5.5. deanimate-gifs

8.5.6. downgrade-http-version8.5.6. downgrade-http-version

8.5.7. fast-redirects8.5.7. fast-redirects

8.5.8. filter8.5.8. filter

8.5.9. handle-as-image8.5.9. handle-as-image

8.5.10. hide-forwarded-for-headers8.5.10. hide-forwarded-for-headers

8.5.11. hide-from-header8.5.11. hide-from-header

8.5.12. hide-referrer8.5.12. hide-referrer8.5.13. hide-user-agent8.5.13. hide-user-agent

8.5.14. kill-popups8.5.14. kill-popups

8.5.15. limit-connect8.5.15. limit-connect

8.5.16. prevent-compression8.5.16. prevent-compression

8.5.17. send-vanilla-wafer8.5.17. send-vanilla-wafer

8.5.18. send-wafer8.5.18. send-wafer

8.5.19. session-cookies-only8.5.19. session-cookies-only

8.5.20. set-image-blocker8.5.20. set-image-blocker

8.5.21. Summary

8.7.1. default.action

8.7.2. user.action

Appendix

14.2. Privoxy
Short cuts. Turn off, then on:

The Main Configuration FilePrivoxy will bind to all interfaces (addresses) on your machine and may become reachable - from the Internet. In that case, consider using access control lists (ACL's) - (see "ACLs" below), or a firewall. + from the Internet. In that case, consider using access control lists (ACL's, see below), and/or + a firewall. +

If you open Privoxy to untrusted users, you will + also want to turn off the enable-edit-actions and + enable-remote-toggle + options!

7.4.5. ACLs: permit-access and deny-access

Privoxy Configuration

6.1. Controlling PrivoxyPrivoxy Copyright, License and History

12.1. License

The Filter File

9.1. Filter File Tutorial

Privoxy User Manual

$Id: user-manual.sgml,v 1.118 2002/05/21 04:54:55 hal9 Exp $

$Id: user-manual.sgml,v 1.121 2002/05/23 23:20:17 oes Exp $

2.1.1. Red Hat, SuSE and Conectiva RPMsRed Hat, SuSE RPMs and Conectiva
2.1.2.
5.1. RedHat, Conectiva and DebianRedHat and Conectiva
5.2. Debian
5.3. SuSE
5.3. 5.4. Windows
5.4. 5.5. Solaris, NetBSD, FreeBSD, HP-UX and others
5.5. 5.6. OS/2
5.6. 5.7. MAX OSX
5.7. 5.8. AmigaOS
5.8. 5.9. Command Line Options
6.1. Controlling Privoxy
8.1. Finding the Right Mix
8.2. How to Edit
22
8.4.1. The Domain Pattern
8.4.2. The Path Pattern
8.5.1. add-headeradd-header
8.5.2. blockblock
8.5.3. crunch-incoming-cookiescrunch-incoming-cookies
8.5.4. crunch-outgoing-cookiescrunch-outgoing-cookies
8.5.5. deanimate-gifsdeanimate-gifs
8.5.6. downgrade-http-versiondowngrade-http-version
8.5.7. fast-redirectsfast-redirects
8.5.8. filterfilter
8.5.9. handle-as-imagehandle-as-image
8.5.10. hide-forwarded-for-headershide-forwarded-for-headers
8.5.11. hide-from-headerhide-from-header
8.5.12. hide-referrerhide-referrer
8.5.13. hide-user-agenthide-user-agent
8.5.14. kill-popups
8.5.15. limit-connectlimit-connect
8.5.16. prevent-compressionprevent-compression
8.5.17. send-vanilla-wafersend-vanilla-wafer
8.5.18. send-wafersend-wafer
8.5.19. session-cookies-onlysession-cookies-only
8.5.20. set-image-blockerset-image-blocker
8.5.21. Summary
8.7.1. default.action
8.7.2. user.action
9.1. Filter File Tutorial
12.1. License
14.2. PrivoxyInstallation2.1.1. Red Hat, SuSE and Conectiva RPMs2.1.1. Red Hat, SuSE RPMs and Conectiva

RPMs can be installed with If you have problems with failed dependencies, try rebuilding the SRC RPM: rpm --rebuild privoxy-2.9.15-1.src.rpmrpm --rebuild privoxy-2.9.15-1.src.rpm;. This will use your locally installed libraries and RPM version.

2.1.2. Debian

FIXME.

DEBs can be installed with dpkg -i + privoxy_2.9.15-1.deb, and will use + /etc/privoxy for the location of configuration + files.

IntroductionQuickstart to Using Privoxypatterns that use - wildcards so they can apply potentially to a range of similar URLs.

When you connect to a website, the full path of the URL will either match one - of the "actions" as defined in - When you connect to a website, the full URL will either match one or more + of the sections as defined in Privoxy's configuration, or not. If so, then - configuration, + or not. If so, then Privoxy will perform the action accordingly. If - not, then nothing special happens. Futhermore, web pages may contain - embedded, secondary URLs that your web browser will display as it parses the +> will perform the + respective actions. If not, then nothing special happens. Futhermore, web + pages may contain embedded, secondary URLs that your web browser will + use to load additional components of the page, as it parses the original page's HTML content. An ad image for instance, is just a URL embedded in the page somewhere. The image itself may be on the same server, or a server somewhere else on the Internet. Complex web pages will have many such embedded URLs.

The actions we need to know about for ad blocking are: The actions we need to know about for ad blocking are: block, , handle-as-image, and , and + set-image-blocker:

  • blockblock - this action stops any contact between your browser and any URL patterns that match this action's configuration. It can be used for blocking ads, but also anything that is determined to be unwanted. By itself, it simply stops any - communication with the remote server. If this is the only action that - matches for this particular URL, then Privoxy will - display its own BLOCKED page to let you now what has happened. +>'s + own built-in BLOCKED page instead to let you now what has happened.

  • handle-as-imagehandle-as-image - - forces Privoxy to treat this URL as if it were - an image. to treat this URL as an image. + Privoxy knows about common image - types (e.g. GIF), but there are many situations where this does not apply. - So we'll force it. This is particularly important for ad blocking, since - once we can treat it as an image, we can make more intelligent decisisions - on how to handle it. There are some limitations to this though. For - instance, you can't just force an image substituion for an entire HTML page +>'s default configuration already does this + for all common image types (e.g. GIF), but there are many situations where this + is not as easy to determine. So we'll force it in these cases. This is particularly + important for ad blocking, since only if we know that it's an image, we can replace + it by an image instead of the BLOCKED page, which would only result in a + "broken image" icon. There are some limitations to this though. For + instance, you can't just brute-force an image substituion for an entire HTML page in most situations.

  • set-image-blocker - - tells set-image-blocker - tells + Privoxy what to display in place of - an ad image that has hit a block rule. For this to come into play, - the URL must match a block action somewhere in the configuration. - what to display in place of an ad image that + has hit a block rule. For this to come into play, the URL must match a + block action somewhere in the + configuration, And, it must also either be of a known image type, or - match an and, it must also match an + handle-as-image - action. +>handle-as-image action.

    The configuration options on what to display instead of the ad are: @@ -487,8 +502,8 @@ BORDER="0" >    http://<URL> - A redirect to any URL of the - user's choosing (advanced usage). +> - A redirect to any image anywhere + of the user's choosing (advanced usage). Privoxy editor at editor at http://config.privoxy.org/show-status

  • You should have an Actions section labeled +block. - If not, click the You should have a section with only + block listed under + "Actions:". + If not, click a "EditInsert new section below" button just - under the word "Actions". This will bring up a list of all - actions. Find block near the top, and click in the +> + button, and in the new section that just appeared, click the Edit button right under the word "Actions:". + This will bring up a list of all actions. Find + block near the top, and click + in the "Enabled" column, then - column, then "Submit" just below the list. +> + just below the list.

  • Now, in the +block actions section, click the - Now, in the block actions section, + click the ""Copy Link - LocationCopy Link Location". Remove the . + Remove the http:// at - the beginning of the URL. Then, click +> at the beginning of the URL. Then, click "Submit". +> (or + "OK" if in a pop-up window).

  • Actions Files Tutorial.

    . + The ideas explained thererin also apply to the web-based editor.

See AlsoStarting Privoxy

5.1. RedHat, Conectiva and Debian5.1. RedHat and Conectiva

We use a script. Note that RedHat does not start Privoxy upon booting per @@ -155,7 +154,7 @@ default. It will use the file /etc/privoxy/config as its -main configuration file. FIXME: Debian??

5.2. Debian

We use a script. Note that Debian starts Privoxy upon booting per + default. It will use the file + /etc/privoxy/config as its main configuration + file.

 # /etc/init.d/privoxy start

5.2. SuSE5.3. SuSE

We use a script. It will use the file 5.3. Windows5.4. Windows

Click on the Privoxy Icon to start Privoxy. If no configuration file is @@ -227,7 +257,7 @@ CLASS="SECT2" CLASS="SECT2" >5.4. Solaris, NetBSD, FreeBSD, HP-UX and others5.5. Solaris, NetBSD, FreeBSD, HP-UX and others

Example Unix startup command:

5.5. OS/25.6. OS/2

FIXME.

5.6. MAX OSX5.7. MAX OSX

FIXME.

5.7. AmigaOS5.8. AmigaOS

FIXME.

5.8. Command Line Options5.9. Command Line Options

TemplatesNote to Upgraders