X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fcontacting.sgml;h=a75197d0b023c9c4b93485d7ba1471ee3808a223;hp=331b5981db15f0b05a70a2a421c50d449ce22ce5;hb=6b6d7c96a8e264bac0f95e4403fc728a464e11b9;hpb=b6eb803479b021093fc609b6205a7ace767f4ff7 diff --git a/doc/source/contacting.sgml b/doc/source/contacting.sgml index 331b5981..a75197d0 100644 --- a/doc/source/contacting.sgml +++ b/doc/source/contacting.sgml @@ -3,9 +3,9 @@ Purpose : Entity included in other project documents. - $Id: contacting.sgml,v 2.41 2014/12/19 12:30:38 fabiankeil Exp $ + $Id: contacting.sgml,v 2.46 2017/01/23 13:03:06 fabiankeil Exp $ - Copyright (C) 2001-2011 Privoxy Developers http://www.privoxy.org/ + Copyright (C) 2001-2011 Privoxy Developers https://www.privoxy.org/ See LICENSE. ====================================================================== @@ -58,7 +58,7 @@ If you aren't using the latest Privoxy version, the problem may have been found and fixed in the meantime. We would appreciate if you could take the time - to upgrade + to upgrade to the latest version and verify that the problem still exists. @@ -128,22 +128,25 @@ is being used and the following debug options are enabled (all of them): - debug 1 # Log the destination for each request Privoxy let through. See also debug 1024. + debug 1 # Log the destination for each request Privoxy let through. + # See also debug 1024. debug 2 # show each connection status debug 4 # show I/O status debug 8 # show header parsing debug 128 # debug redirects debug 256 # debug GIF de-animation debug 512 # Common Log Format -debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why. +debug 1024 # Log the destination for requests Privoxy didn't let through, + # and the reason why. debug 4096 # Startup banner and warnings. -debug 8192 # Non-fatal errors +debug 8192 # Non-fatal errors +debug 65536 # Log applying actions If you are having trouble with a filter, please additionally enable debug 64 # debug regular expression filters - If you are using Privoxy 3.0.17 or later and suspect that it interprets the - request or the response incorrectly, please enable + If you suspect that Privoxy interprets the request or the response + incorrectly, please enable debug 32768 # log all data read from the network @@ -189,7 +192,7 @@ debug 8192 # Non-fatal errors - The appendix + The appendix of the Privoxy User Manual also has helpful information on understanding actions, and action debugging. @@ -197,7 +200,7 @@ debug 8192 # Non-fatal errors Get Support All users are welcome to discuss their issues on the users + url="https://lists.privoxy.org/mailman/listinfo/privoxy-users">users mailing list, where the developers also hang around. @@ -305,6 +308,9 @@ users list. Technically interested users and people who wish to 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. @@ -315,8 +321,7 @@ including list archives, at: SourceForge support trackers may be used as well, but have various technical problems that are unlikely to be fixed anytime soon. If you don't get a timely response, please try the - mailing list as well. While it's hosted at SourceForge as well, it usually - works as expected. + mailing list as well.