X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fsource%2Fcontacting.sgml;h=accbbf9dfb393dd2ed46cb950d8ca648c90353df;hb=64677ea8590e0ebad837f356fc7abc34cdb603ce;hp=304e4bacd80aecf26536c3d072f729a10961a594;hpb=c8fef82436741e1c885de359e79e64522f1d9624;p=privoxy.git diff --git a/doc/source/contacting.sgml b/doc/source/contacting.sgml index 304e4bac..accbbf9d 100644 --- a/doc/source/contacting.sgml +++ b/doc/source/contacting.sgml @@ -1,11 +1,9 @@ @@ -58,14 +55,13 @@ 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. Please be sure to provide the following information when reporting problems or requesting support: - @@ -77,10 +73,8 @@ The operating system and versions you run - Privoxy on, (e.g. Windows - 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. + Privoxy on, e.g. Windows + XP SP2. @@ -101,14 +95,14 @@ Whether your version of Privoxy is one supplied - by the Privoxy developers via SourceForge, + by the Privoxy developers, or if you got your copy somewhere else. - Whether you are using Privoxy in tandem with + Whether you are using Privoxy together with another proxy such as Tor. If so, please temporary disable the other proxy to see if the symptoms change. @@ -130,24 +124,29 @@ 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. See also debug 1024. + # See also debug 1024. debug 2 # show each connection status -debug 4 # show I/O status +debug 4 # show tagging-related messages 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 - debug 32768 # log all data read from the network + + If you suspect that Privoxy interprets the request or the response + incorrectly, please enable additionally + debug 32768 # log all data read from the network It's easy for us to ignore log messages that aren't relevant but missing log messages may make it impossible to investigate a problem. If you aren't @@ -159,10 +158,12 @@ debug 8192 # Non-fatal errors submit any logfiles you didn't read first. You can mask sensitive information as long as it's clear that you removed something. + + Please clear the browser cache before reproducing the problem. + - You don't have to tell us your actual name when filing a problem @@ -185,33 +186,20 @@ debug 8192 # Non-fatal errors - If you are new to reporting problems, you might be interested in - How to Report Bugs Effectively. - - - - The appendix + The appendix of the Privoxy User Manual also has helpful information on understanding actions, and action debugging. Get Support - For casual users, our - support forum at SourceForge - is probably best suited: - http://sourceforge.net/tracker/?group_id=11118&atid=211118 - - - - All users are of course welcome to discuss their issues on the users + All users are welcome to discuss their issues on the users mailing list, where the developers also hang around. - Please don't sent private support requests to individual Privoxy + Please don't send private support requests to individual Privoxy developers, either use the mailing lists or the support trackers. @@ -259,6 +247,8 @@ debug 8192 # Non-fatal errors Bugs in the programming code that makes up Privoxy, such as that might cause a crash. + Documentation issues, for example spelling errors and unclear descriptions, + are bugs, too. @@ -269,43 +259,37 @@ debug 8192 # Non-fatal errors Please send feedback on ads that slipped through, innocent images that were blocked, sites that don't work properly, and other configuration related problem of default.action file, to - - http://sourceforge.net/tracker/?group_id=11118&atid=460288, + https://sourceforge.net/p/ijbswa/actionsfile-feedback/, the Actions File Tracker. - - New, improved default.action files may occasionally be made - available based on your feedback. These will be announced on the ijbswa-announce - list and available from our the files section of - our project page. - Reporting Bugs - - Please report all bugs through our bug tracker: - http://sourceforge.net/tracker/?group_id=11118&atid=111118. - - Before doing so, please make sure that the bug has not already been submitted + Before reporting bugs, please make sure that the bug has not already been submitted and observe the additional hints at the top of the submit + url="https://sourceforge.net/p/ijbswa/bugs/">submit form. If already submitted, please feel free to add any info to the original report that might help to solve the issue. -Request New Features +Reporting security problems - You are welcome to submit ideas on new features or other proposals - for improvement through our feature request tracker at - http://sourceforge.net/tracker/?atid=361118&group_id=11118. + If you discovered a security problem or merely suspect that a bug might + be a security issue, please mail Fabian Keil <fk@fabiankeil.de> + (OpenPGP fingerprint: 4F36 C17F 3816 9136 54A1 E850 6918 2291 8BA2 371C). + + + Usually you should get a response within a day, otherwise it's + likely that either your mail or the response didn't make it. + If that happens, please mail to the developer list to request a + status update. @@ -318,6 +302,20 @@ 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: -http://sourceforge.net/mail/?group_id=11118. +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/p/ijbswa/mailman/. + +SourceForge support trackers + + The + 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. + + +