X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Fappendix.html;h=40b6c863f0852f93e8cd2f037cd96b61ccb0064c;hp=2c05d840d524d7e06996876a201a4b58fc23ffac;hb=07710938efbece9c2c3f6d4b5ccf6f66d1396f1b;hpb=46174e1f222d671ce9aab072e6174499756911ed diff --git a/doc/webserver/user-manual/appendix.html b/doc/webserver/user-manual/appendix.html index 2c05d840..40b6c863 100644 --- a/doc/webserver/user-manual/appendix.html +++ b/doc/webserver/user-manual/appendix.html @@ -7,14 +7,17 @@ NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.79"> +HREF="../p_doc.css"> Privoxy 3.0.7 User ManualPrivoxy 3.0.11 User Manual

14.2. Privoxy's Internal Pages

  • - 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:

    Short cuts. Turn off, then on:

  • Privoxy - Enable @@ -1019,7 +1030,7 @@ TARGET="_top" >

  • Privoxy - Disable @@ -1028,7 +1039,7 @@ TARGET="_top" >

  • Privoxy - Toggle Privoxy (Toggles between enabled and disabled) @@ -1225,19 +1236,6 @@ CLASS="QUOTE" >

  • 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 any 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 @@ -1444,7 +1450,8 @@ CLASS="GUIBUTTON" >[ Edit ] - {+deanimate-gifs {last} + {+change-x-forwarded-for{block} + +deanimate-gifs {last} +fast-redirects {check-decoded-url} +filter {refresh-tags} +filter {img-reorder} @@ -1452,7 +1459,6 @@ CLASS="GUIBUTTON" +filter {webbugs} +filter {jumping-windows} +filter {ie-exploits} - +hide-forwarded-for-headers +hide-from-header {block} +hide-referrer {forge} +session-cookies-only @@ -1631,6 +1637,7 @@ CLASS="SCREEN" -add-header -block + +change-x-forwarded-for{block} -client-header-filter{hide-tor-exit-notation} -content-type-overwrite -crunch-client-header @@ -1672,24 +1679,18 @@ CLASS="SCREEN" -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 -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
    We'll just show the interesting part here - the explicit matches. It is matched three different times. Two "+block""+block{}" sections, and a "+block +handle-as-image""+block{} +handle-as-image", which is the expanded form of one of our aliases that had been defined as: "+block""+block{}" 
    
 { +block +handle-as-image }
+>
 { +block{Path starts with "ads".} +handle-as-image }
  /ads
    ".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.