X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=default.filter;h=94110cc445c5607d24118c48d07e30fc7c6729d9;hb=fc9872444692d52f3f15341bdab3f95f49388106;hp=b5ca574463ac4cf2ad1735afe2dc26b2d42f89d3;hpb=93065fa0aef98a889c27ddc0b9f1b08632ef388e;p=privoxy.git diff --git a/default.filter b/default.filter index b5ca5744..94110cc4 100644 --- a/default.filter +++ b/default.filter @@ -2,7 +2,7 @@ # # File : $Source: /cvsroot/ijbswa/current/default.filter,v $ # -# $Id: default.filter,v 1.77 2010/02/05 21:41:31 fabiankeil Exp $ +# $Id: default.filter,v 1.82 2011/06/23 14:04:29 fabiankeil Exp $ # # Purpose : Rules to process the content of web pages # @@ -128,15 +128,15 @@ s/(open\s*\([^\)]+always(?:raised|lowered)=)(["']?)(?:yes|1)\2/$1$2no$2/sigU ################################################################################# # -# js-events: Kill all JS event bindings and timers (Radically destructive! Only for extra nasty sites). +# js-events: Kill JavaScript event bindings and timers (Radically destructive! Only for extra nasty sites). # ################################################################################# -FILTER: js-events Kill all JS event bindings and timers (Radically destructive! Only for extra nasty sites). +FILTER: js-events Kill JavaScript event bindings and timers (Radically destructive! Only for extra nasty sites). s/(on|event\.)((mouse(over|out|down|up|move))|(un)?load|contextmenu|selectstart)/never/ig # Not events, but abused on the same type of sites: s/(alert|confirm)\s*\(/concat(/ig -s/settimeout\(/concat(/ig +s/set(timeout|interval)\(/concat(/ig ################################################################################# # @@ -603,7 +603,7 @@ s@@\n\n$0@ # Are these ids still in use? @@ -764,6 +767,34 @@ CLIENT-HEADER-TAGGER: css-requests Tags detected CSS requests as "CSS-REQUEST". s@^Accept:\s*text/css.*@CSS-REQUEST@i +################################################################################# +# +# range-requests: Tags range requests as "RANGE-REQUEST". +# +# By default Privoxy removes Range headers for requests to +# ressources that will be filtered to make sure the filters +# get the whole picture. Otherwise Range requests could be +# intentionally used to circumvent filters or, less likely, +# filtering a partial response may damage it because it matched +# a pattern that the ressource as a whole wouldn't. +# +# Range requests can be useful and save bandwidth so instead +# of removing Range headers for requests to ressources that +# will be filtered, you may prefer to simply disable filtering +# for those requests. +# +# That's what this tagger is all about. After enabling it, +# you can disable filtering for range requests using the following +# action section: +# +# {-filter -deanimate-gifs} +# TAG:^RANGE-REQUEST +# +################################################################################# +CLIENT-HEADER-TAGGER: range-requests Tags range requests as "RANGE-REQUEST". + +s@^Range:.*@RANGE-REQUEST@i + ################################################################################# # # client-ip-address: Tags the request with the client's IP address.