Since
- Toggle Privoxy on or off. In this case, config file. When toggled "off", "Privoxy" continues
- to run, but only as a pass-through proxy, with no actions taking place:
+>
+ continues to run, but only as a pass-through proxy, with no actions taking
+ place:
Below are some Privoxy - Enable
@@ -1019,7 +1030,7 @@ TARGET="_top"
> Privoxy - Disable
@@ -1028,7 +1039,7 @@ TARGET="_top"
> Privoxy - Toggle Privoxy (Toggles between enabled and disabled)
@@ -1070,14 +1081,15 @@ CLASS="SECT2"
CLASS="SECT2"
>14.3. Chain of Events14.3. Chain of Events Let's take a quick look at the basic sequence of events when a web page is
- requested by your browser and Let's take a quick look at how some of Privoxy is on duty: Now the web server starts sending its response back (i.e. typically a web page and related
- data).
+> Now the web server starts sending its response back (i.e. typically a web
+ page).
If the "+kill-popups"
- action applies, and it is an HTML or JavaScript document, the popup-code in the
- response is filtered on-the-fly as it is received.
- If a If any "+filter"
+> action
or back to your browser.
If neither If neither a "+filter"
+> action
or As the browser receives the now (possibly filtered) page content, it
reads and then requests any URLs that may be embedded within the page
source, e.g. ad images, stylesheets, JavaScript, other HTML documents (e.g.
- frames), sounds, etc. For each of these objects, the browser issues a new
- request. And each such request is in turn processed as above. Note that a
- complex web page may have many such embedded URLs.
+ frames), sounds, etc. For each of these objects, the browser issues a
+ separate request (this is easily viewable in Privoxy's
+ logs). And each such request is in turn processed just as above. Note that a
+ complex web page will have many, many such embedded URLs. If these
+ secondary requests are to a different server, then quite possibly a very
+ differing set of actions is triggered.
14.2. Privoxy's Internal Pages
14.2. Privoxy's Internal Pages Short cuts. Turn off, then on:
14.2.1. Bookmarklets14.2.1. Bookmarklets
- is then checked and if it does not match, an
+ and
+ "+handle-as-empty-document"
+ are then checked, and if there is no match, an
HTML "BLOCKED" page is sent back. Otherwise, if it does match,
- an image is returned. The type of image depends on the setting of page is sent back to the browser. Otherwise, if
+ it does match, an image is returned for the former, and an empty text
+ document for the latter. The type of image would depend on the setting of
+
NOTE: This is somewhat of a simplistic overview of what happens with each URL + request. For the sake of brevity and simplicity, we have focused on + Privoxy's core features only.
The way the Bookmarklets section on a quick and easy way to do this (be sure to flush caches afterward!). Looking at the - logs is a good idea too.
config file settings, and may need to be + turned "on".)Another easy troubleshooting step to try is if you have done any customization of your installation, revert back to the installed @@ -1410,7 +1440,7 @@ WIDTH="100%" >
Matches for http://google.com:
+> Matches for http://www.google.com:
In file: default.action [ Edit ]
- {-add-header
- -block
- -content-type-overwrite
- -crunch-client-header
- -crunch-if-none-match
- -crunch-incoming-cookies
- -crunch-outgoing-cookies
- -crunch-server-header
+ {+change-x-forwarded-for{block}
+deanimate-gifs {last}
- -downgrade-http-version
+fast-redirects {check-decoded-url}
- -filter {js-events}
- -filter {content-cookies}
- -filter {all-popups}
- -filter {banners-by-link}
- -filter {tiny-textforms}
- -filter {frameset-borders}
- -filter {demoronizer}
- -filter {shockwave-flash}
- -filter {quicktime-kioskmode}
- -filter {fun}
- -filter {crude-parental}
- -filter {site-specifics}
- -filter {js-annoyances}
- -filter {html-annoyances}
+filter {refresh-tags}
- -filter {unsolicited-popups}
+filter {img-reorder}
+filter {banners-by-size}
+filter {webbugs}
+filter {jumping-windows}
+filter {ie-exploits}
- -filter {google}
- -filter {yahoo}
- -filter {msn}
- -filter {blogspot}
- -filter {xml-to-html}
- -filter {html-to-xml}
- -filter-client-headers
- -filter-server-headers
- -force-text-mode
- -handle-as-empty-document
- -handle-as-image
- -hide-accept-language
- -hide-content-disposition
- +hide-forwarded-for-headers
+hide-from-header {block}
- -hide-if-modified-since
+hide-referrer {forge}
- -hide-user-agent
- -inspect-jpegs
- -kill-popups
- -limit-connect
- -overwrite-last-modified
- +prevent-compression
- -redirect
- -send-vanilla-wafer
- -send-wafer
+session-cookies-only
+set-image-blocker {pattern}
- -treat-forbidden-connects-like-blocks }
/
{ -session-cookies-only }
@@ -1655,6 +1637,8 @@ CLASS="SCREEN"
-add-header
-block
+ +change-x-forwarded-for{block}
+ -client-header-filter{hide-tor-exit-notation}
-content-type-overwrite
-crunch-client-header
-crunch-if-none-match
@@ -1663,7 +1647,7 @@ CLASS="SCREEN"
-crunch-server-header
+deanimate-gifs {last}
-downgrade-http-version
- +fast-redirects {check-decoded-url}
+ -fast-redirects
-filter {js-events}
-filter {content-cookies}
-filter {all-popups}
@@ -1689,31 +1673,24 @@ CLASS="SCREEN"
-filter {yahoo}
-filter {msn}
-filter {blogspot}
- -filter {xml-to-html}
- -filter {html-to-xml}
- -filter-client-headers
- -filter-server-headers
+ -filter {no-ping}
-force-text-mode
-handle-as-empty-document
-handle-as-image
-hide-accept-language
-hide-content-disposition
- +hide-forwarded-for-headers
+hide-from-header {block}
-hide-if-modified-since
+hide-referrer {forge}
-hide-user-agent
- -inspect-jpegs
- -kill-popups
-limit-connect
-overwrite-last-modified
- +prevent-compression
+ -prevent-compression
-redirect
- -send-vanilla-wafer
- -send-wafer
+ -server-header-filter{xml-to-html}
+ -server-header-filter{html-to-xml}
-session-cookies-only
- +set-image-blocker {pattern}
- -treat-forbidden-connects-like-blocks
{ +block }
+>
{ +block{Domains starts with "ad"} }
ad*.
- { +block }
+ { +block{Domain contains "ad"} }
.ad.
- { +block +handle-as-image }
+ { +block{Doubleclick banner server} +handle-as-image }
.[a-vx-z]*.doubleclick.net
{ +block +handle-as-image }
+>
{ +block{Path starts with "ads".} +handle-as-image }
/adsImages that are inexplicably being blocked, may well be hitting the ".com". This will effectively match any TLD with +>). This will effectively match any TLD with google in it, such as mail.google.demail.google.de., just as an example.