]*?)\sping=(['"]?)([^"'>]+)\2([>\s]?)@\
#################################################################################
FILTER: google CSS-based block for Google text ads. Also removes a width limitation and the toolbar advertisement.
-s@@\n$0@
# Are these ids still in use?
s@(]*) id=(["']?)ads_[^\2]*\2@$1 class="msn_ads"@Uig
@@ -764,6 +776,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.
@@ -773,6 +813,16 @@ CLIENT-HEADER-TAGGER: client-ip-address Tags the request with the client's IP ad
s@^\w*\s+.*\s+HTTP/\d\.\d\s*@IP-ADDRESS: $origin@D
+#################################################################################
+#
+# listen-address: Tags the request with the listen-address on which the request
+# came in.
+#
+#################################################################################
+CLIENT-HEADER-TAGGER: listen-address Tags the request with the listen-address on which the request came in.
+
+s@^\w*\s+.*\s+HTTP/\d\.\d\s*@LISTEN-ADDRESS: $listen-address@D
+
#################################################################################
#
# http-method: Tags the request with its HTTP method.
@@ -809,6 +859,15 @@ CLIENT-HEADER-TAGGER: user-agent Tags the request with the complete User-Agent h
s@^User-Agent:.*@$0@i
+#################################################################################
+#
+# referer: Tags the request with the complete Referer header.
+#
+#################################################################################
+CLIENT-HEADER-TAGGER: referer Tags the request with the complete Referer header.
+
+s@^Referer:.*@$0@i
+
#################################################################################
#
# content-type: Tags the request with the content type declared by the server.