X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Fappendix.html;h=d9aceac93161910bbe86363a07d407e93e96fa83;hb=9adfbd2f4dd6acc1d92f00d46d18a16e8dfd5f1b;hp=4a9c95b60f4cf63f0e8d50b6769b2dcbff842e55;hpb=a5b1999794b4b0faa68812c0b8b2861316ae8341;p=privoxy.git diff --git a/doc/webserver/user-manual/appendix.html b/doc/webserver/user-manual/appendix.html index 4a9c95b6..d9aceac9 100644 --- a/doc/webserver/user-manual/appendix.html +++ b/doc/webserver/user-manual/appendix.html @@ -7,7 +7,7 @@ NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ ">Privoxy 3.1.1 User ManualPrivoxy 3.0.4 User Manual

14. Appendix

14. Appendix

14.1. Regular Expressions

14.1. Regular Expressions

PCRE and - PCRSPCRS libraries.

If you are reading this, you probably don't understand what

14.2. 14.2. Privoxy's Internal Pages

@@ -818,7 +825,9 @@ CLASS="APPLICATION" editing of actions files:

@@ -836,7 +845,9 @@ TARGET="_top" Show the source code version numbers:

@@ -854,7 +865,9 @@ TARGET="_top" Show the browser's request headers:

@@ -872,7 +885,9 @@ TARGET="_top" Show which actions apply to a URL and why:

@@ -894,7 +909,9 @@ CLASS="QUOTE" to run, but only as a pass-through proxy, with no actions taking place:

@@ -909,7 +926,9 @@ TARGET="_top" > Short cuts. Turn off, then on:

@@ -921,7 +940,9 @@ TARGET="_top"

@@ -942,7 +963,9 @@ CLASS="SECT3" >

14.2.1. Bookmarklets

14.2.1. Bookmarklets

Below are some

  • Privoxy - Submit Actions File Feedback -

  • Privoxy - Why?

    14.3. Chain of Events

    14.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 default.filter) are processed against the buffered - content. Filters are applied in the order they are specified in the - default.filter file. Animated GIFs, if present, are - reduced to either the first or last frame, depending on the action +> and any other filter files) are + processed against the buffered content. Filters are applied in the order + they are specified in one of the filter files. Animated GIFs, if present, + are reduced to either the first or last frame, depending on the action setting.The entire page, which is now filtered, is then sent by

    14.4. Anatomy of an Action

    14.4. Anatomy of an Action

    The way "+filter" action) from - the default.filter file since this is handled very + one of the filter files since this is handled very differently and not so easy to trap! It also will not tell you about any other URLs that may be embedded within the URL you are testing. For instance, images such as ads are expressed as URLs within the raw page source of HTML pages. So @@ -1378,7 +1390,8 @@ HREF="http://google.com" TARGET="_top" >google.com, - and look at it one section at a time:

    [ Edit ] -{-add-header - -block - -crunch-outgoing-cookies - -crunch-incoming-cookies - +deanimate-gifs{last} - -downgrade-http-version - +fast-redirects - -filter{popups} - -filter{fun} - -filter{shockwave-flash} - -filter{crude-parental} - +filter{html-annoyances} - +filter{js-annoyances} - +filter{content-cookies} - +filter{webbugs} - +filter{refresh-tags} - +filter{nimda} - +filter{banners-by-size} - +hide-forwarded-for-headers - +hide-from-header{block} - +hide-referer{forge} - -hide-user-agent - -handle-as-image - -kill-popups - -limit-connect - +prevent-compression - -send-vanilla-wafer - -send-wafer - +session-cookies-only - +set-image-blocker{pattern} } + {-add-header + -block + -content-type-overwrite + -crunch-client-header + -crunch-if-none-match + -crunch-incoming-cookies + -crunch-outgoing-cookies + -crunch-server-header + +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-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 } .google.com @@ -1449,7 +1487,7 @@ CLASS="GUIBUTTON" >

    This tells us how we have defined our +> This is telling us how we have defined our "actions", and - which ones match for our example, "google.com". The first listing +>. + Displayed is all the actions that are available to us. Remember, + the + sign denotes "on". - + denotes "off". So some are "on" here, but many + are "off". Each example we try may provide a slightly different + end result, depending on our configuration directives.

    The first listing is any matches for the standard.action"+session-cookies-only" - (i.e. not persistent). So we will allow persistent cookies for google. The - second turns Then, for our user.action file, we again have no hits.

    file, we again have no hits. + So there is nothing google-specific that we might have added to our own, local + configuration.

    And finally we pull it all together in the bottom section and summarize how Final results: - -add-header - -block - -crunch-outgoing-cookies - -crunch-incoming-cookies - +deanimate-gifs{last} - -downgrade-http-version - -fast-redirects - -filter{popups} - -filter{fun} - -filter{shockwave-flash} - -filter{crude-parental} - +filter{html-annoyances} - +filter{js-annoyances} - +filter{content-cookies} - +filter{webbugs} - +filter{refresh-tags} - +filter{nimda} - +filter{banners-by-size} - +hide-forwarded-for-headers - +hide-from-header{block} - +hide-referer{forge} - -hide-user-agent - -handle-as-image - -kill-popups - -limit-connect - +prevent-compression - -send-vanilla-wafer + -add-header + -block + -content-type-overwrite + -crunch-client-header + -crunch-if-none-match + -crunch-incoming-cookies + -crunch-outgoing-cookies + -crunch-server-header + +deanimate-gifs {last} + -downgrade-http-version + -fast-redirects + +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-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} and "session-cookies-only", + which are actived specifically for this site in our configuration, + and thus show in the "Final Results".

    Now another example, {-add-header - -block - -crunch-incoming-cookies - -crunch-outgoing-cookies + -block + -content-type-overwrite + -crunch-client-header + -crunch-if-none-match + -crunch-incoming-cookies + -crunch-outgoing-cookies + -crunch-server-header +deanimate-gifs -downgrade-http-version - +fast-redirects + +fast-redirects{check-decoded-url} +filter{html-annoyances} +filter{js-annoyances} +filter{kill-popups} @@ -1731,17 +1819,27 @@ CLASS="GUIBUTTON" +filter{banners-by-size} +filter{hal} +filter{fun} + -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-referer{forge} -hide-user-agent - -handle-as-image + -inspect-jpegs +kill-popups + -overwrite-last-modified +prevent-compression + -redirect -send-vanilla-wafer -send-wafer +session-cookies-only - +set-image-blocker{blank} } + +set-image-blocker{blank} + -treat-forbidden-connects-like-blocks } / { +block +handle-as-image } @@ -1757,23 +1855,24 @@ CLASS="QUOTE" > is matching "/ads"! But - we did not want this at all! Now we see why we get the blank page. We could - now add a new action below this that explicitly does in our + configuration! But we did not want this at all! Now we see why we get the + blank page. We could now add a new action below this that explicitly + notun - block ( blocks ("{-block}") paths with ) paths with + "adsl". There are - various ways to handle such exceptions. Example:

    in them (remember, last match in the configuration wins). + There are various ways to handle such exceptions. Example: