CLASS="APPLICATION"
>Privoxy</SPAN
> and its configuration.
- However, please note the following hints, so we can
- provide you with the best support:</P
+ However, please note the following hints, so we can
+ provide you with the best support.</P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-SUPPORT"
->6.1. Get Support</A
+NAME="SUFFICIENT-INFORMATION"
+>6.1. Please provide sufficient information</A
></H2
><P
-> For casual users, our
- <A
-HREF="http://sourceforge.net/tracker/?group_id=11118&atid=211118"
-TARGET="_top"
->support forum at SourceForge</A
->
- is probably best suited:
- <A
-HREF="http://sourceforge.net/tracker/?group_id=11118&atid=211118"
-TARGET="_top"
->http://sourceforge.net/tracker/?group_id=11118&atid=211118</A
-></P
-><P
-> All users are of course welcome to discuss their issues on the <A
-HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-users"
-TARGET="_top"
->users
- mailing list</A
->, where the developers also hang around.</P
-><P
-> Please don't sent private support requests to individual Privoxy
- developers, either use the mailing lists or the support trackers.</P
-><P
-> 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.</P
-><P
-> 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.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="REPORTING"
->6.2. Reporting Problems</A
-></H2
+> A lot of support requests don't contain enough information and can't
+ be solved without a lot of back and forth which causes unnecessary
+ delays. Reading this section should help to prevent that.</P
><P
-><SPAN
-CLASS="QUOTE"
->"Problems"</SPAN
-> for our purposes, come in two forms:</P
-><P
-></P
-><UL
-><LI
-><P
-> Configuration issues, such as ads that slip through, or sites that
- don't function properly due to one <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->
- <SPAN
-CLASS="QUOTE"
->"action"</SPAN
-> or another being turned <SPAN
-CLASS="QUOTE"
->"on"</SPAN
->.
- </P
-></LI
-><LI
-><P
-> <SPAN
-CLASS="QUOTE"
->"Bugs"</SPAN
-> in the programming code that makes up
- <SPAN
+> Before contacting us to report a problem, please try to verify that it is a
+ <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->, such as that might cause a crash.
- </P
-></LI
-></UL
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="CONTACT-ADS"
->6.2.1. Reporting Ads or Other Configuration Problems</A
-></H3
-><P
-> 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
- <TT
-CLASS="FILENAME"
->default.action</TT
-> file, to
- <A
-HREF="http://sourceforge.net/tracker/?group_id=11118&atid=460288"
-TARGET="_top"
-> http://sourceforge.net/tracker/?group_id=11118&atid=460288</A
->,
- the Actions File Tracker.</P
-><P
-> New, improved <TT
-CLASS="FILENAME"
->default.action</TT
-> files may occasionally be made
- available based on your feedback. These will be announced on the <A
-HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce"
-TARGET="_top"
->ijbswa-announce</A
->
- list and available from our the <A
-HREF="http://sourceforge.net/project/showfiles.php?group_id=11118"
-TARGET="_top"
->files section</A
-> of
- our <A
-HREF="http://sf.net/projects/ijbswa/"
-TARGET="_top"
->project page</A
->.</P
-></DIV
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="CONTACT-BUGS"
->6.2.2. Reporting Bugs</A
-></H3
-><P
-> Please report all bugs through our bug tracker:
- <A
-HREF="http://sourceforge.net/tracker/?group_id=11118&atid=111118"
-TARGET="_top"
->http://sourceforge.net/tracker/?group_id=11118&atid=111118</A
->. </P
-><P
-> Before doing so, please make sure that the bug has <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->not already been submitted</I
-></SPAN
->
- and observe the additional hints at the top of the <A
-HREF="http://sourceforge.net/tracker/?func=add&group_id=11118&atid=111118"
-TARGET="_top"
->submit
- form</A
->. If already submitted, please feel free to add any info to the
- original report that might help to solve the issue.</P
-><P
-> Please try to verify that it is a <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> bug,
- and not a browser or site bug or documented behaviour that just happens
- to be different than what you expected. If unsure,
+> problem, and not a browser or site problem
+ or documented behaviour that just happens to be different than what you expected.
+ If unsure,
try <A
HREF="http://config.privoxy.org/toggle?set=disable"
TARGET="_top"
>Privoxy</SPAN
>, and see if the problem persists.</P
><P
-> If you are using your own custom configuration, please try
- the stock configs to see if the problem is configuration related.
+> If you are using your own custom configuration, please try the default
+ configuration 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.</P
><P
-> If you aren't using the latest Privoxy version, the bug may have been found
+> 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 <A
-HREF="http://www.privoxy.org/user-manual/installation.html"
+HREF="https://www.privoxy.org/user-manual/installation.html"
TARGET="_top"
>upgrade
to the latest version</A
-> (or even the latest CVS snapshot) and verify
- that your bug still exists.</P
+> and verify that the problem still exists.</P
><P
->Please be sure to provide the following information:</P
+> Please be sure to provide the following information when reporting problems
+ or requesting support:</P
><P
-> <P
></P
><UL
><LI
> The exact <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> version you are using
- (if you got the source from CVS, please also provide the source code revisions
- as shown in <A
-HREF="http://config.privoxy.org/show-version"
-TARGET="_top"
->http://config.privoxy.org/show-version</A
->).
+> version you are using.
</P
></LI
><LI
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> on, (e.g. <SPAN
+> on, e.g. <SPAN
CLASS="APPLICATION"
>Windows
XP SP2</SPAN
->), if you are using a Unix flavor,
- sending the output of <SPAN
-CLASS="QUOTE"
->"uname -a"</SPAN
-> should do,
- in case of GNU/Linux, please also name the distribution.
+>.
</P
></LI
><LI
> The name, platform, and version of the <SPAN
CLASS="APPLICATION"
>browser</SPAN
->
+>
you were using (e.g. <SPAN
CLASS="APPLICATION"
>Internet Explorer v5.5</SPAN
problem (e.g. <TT
CLASS="LITERAL"
>http://somesite.example.com/?somethingelse=123</TT
->).
+>).
</P
></LI
><LI
> Whether you are using <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> in tandem with
+> together with
another proxy such as <SPAN
CLASS="APPLICATION"
>Tor</SPAN
></LI
><LI
><P
-> Whether you are using a personal firewall product. If so, does
+> Whether you are using a personal firewall product. If so, does
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
HREF="../user-manual/config.html#DEBUG"
TARGET="_top"
>debug options</A
-> are enabled:
- <P
+> are enabled
+ (all of them):
+ </P
+><P
CLASS="LITERALLAYOUT"
->debug 1 # Log the destination for each request Privoxy let through. See also debug 1024.<br>
+>debug 1 # Log the destination for each request Privoxy let through.<br>
+ # See also debug 1024.<br>
debug 2 # show each connection status<br>
debug 4 # show I/O status<br>
debug 8 # show header parsing<br>
debug 128 # debug redirects<br>
debug 256 # debug GIF de-animation<br>
debug 512 # Common Log Format<br>
-debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why.<br>
+debug 1024 # Log the destination for requests Privoxy didn't let through,<br>
+ # and the reason why.<br>
debug 4096 # Startup banner and warnings.<br>
-debug 8192 # Non-fatal errors</P
->
- If you are having trouble with a filter, please additionally enable
- <P
+debug 8192 # Non-fatal errors<br>
+debug 65536 # Log applying actions</P
+><P
+> If you are having trouble with a filter, please additionally enable
+ </P
+><P
CLASS="LITERALLAYOUT"
>debug 64 # debug regular expression filters</P
->
- Note that Privoxy log files may contain sensitive information so please don't
+><P
+> If you suspect that Privoxy interprets the request or the response
+ incorrectly, please enable
+ </P
+><P
+CLASS="LITERALLAYOUT"
+>debug 32768 # log all data read from the network</P
+><P
+> 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
+ sure which of the debug directives are relevant, please just enable all of them
+ and let us worry about it.
+ </P
+><P
+> 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.
</P
></LI
></UL
-></P
><P
> You don't have to tell us your actual name when filing a problem
- report, but please use a nickname so we can differentiate between
- your messages and the ones entered by other "anonymous" users that
+ 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.</P
+ found a solution. Note that due to spam the trackers may not always
+ allow to post without being logged into SourceForge. If that's the
+ case, you are still free to create a login that isn't directly linked
+ to your name, though.</P
><P
> 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.</P
+ you should automatically get a mail when someone responds to your request.
+ Please don't bother to add an email address when using the tracker.
+ If you prefer to communicate through email, just use one of the mailing
+ lists directly.</P
+><P
+> If you are new to reporting problems, you might be interested in
+ <A
+HREF="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html"
+TARGET="_top"
+>How to Report Bugs Effectively</A
+>.</P
><P
> The <A
-HREF="http://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT"
+HREF="https://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT"
TARGET="_top"
>appendix
of the Privoxy User Manual</A
-> also has helpful information
+> also has helpful information
on understanding <TT
CLASS="LITERAL"
>actions</TT
>, and <TT
CLASS="LITERAL"
>action</TT
-> debugging. </P
+> debugging.</P
></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="CONTACT-SUPPORT"
+>6.2. Get Support</A
+></H2
+><P
+> All users are welcome to discuss their issues on the <A
+HREF="https://lists.privoxy.org/mailman/listinfo/privoxy-users"
+TARGET="_top"
+>users
+ mailing list</A
+>, where the developers also hang around.</P
+><P
+> Please don't send private support requests to individual Privoxy
+ developers, either use the mailing lists or the support trackers.</P
+><P
+> If you have to contact a Privoxy developer directly for other reasons,
+ please send a real mail and do not bother with SourceForge's messaging
+ system. Answers to SourceForge messages are usually bounced by SourceForge's
+ mail server in which case the developer wasted time writing a response you
+ don't get. From your point of view it will look like your message has
+ been completely ignored, so this is frustrating for all parties involved.</P
+><P
+> 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.</P
+><P
+> 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.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-FEATURE"
->6.3. Request New Features</A
+NAME="REPORTING"
+>6.3. Reporting Problems</A
></H2
><P
-> You are welcome to submit ideas on new features or other proposals
- for improvement through our feature request tracker at
+><SPAN
+CLASS="QUOTE"
+>"Problems"</SPAN
+> for our purposes, come in two forms:</P
+><P
+></P
+><UL
+><LI
+><P
+> Configuration issues, such as ads that slip through, or sites that
+ don't function properly due to one <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>
+ <SPAN
+CLASS="QUOTE"
+>"action"</SPAN
+> or another being turned <SPAN
+CLASS="QUOTE"
+>"on"</SPAN
+>.
+ </P
+></LI
+><LI
+><P
+> <SPAN
+CLASS="QUOTE"
+>"Bugs"</SPAN
+> in the programming code that makes up
+ <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>, such as that might cause a crash.
+ Documentation issues, for example spelling errors and unclear descriptions,
+ are bugs, too.
+ </P
+></LI
+></UL
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="CONTACT-ADS"
+>6.3.1. Reporting Ads or Other Configuration Problems</A
+></H3
+><P
+> 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
+ <TT
+CLASS="FILENAME"
+>default.action</TT
+> file, to
<A
-HREF="http://sourceforge.net/tracker/?atid=361118&group_id=11118"
+HREF="https://sourceforge.net/tracker/?group_id=11118&atid=460288"
TARGET="_top"
->http://sourceforge.net/tracker/?atid=361118&group_id=11118</A
->.</P
+> https://sourceforge.net/tracker/?group_id=11118&atid=460288</A
+>,
+ the Actions File Tracker.</P
+></DIV
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="CONTACT-BUGS"
+>6.3.2. Reporting Bugs</A
+></H3
+><P
+> Before reporting bugs, please make sure that the bug has <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>not already been submitted</I
+></SPAN
+>
+ and observe the additional hints at the top of the <A
+HREF="https://sourceforge.net/tracker/?func=add&group_id=11118&atid=111118"
+TARGET="_top"
+>submit
+ form</A
+>. If already submitted, please feel free to add any info to the
+ original report that might help to solve the issue.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="SECURITY-CONTACT"
+>6.4. Reporting security problems</A
+></H2
+><P
+> 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).</P
+><P
+> 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.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="CONTACT-OTHER"
->6.4. Other</A
+NAME="MAILING-LISTS"
+>6.5. Mailing Lists</A
></H2
><P
->For any other issues, feel free to use the mailing lists. Technically interested users
-and people who wish to contribute to the project are also welcome on the developers list!
+>If you prefer to communicate through email, instead of using a web interface,
+feel free to use one of the mailing lists.
+To discuss issues that haven't been completely diagnosed yet, please use the Privoxy
+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 <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>-related mailing lists,
including list archives, at:
<A
-HREF="http://sourceforge.net/mail/?group_id=11118"
+HREF="https://lists.privoxy.org/mailman/listinfo"
+TARGET="_top"
+>https://lists.privoxy.org/mailman/listinfo</A
+>.
+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:
+<A
+HREF="https://sourceforge.net/mail/?group_id=11118"
TARGET="_top"
->http://sourceforge.net/mail/?group_id=11118</A
+>https://sourceforge.net/mail/?group_id=11118</A
>.</P
></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="SF-TRACKERS"
+>6.6. SourceForge support trackers</A
+></H2
+><P
+> The
+ <A
+HREF="https://sourceforge.net/tracker/?group_id=11118&atid=211118"
+TARGET="_top"
+>SourceForge support trackers</A
+>
+ 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.</P
+></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
projects / privoxy.git / blobdiff