X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fcontacting.sgml;h=93d07f0f13d2f309dbf051e01fa245c4a8089224;hp=fd7c68ea1ea6f34ff49b8b66ef8feadecfe2fa54;hb=6252f95180ded7bb95477c31be144a61721594a4;hpb=6cb41778d4fe473b3aa421acbee208a99f2df27b diff --git a/doc/source/contacting.sgml b/doc/source/contacting.sgml index fd7c68ea..93d07f0f 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.7 2006/09/10 14:53:54 hal9 Exp $ + $Id: contacting.sgml,v 2.16 2010/02/14 17:59:31 fabiankeil Exp $ - Copyright (C) 2001 - 2006 Privoxy Developers http://privoxy.org + Copyright (C) 2001-2010 Privoxy Developers http://www.privoxy.org/ See LICENSE. ====================================================================== @@ -47,6 +47,26 @@ mailing list, where the developers also hang around. + + Please don't sent private support requests to individual Privoxy + developers, either use the mailing lists or the support trackers. + + + + Note that the Privoxy mailing lists are moderated. Posts from unsubscribed + addresses have to be accepted manually by a moderator. This may cause a + delay of several days and if you use a subject that doesn't clearly + mention Privoxy or one of its features, your message may be accidentally + discarded as spam. + + + + If you aren't subscribed, you should therefore spend a few seconds + to come up with a proper subject. Additionally you should make it clear + that you want to get CC'd. Otherwise some responses will be directed to + the mailing list only, and you won't see them. + + Reporting Problems @@ -95,8 +115,7 @@ Reporting Bugs - Please report all bugs only through our - bug tracker: + Please report all bugs through our bug tracker: http://sourceforge.net/tracker/?group_id=11118&atid=111118. @@ -105,24 +124,30 @@ and observe the additional hints at the top of the submit form. If already submitted, please feel free to add any info to the - original report that might help solve the issue. + original report that might help to solve the issue. - + Please try to verify that it is a Privoxy bug, - and not a browser or site bug first. If unsure, - try toggling + and not a browser or site bug or documented behaviour that just happens + to be different than what you expected. If unsure, + try toggling off Privoxy, and see if the problem persists. + + + If you are using your own custom configuration, please try the stock configs to see if the problem is configuration related. + If you're having problems with a feature that is disabled by default, + please ask around on the mailing list if others can reproduce the problem. - If not using the latest version, the bug may have been found + If you aren't using the latest Privoxy version, the bug may have been found and fixed in the meantime. We would appreciate if you could take the time to upgrade to the latest version (or even the latest CVS snapshot) and verify - your bug. + that your bug still exists. Please be sure to provide the following information: @@ -132,8 +157,9 @@ Please be sure to provide the following information: - The exact Privoxy version of the proxy software -(if you got the source from CVS, please also give the date). + The exact Privoxy version you are using + (if you got the source from CVS, please also provide the source code revisions + as shown in http://config.privoxy.org/show-version). @@ -141,7 +167,9 @@ Please be sure to provide the following information: The operating system and versions you run Privoxy on, (e.g. Windows - XP). + XP SP2), if you are using a Unix flavor, + sending the output of uname -a should do, + in case of GNU/Linux, please also name the distribution. @@ -155,23 +183,23 @@ Please be sure to provide the following information: The URL where the problem occurred, or some way for us to duplicate the - problem (e.g. http://somesite.example.com?somethingelse=123). + problem (e.g. http://somesite.example.com/?somethingelse=123). Whether your version of Privoxy is one supplied - by the developers of Privoxy via SourceForge, - or somewhere else. + by the Privoxy developers via SourceForge, + or if you got your copy somewhere else. Whether you are using Privoxy in tandem with - another proxy such as TOR. If so, please try - disabling the other proxy. + another proxy such as Tor. If so, please + temporary disable the other proxy to see if the symptoms change. @@ -186,19 +214,48 @@ Please be sure to provide the following information: Any other pertinent information to help identify the problem such as config or log file excerpts (yes, you should have log file entries for each - action taken). - - - - - - Please provide your SF login, or email address, in case we - need to contact you. + action taken). To get a meaningful logfile, please make sure that the + logfile directive + is being used and the following debug options are enabled: + 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 4096 # Startup banner and warnings. +debug 8192 # Non-fatal errors + If you are having trouble with a filter, please additionally enable + debug 64 # debug regular expression filters + If you using Privoxy 3.0.17 or later and suspect that it interprets the + request or the response incorrectly, please enable + debug 32768 # log all data read from the network + Note that Privoxy log files may contain sensitive information so please don't + submit any logfiles you didn't read first. You can mask sensitive information + as long as it's clear that you removed something. + + + You don't have to tell us your actual name when filing a problem + report, but if you don't, please use a nickname so we can differentiate + between your messages and the ones entered by other "anonymous" users that + may respond to your request if they have the same problem or already + found a solution. + + + + Please also check the status of your request a few days after submitting + it, as we may request additional information. If you use a SF id, + you should automatically get a mail when someone responds to your request. + + The appendix of the Privoxy User Manual also has helpful information