X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=default.filter;h=72ec7a2e8d67de83c0bb2c7cc4a6273eeb5f802b;hb=48855b15032d5740544dcc004887c4cc9c63dee0;hp=041562f5badc58e44ce0058b0b3ea098c88f0f08;hpb=98a5edc74a94e212ae89590798fd1ec0e41d1656;p=privoxy.git diff --git a/default.filter b/default.filter index 041562f5..72ec7a2e 100644 --- a/default.filter +++ b/default.filter @@ -2,7 +2,7 @@ # # File : $Source: /cvsroot/ijbswa/current/default.filter,v $ # -# $Id: default.filter,v 1.76 2009/10/03 10:40:05 fabiankeil Exp $ +# $Id: default.filter,v 1.81 2011/06/23 13:58:53 fabiankeil Exp $ # # Purpose : Rules to process the content of web pages # @@ -177,15 +177,15 @@ s|||igU ################################################################################# # -# refresh-tags: Kill automatic refresh tags (for dial-on-demand setups). +# refresh-tags: Kill automatic refresh tags if refresh time is larger than 9 seconds. # ################################################################################# -FILTER: refresh-tags Kill automatic refresh tags (for dial-on-demand setups). +FILTER: refresh-tags Kill automatic refresh tags if refresh time is larger than 9 seconds. # Note: Only deactivates refreshes with more than 9 seconds delay to # preserve monster-stupid but common redirections via meta tags. # -s/\2]*))?\2/\2]*))?\2@@\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.