| Privoxy 3.0.20 User Manual | +Privoxy 3.0.25 User Manual | ||||
|---|---|---|---|---|---|
- forward-socks5 / 127.0.0.1:9050 . + forward-socks5t / 127.0.0.1:9050 . |
|||||
Note that if you got Tor through one of the bundles, you may + have to change the port from 9050 to 9150 (or even another + one). For details, please check the documentation on the + Tor + website.
+The public Tor network can't be used to reach your local network, if you need to access local servers you therefore might want to make some @@ -2232,6 +2330,9 @@ HTTP connections into Privoxy.
+Note that intercepting encrypted connections (HTTPS) isn't + supported.
+Make sure that Privoxy's own requests aren't redirected as well. Additionally take care that Privoxy can't @@ -2491,8 +2592,8 @@ tolerate pipelining. Whether or not that improves performance mainly depends on the client configuration.
-This options is new and should be considered - experimental.
+If you are seeing problems with pages not properly loading, + disabling this option could work around the problem.
None
+128
Obviously using this option only makes sense if you choose a limit below the one enforced by the operating system.
+ +One most POSIX-compliant systems Privoxy can't properly deal with more than + FD_SETSIZE file descriptors at the same time and has to reject + connections if the limit is reached. This will likely change in + a future version, but currently this limit can't be increased + without recompiling Privoxy + with a different FD_SETSIZE limit.
This is a work-around for Firefox bug 492459: " Websites are no longer rendered if SSL requests for - JavaScripts are blocked by a proxy. " (https://bugzilla.mozilla.org/show_bug.cgi?id=492459) - As the bug has been fixed for quite some time this option - should no longer be needed and will be removed in a future - release. Please speak up if you have a reason why the option - should be kept around.
+This directive was added as a work-around for Firefox bug + 492459: "Websites are no longer rendered if + SSL requests for JavaScripts are blocked by a proxy." + (https://bugzilla.mozilla.org/show_bug.cgi?id=492459), + the bug has been fixed for quite some time, but this directive + is also useful to make it harder for websites to detect whether + or not resources are being blocked.
The name of a tag that will always be set for clients that + requested it through the webinterface.
+Tag name followed by a + description that will be shown in the webinterface
+None
+| Warning | +
|
+ This is an experimental feature. The syntax is + likely to change in future versions. + |
+
Client-specific tags allow Privoxy admins to create + different profiles and let the users chose which one they want + without impacting other users.
+ +One use case is allowing users to circumvent certain blocks + without having to allow them to circumvent all blocks. This is + not possible with the enable-remote-toggle + feature because it would bluntly disable all blocks for all + users and also affect other actions like filters. It also is + set globally which renders it useless in most multi-user + setups.
+ +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/show-client-tags. + The specific tag description is only used on the web page and + should be phrased in away that the user understand the effect + of the tag.
+
+ + # Define a couple of tags, the described effect requires action sections + # that are enabled based on CLIENT-TAG patterns. + client-specific-tag circumvent-blocks Overrule blocks but do not affect other actions + disable-content-filters Disable content-filters but do not affect other actions + ++ |
+
How long a temporarily enabled tag remains enabled.
+Time in seconds.
+60
+| Warning | +
|
+ This is an experimental feature. The syntax is + likely to change in future versions. + |
+
In case of some tags users may not want to enable them + permanently, but only for a short amount of time, for example + to circumvent a block that is the result of an overly-broad URL + pattern.
+ +The CGI interface http://config.privoxy.org/show-client-tags therefore + provides a "enable this tag temporarily" option. If it is used, + the tag will be set until the client-tag-lifetime is over.
+
+ + # Increase the time to life for temporarily enabled tags to 3 minutes + client-tag-lifetime 180 + ++ |
+