From 797ddff0b98384c2033537b283c9e6e43fba8df3 Mon Sep 17 00:00:00 2001
From: Fabian Keil The first step is to join the developer's mailing list. You can submit your ideas, or even
- better patches. Patches are best submitted to the Sourceforge tracker
- set up for this purpose, but can be sent to the list for review
+ "https://lists.privoxy.org/mailman/listinfo/privoxy-devel" target=
+ "_top">privoxy-devel mailing list. You can submit your ideas, or
+ even better patches. Patches are best submitted to the Sourceforge
+ tracker set up for this purpose, but can be sent to the list for review
too. You will also need to have a cvs package installed, which will
diff --git a/doc/webserver/developer-manual/newrelease.html b/doc/webserver/developer-manual/newrelease.html
index 4b18f1ec..92906b0a 100644
--- a/doc/webserver/developer-manual/newrelease.html
+++ b/doc/webserver/developer-manual/newrelease.html
@@ -978,7 +978,7 @@
When all (or: most of the) packages have been uploaded and made
available, send an email to the announce
+ "mailto:privoxy-announce@lists.privoxy.org" target="_top">announce
mailing list, Subject: "Version X.Y.Z available for download". Be
sure to include the If you wish to receive an email notification whenever we release
updates of Privoxy or the actions
file, subscribe to our announce mailing list,
- ijbswa-announce@lists.sourceforge.net.
All users are welcome to discuss their issues on the users mailing list, where the developers also hang around.
@@ -313,7 +313,11 @@ contribute to the project are always welcome on the developers list. You can find an overview of all Privoxy-related mailing lists, including list - archives, at: https://lists.privoxy.org/mailman/listinfo. The lists + hosted on privoxy.org have been created in 2016, the previously-used + lists hosted at SourceForge are deprecated but the archives may still + be useful: https://sourceforge.net/mail/?group_id=11118.Copyright © 2001-2016 by Privoxy Developers <ijbswa-developers@lists.sourceforge.net>
Some source code is based on code Copyright © 1997 by Anonymous Coders and Junkbusters, Inc. and licensed under the Privoxy.
Privoxy is free software; you can
redistribute it and/or modify it under the terms of the
A long time ago, there was the Internet
Junkbuster, by Anonymous Coders and Junkbusters Corporation.
diff --git a/doc/webserver/faq/general.html b/doc/webserver/faq/general.html
index 5b79f04c..1b07e511 100644
--- a/doc/webserver/faq/general.html
+++ b/doc/webserver/faq/general.html
@@ -498,12 +498,12 @@
lists. So first thing, subscribe to the Privoxy Users or the Privoxy Developers mailing list, join the
- discussion, help out other users, provide general feedback or report
- problems you noticed. If you intend to help out with the trackers, you also might want
to Privoxy has stopped working.
- Chances are that the site suffers from a bug in PHP, which results in empty pages being sent
- if the client explicitly requests an uncompressed page, like
- Privoxy does. This bug has been fixed
- in PHP 4.2.3. To find out if this is in fact the source of the problem, try adding
- the site to a -prevent-compression section in
- user.action: If that works, you may also want to report the problem to the site's
- webmasters, telling them to use zlib.output_compression instead of
- ob_gzhandler in their PHP applications (workaround) or upgrade to PHP
- 4.2.3 or later (fix). This may be the result of an overly aggressive filter. The filters
@@ -489,7 +452,7 @@ Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua
This is probably a manifestation of the "100%
@@ -598,7 +561,7 @@ Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua
It's probably due to compression. It is a common practice for web
@@ -629,7 +592,7 @@ Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua
Please report the problem to the creator of your selinux
@@ -700,7 +663,7 @@ Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua
Privoxy marks sockets as tainted
@@ -756,6 +719,28 @@ Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua
problem that may be worth fixing, the problem will be explicitly logged
as error. This can happen if your custom filters require more memory than
+ Privoxy is allowed to use. Usually the
+ problem is that the operating system enforces a stack size limit that
+ isn't sufficient. Unless the problem occurs with the filters available in the default
+ configuration, this is not considered a Privoxy bug. To prevent the crashes you can rewrite your filter to use less
+ ressources, increase the relevant memory limit or recompile pcre to use
+ less stack space. For details please see the pcrestack man page and the documentation of your operating
+ system.7.2. History
+ 7.2. History
5.11. I get a
- completely blank page at one site. "View
- Source" shows only: <html><body></body></html>.
- Without Privoxy the page loads fine.
-
-
-
-
-
-
-
-
-
- # Make exceptions for ill-behaved sites:
- #
- {-prevent-compression}
- .example.com
-
- 5.12. My logs
+
5.11. My logs
show many "Unable to get my own hostname"
lines. Why?
@@ -448,7 +411,7 @@ Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua
5.13. When I try to launch
+
5.12. When I try to launch
Privoxy, I get an error message "port 8118 is
already in use" (or similar wording). Why?
@@ -464,7 +427,7 @@ Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua
5.14. Pages
+
5.13. Pages
with UTF-8 fonts are garbled.
5.15. Why
+
5.14. Why
are binary files (such as images) corrupted when Privoxy is
used?
@@ -502,7 +465,7 @@ Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua
5.16. What
+
5.15. What
is the "demoronizer" and why is it
there?
@@ -530,7 +493,7 @@ Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua
5.17. Why do I
+
5.16. Why do I
keep seeing "PrivoxyWindowOpen()" in raw
source code?
@@ -551,7 +514,7 @@ Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua
5.18. I am getting
+
5.17. I am getting
too many DNS errors like "404 No Such
Domain". Why can't Privoxy do this better?
@@ -579,7 +542,7 @@ Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua
5.19. At one site
+
5.18. At one site
Privoxy just hangs, and starts taking all CPU. Why is this?
5.20. I just
+
5.19. I just
installed Privoxy, and all my browsing has slowed to a crawl. What
gives?
@@ -612,7 +575,7 @@ Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua
5.21. Why do
+
5.20. Why do
my filters work on some sites but not on others?
5.22. On
+
5.21. On
some HTTPS sites my browser warns me about unauthenticated content, the
URL bar doesn't get highlighted and the lock symbol appears to be
broken. What's going on?
@@ -675,7 +638,7 @@ Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua
5.23. I get selinux
+
5.22. I get selinux
error messages. How can I fix this?
5.24. I
+
5.23. I
compiled Privoxy with Gentoo's portage
and it appears to be very slow. Why?
@@ -723,7 +686,7 @@ Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua
5.25.
+
5.24.
What are tainted sockets and how do I prevent them?
5.25. After adding my custom filters, Privoxy crashes when visitting certain
+ websites
+
+
Table 1. Default Configurations
diff --git a/doc/webserver/user-manual/appendix.html b/doc/webserver/user-manual/appendix.html index e31e01c6..080718e5 100644 --- a/doc/webserver/user-manual/appendix.html +++ b/doc/webserver/user-manual/appendix.html @@ -313,7 +313,7 @@Privoxy main page:
+Privoxy main page:
Show information about the current configuration, including - viewing and editing of actions files:
+ viewing and editing of actions files:
- -
Show the source code version numbers:
+Show the source code version numbers:
- -
Show the browser's request headers:
+Show the browser's request headers:
- -
Show which actions apply to a URL and why:
+Show which actions apply to a URL and why:
"off", "Privoxy" continues to run, but only as a pass-through proxy, with no actions taking place:
+ "AEN5916" id="AEN5916">-Short cuts. Turn off, then on:
+Short cuts. Turn off, then on:
-+
Whether or not Privoxy should use IP addresses specified + with the X-Forwarded-For header
+0 or one
+0
+Warning | +
+ This is an experimental feature. The syntax is + likely to change in future versions. + |
+
If clients reach Privoxy through another proxy, for example + a load balancer, Privoxy can't tell the client's IP address + from the connection. If multiple clients use the same proxy, + they will share the same client tag settings which is usually + not desired.
+ +This option lets Privoxy use the X-Forwarded-For header + value as client IP address. If the proxy sets the header, + multiple clients using the same proxy do not share the same + client tag settings.
+ +This option should only be enabled if Privoxy can only be + reached through a proxy and if the proxy can be trusted to set + the header correctly. It is recommended that ACL are used to + make sure only trusted systems can reach Privoxy.
+ +If access to Privoxy isn't limited to trusted systems, this + option would allow malicious clients to change the client tags + for other clients or increase Privoxy's memory requirements by + registering lots of client tag settings for clients that don't + exist.
+
+ + # Allow systems that can reach Privoxy to provide the client + # IP address with a X-Forwarded-For header. + trust-x-forwarded-for 1 + |