X-Git-Url: http://www.privoxy.org/gitweb/%40user-manual%40%40actions-help-prefix%40HIDE-IF-MODIFIED-SINCE?a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Factions-file.html;h=9acdf9ed38a5466d62c35da199280a9f199cb938;hb=9def9517abf9440ecd38685ccd2aaa3638432084;hp=8c00ca93b28d73ed5192e80600c5483f1ffe5657;hpb=d1c39df48bd2a8953ceb49fdbb370b20f3d89422;p=privoxy.git diff --git a/doc/webserver/user-manual/actions-file.html b/doc/webserver/user-manual/actions-file.html index 8c00ca93..9acdf9ed 100644 --- a/doc/webserver/user-manual/actions-file.html +++ b/doc/webserver/user-manual/actions-file.html @@ -6,7 +6,7 @@
Privoxy 3.0.23 User Manual | +Privoxy 3.0.25 User Manual | ||||
---|---|---|---|---|---|
Warning | +
+ This is an experimental feature. The syntax is likely to + change in future versions. + |
+
Client tag patterns are not set based on HTTP headers but based on + the client's IP address. Users can enable them themselves, but the + Privoxy admin controls which tags are available and what their effect + is.
+ +After a client-specific tag has been defined with the client-specific-tag, directive, + action sections can be activated based on the tag by using a + CLIENT-TAG pattern. The CLIENT-TAG pattern is evaluated at the same + priority as URL patterns, as a result the last matching pattern wins. + Tags that are created based on client or server headers are evaluated + later on and can overrule CLIENT-TAG and URL patterns!
+ +The tag is set for all requests that come from clients that + requested it to be set. Note that "clients" are differentiated by IP + address, if the IP address changes the tag has to be requested + again.
+ +Clients can request tags to be set by using the CGI interface + http://config.privoxy.org/client-tags.
+ +Example:
+ +
+ +# If the admin defined the client-specific-tag circumvent-blocks, +# and the request comes from a client that previously requested +# the tag to be set, overrule all previous +block actions that +# are enabled based on URL to CLIENT-TAG patterns. +{-block} +CLIENT-TAG:^circumvent-blocks$ + +# This section is not overruled because it's located after +# the previous one. +{+block{Nobody is supposed to request this.}} +example.org/blocked-example-page ++ |
+
-+add-header{X-User-Tracking: sucks} +# Add a DNT ("Do not track") header to all requests, +# event to those that already have one. +# +# This is just an example, not a recommendation. +# +# There is no reason to believe that user-tracking websites care +# about the DNT header and depending on the User-Agent, adding the +# header may make user-tracking easier. +{+add-header{DNT: 1}} +/
Parameterized.
+Multi-value.
Parameterized.
+Multi-value.
Parameterized.
+Multi-value.
Parameterized.
+Multi-value.
Multi-value.
+Parameterized.
"forward-webserver + 127.0.0.1:80" to use the HTTP server listening at + 127.0.0.1 port 80 without adjusting the request + headers.
+ +This makes it more convenient to use Privoxy to make + existing websites available as onion services as well.
+ +Many websites serve content with hardcoded URLs and + can't be easily adjusted to change the domain based on the + one used by the client.
+ +Putting Privoxy between Tor and the webserver (or an + stunnel that forwards to the webserver) allows to rewrite + headers and content to make client and server happy at the + same time.
+ +Using Privoxy for webservers that are only reachable + through onion addresses and whose location is supposed to + be secret is not recommended and should not be necessary + anyway.
+Parameterized.
+Multi-value.
Parameterized.
+Multi-value.