<META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.64 -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK REL="HOME" -TITLE="Privoxy User Manual" +TITLE="Privoxy 3.0.27 User Manual" HREF="index.html"><LINK REL="PREVIOUS" -TITLE="Privoxy Configuration" -HREF="configuration.html"><LINK +TITLE="Privoxy's Template Files" +HREF="templates.html"><LINK REL="NEXT" -TITLE="Copyright and History" +TITLE="Privoxy Copyright, License and History" HREF="copyright.html"><LINK REL="STYLESHEET" TYPE="text/css" -HREF="../p_doc.css"></HEAD +HREF="../p_doc.css"><META +HTTP-EQUIV="Content-Type" +CONTENT="text/html; +charset=ISO-8859-1"> +<LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css"> +</head ><BODY CLASS="SECT1" BGCOLOR="#EEEEEE" @@ -29,6 +34,7 @@ ALINK="#0000FF" ><DIV CLASS="NAVHEADER" ><TABLE +SUMMARY="Header navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" @@ -37,7 +43,7 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->Privoxy User Manual</TH +>Privoxy 3.0.27 User Manual</TH ></TR ><TR ><TD @@ -45,7 +51,8 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="configuration.html" +HREF="templates.html" +ACCESSKEY="P" >Prev</A ></TD ><TD @@ -59,6 +66,7 @@ ALIGN="right" VALIGN="bottom" ><A HREF="copyright.html" +ACCESSKEY="N" >Next</A ></TD ></TR @@ -72,168 +80,438 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="CONTACT" ->6. Contacting the Developers, Bug Reporting and Feature +>11. Contacting the Developers, Bug Reporting and Feature Requests</A ></H1 ><P -> We value your feedback. However, to provide you with the best support, please - note: - - <P +> We value your feedback. In fact, we rely on it to improve + <SPAN +CLASS="APPLICATION" +>Privoxy</SPAN +> and its configuration. + However, please note the following hints, so we can + provide you with the best support.</P +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="SUFFICIENT-INFORMATION" +>11.1. Please provide sufficient information</A +></H2 +><P +> 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 +> Before contacting us to report a problem, please try to verify that it is a + <SPAN +CLASS="APPLICATION" +>Privoxy</SPAN +> 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" +>toggling + off</A +> <SPAN +CLASS="APPLICATION" +>Privoxy</SPAN +>, and see if the problem persists.</P +><P +> 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 problem may have been found + and fixed in the meantime. We would appreciate if you could take the time + to <A +HREF="https://www.privoxy.org/user-manual/installation.html" +TARGET="_top" +>upgrade + to the latest version</A +> and verify that the problem still exists.</P +><P +> Please be sure to provide the following information when reporting problems + or requesting support:</P +><P ></P ><UL ><LI ><P -CLASS="LITERALLAYOUT" -> Use the Sourceforge Support Forum to get help:<br> - <br> - <A -HREF="http://sourceforge.net/tracker/?group_id=11118&atid=211118" -TARGET="_top" ->http://sourceforge.net/tracker/?group_id=11118&atid=211118</A -><br> - </P +> The exact <SPAN +CLASS="APPLICATION" +>Privoxy</SPAN +> version you are using. + </P ></LI ><LI ><P -CLASS="LITERALLAYOUT" -> Submit bugs only through our Sourceforge Bug Forum:<br> - <br> - <A -HREF="http://sourceforge.net/tracker/?group_id=11118&atid=111118" -TARGET="_top" ->http://sourceforge.net/tracker/?group_id=11118&atid=111118</A ->. <br> - </P +> The operating system and versions you run + <SPAN +CLASS="APPLICATION" +>Privoxy</SPAN +> on, e.g. <SPAN +CLASS="APPLICATION" +>Windows + XP SP2</SPAN +>. + </P +></LI +><LI +><P +> 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 +> for Mac). + </P +></LI +><LI +><P +> The URL where the problem occurred, or some way for us to duplicate the + problem (e.g. <TT +CLASS="LITERAL" +>http://somesite.example.com/?somethingelse=123</TT +>). + </P +></LI +><LI ><P -> Make sure that the bug has not already been submitted. Please try to - verify that it is a <SPAN +> Whether your version of <SPAN CLASS="APPLICATION" >Privoxy</SPAN -> bug, and not a - browser or site bug first. If you are using your own custom configuration, - please try the stock configs to see if the problem is a configuration - related bug. And if not using the latest development snapshot, please try - the latest one. Or even better, CVS sources. Please be sure to include the - <SPAN +> is one supplied + by the <SPAN CLASS="APPLICATION" >Privoxy</SPAN ->/<SPAN +> developers via SourceForge, + or if you got your copy somewhere else. + </P +></LI +><LI +><P +> Whether you are using <SPAN CLASS="APPLICATION" ->Junkbuster</SPAN -> - version, platform, browser, any pertinent log data, any other relevant - details (please be specific) and, if possible, some way to reproduce the - bug. - </P +>Privoxy</SPAN +> together with + another proxy such as <SPAN +CLASS="APPLICATION" +>Tor</SPAN +>. If so, please + temporary disable the other proxy to see if the symptoms change. + </P ></LI ><LI ><P -CLASS="LITERALLAYOUT" -> Submit feature requests only through our Sourceforge feature request forum:<br> - <br> - <A -HREF="http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse" -TARGET="_top" ->http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse</A ->.<br> - </P +> Whether you are using a personal firewall product. If so, does + <SPAN +CLASS="APPLICATION" +>Privoxy</SPAN +> work without it? + </P ></LI ><LI ><P -CLASS="LITERALLAYOUT" -> Submit missed ads and banners, and incorrectly blocked images, popups, etc:<br> - <br> - <A -HREF="http://p.p/" +> 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). To get a meaningful logfile, please make sure that the + <A +HREF="../user-manual/config.html#LOGFILE" TARGET="_top" ->http://p.p/</A ->, and select <A -HREF="javascript:w=Math.floor(screen.width/2);h=Math.floor(screen.height*0.9);void(window.open('http://www.privoxy.org/actions','Feedback','screenx='+w+',width='+w+',height='+h+',scrollbars=yes,toolbar=no,location=no,directories=no,status=no,menubar=no,copyhistory=no').focus());" +>logfile directive</A +> + is being used and the following <A +HREF="../user-manual/config.html#DEBUG" TARGET="_top" -><SPAN -CLASS="QUOTE" ->"actions file feedback system"</SPAN -></A -><br> - </P +>debug options</A +> are enabled + (all of them): + </P +><P +CLASS="LITERALLAYOUT" +>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,<br> + # and the reason why.<br> +debug 4096 # Startup banner and warnings.<br> +debug 8192 # Non-fatal errors<br> +debug 65536 # Log applying actions</P ><P -> This page can also be reached from many of the internal CGI pages. +> If you are having trouble with a filter, please additionally enable </P -></LI -><LI ><P CLASS="LITERALLAYOUT" -> For any other issues, feel free to use the mailing lists:<br> - <br> - <A -HREF="http://sourceforge.net/mail/?group_id=11118" -TARGET="_top" ->http://sourceforge.net/mail/?group_id=11118</A ->.<br> - </P -><P -> Anyone interested in actively participating in development and related - discussions can also join the appropriate mailing list. Archives are - available too. - </P +>debug 64 # debug regular expression filters</P +><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 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. 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. + 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="https://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT" +TARGET="_top" +>appendix + of the Privoxy User Manual</A +> also has helpful information + on understanding <TT +CLASS="LITERAL" +>actions</TT +>, and <TT +CLASS="LITERAL" +>action</TT +> debugging.</P +></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="SUBMITACTIONS" ->6.1. Submitting Ads and <SPAN -CLASS="QUOTE" ->"Action"</SPAN -> Problems</A +NAME="CONTACT-SUPPORT" +>11.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="REPORTING" +>11.3. Reporting Problems</A ></H2 ><P -> Ads and banners that are not stopped by <SPAN +><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 -> - can be submitted to the developers by accessing a special page and filling - out the brief, required form. Conversely, you can also report pages, images, - etc. that <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 -> is blocking, but should not. - The form itself does require Internet access.</P +>, 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" +>11.3.1. Reporting Ads or Other Configuration Problems</A +></H3 ><P -> To do this, point your browser to <SPAN +> 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="https://sourceforge.net/tracker/?group_id=11118&atid=460288" +TARGET="_top" +> 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" +>11.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" +>11.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="MAILING-LISTS" +>11.5. Mailing Lists</A +></H2 +><P +>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 -> - at <A -HREF="http://p.p/" +>-related mailing lists, +including list archives, at: +<A +HREF="https://lists.privoxy.org/mailman/listinfo" TARGET="_top" ->http://p.p/</A ->, and then select - <A -HREF="javascript:w=Math.floor(screen.width/2);h=Math.floor(screen.height*0.9);void(window.open('http://www.privoxy.org/actions','Feedback','screenx='+w+',width='+w+',height='+h+',scrollbars=yes,toolbar=no,location=no,directories=no,status=no,menubar=no,copyhistory=no').focus());" +>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" ->Actions file feedback system</A ->, - near the bottom of the page. Paste in the URL that is the cause of the - unwanted behavior, and follow the prompts. The developers will - try to incorporate your submission into future versions.</P +>https://sourceforge.net/mail/?group_id=11118</A +>.</P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="SF-TRACKERS" +>11.6. SourceForge support trackers</A +></H2 ><P -> New <TT -CLASS="FILENAME" ->default.actions</TT -> files will occasionally be made - available based on your feedback. These - will be announced on the +> The <A -HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce" +HREF="https://sourceforge.net/tracker/?group_id=11118&atid=211118" TARGET="_top" ->ijbswa-announce</A +>SourceForge support trackers</A > - list.</P + 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 @@ -241,6 +519,7 @@ CLASS="NAVFOOTER" ><HR ALIGN="LEFT" WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" @@ -251,7 +530,8 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="configuration.html" +HREF="templates.html" +ACCESSKEY="P" >Prev</A ></TD ><TD @@ -260,6 +540,7 @@ ALIGN="center" VALIGN="top" ><A HREF="index.html" +ACCESSKEY="H" >Home</A ></TD ><TD @@ -268,6 +549,7 @@ ALIGN="right" VALIGN="top" ><A HREF="copyright.html" +ACCESSKEY="N" >Next</A ></TD ></TR @@ -276,10 +558,7 @@ HREF="copyright.html" WIDTH="33%" ALIGN="left" VALIGN="top" -><SPAN -CLASS="APPLICATION" ->Privoxy</SPAN -> Configuration</TD +>Privoxy's Template Files</TD ><TD WIDTH="34%" ALIGN="center" @@ -289,7 +568,7 @@ VALIGN="top" WIDTH="33%" ALIGN="right" VALIGN="top" ->Copyright and History</TD +>Privoxy Copyright, License and History</TD ></TR ></TABLE ></DIV

X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Fcontact.html;h=ae0b37e5e9444b14e9c8caa41e13c4f816ba8db2;hp=6e65674a39c46c582c60e77fe7149bd2a7cf2ae3;hb=3c890b0540031fa87cc28514b3e4d0e23124fbcd;hpb=7017546f48d1189837d3b8d6a523328195279e57 diff --git a/doc/webserver/user-manual/contact.html b/doc/webserver/user-manual/contact.html index 6e65674a..ae0b37e5 100644 --- a/doc/webserver/user-manual/contact.html +++ b/doc/webserver/user-manual/contact.html @@ -1,3 +1,4 @@ + <META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.64 -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK REL="HOME" -TITLE="Privoxy User Manual" +TITLE="Privoxy 3.0.27 User Manual" HREF="index.html"><LINK REL="PREVIOUS" -TITLE="Privoxy Configuration" -HREF="configuration.html"><LINK +TITLE="Privoxy's Template Files" +HREF="templates.html"><LINK REL="NEXT" -TITLE="Copyright and History" +TITLE="Privoxy Copyright, License and History" HREF="copyright.html"><LINK REL="STYLESHEET" TYPE="text/css" -HREF="../p_doc.css"></HEAD +HREF="../p_doc.css"><META +HTTP-EQUIV="Content-Type" +CONTENT="text/html; +charset=ISO-8859-1"> +<LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css"> +</head ><BODY CLASS="SECT1" BGCOLOR="#EEEEEE" @@ -29,6 +34,7 @@ ALINK="#0000FF" ><DIV CLASS="NAVHEADER" ><TABLE +SUMMARY="Header navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" @@ -37,7 +43,7 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->Privoxy User Manual</TH +>Privoxy 3.0.27 User Manual</TH ></TR ><TR ><TD @@ -45,7 +51,8 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="configuration.html" +HREF="templates.html" +ACCESSKEY="P" >Prev</A ></TD ><TD @@ -59,6 +66,7 @@ ALIGN="right" VALIGN="bottom" ><A HREF="copyright.html" +ACCESSKEY="N" >Next</A ></TD ></TR @@ -72,168 +80,438 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="CONTACT" ->6. Contacting the Developers, Bug Reporting and Feature +>11. Contacting the Developers, Bug Reporting and Feature Requests</A ></H1 ><P -> We value your feedback. However, to provide you with the best support, please - note: - - <P +> We value your feedback. In fact, we rely on it to improve + <SPAN +CLASS="APPLICATION" +>Privoxy</SPAN +> and its configuration. + However, please note the following hints, so we can + provide you with the best support.</P +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="SUFFICIENT-INFORMATION" +>11.1. Please provide sufficient information</A +></H2 +><P +> 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 +> Before contacting us to report a problem, please try to verify that it is a + <SPAN +CLASS="APPLICATION" +>Privoxy</SPAN +> 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" +>toggling + off</A +> <SPAN +CLASS="APPLICATION" +>Privoxy</SPAN +>, and see if the problem persists.</P +><P +> 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 problem may have been found + and fixed in the meantime. We would appreciate if you could take the time + to <A +HREF="https://www.privoxy.org/user-manual/installation.html" +TARGET="_top" +>upgrade + to the latest version</A +> and verify that the problem still exists.</P +><P +> Please be sure to provide the following information when reporting problems + or requesting support:</P +><P ></P ><UL ><LI ><P -CLASS="LITERALLAYOUT" -> Use the Sourceforge Support Forum to get help:<br> - <br> - <A -HREF="http://sourceforge.net/tracker/?group_id=11118&atid=211118" -TARGET="_top" ->http://sourceforge.net/tracker/?group_id=11118&atid=211118</A -><br> - </P +> The exact <SPAN +CLASS="APPLICATION" +>Privoxy</SPAN +> version you are using. + </P ></LI ><LI ><P -CLASS="LITERALLAYOUT" -> Submit bugs only through our Sourceforge Bug Forum:<br> - <br> - <A -HREF="http://sourceforge.net/tracker/?group_id=11118&atid=111118" -TARGET="_top" ->http://sourceforge.net/tracker/?group_id=11118&atid=111118</A ->. <br> - </P +> The operating system and versions you run + <SPAN +CLASS="APPLICATION" +>Privoxy</SPAN +> on, e.g. <SPAN +CLASS="APPLICATION" +>Windows + XP SP2</SPAN +>. + </P +></LI +><LI +><P +> 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 +> for Mac). + </P +></LI +><LI +><P +> The URL where the problem occurred, or some way for us to duplicate the + problem (e.g. <TT +CLASS="LITERAL" +>http://somesite.example.com/?somethingelse=123</TT +>). + </P +></LI +><LI ><P -> Make sure that the bug has not already been submitted. Please try to - verify that it is a <SPAN +> Whether your version of <SPAN CLASS="APPLICATION" >Privoxy</SPAN -> bug, and not a - browser or site bug first. If you are using your own custom configuration, - please try the stock configs to see if the problem is a configuration - related bug. And if not using the latest development snapshot, please try - the latest one. Or even better, CVS sources. Please be sure to include the - <SPAN +> is one supplied + by the <SPAN CLASS="APPLICATION" >Privoxy</SPAN ->/<SPAN +> developers via SourceForge, + or if you got your copy somewhere else. + </P +></LI +><LI +><P +> Whether you are using <SPAN CLASS="APPLICATION" ->Junkbuster</SPAN -> - version, platform, browser, any pertinent log data, any other relevant - details (please be specific) and, if possible, some way to reproduce the - bug. - </P +>Privoxy</SPAN +> together with + another proxy such as <SPAN +CLASS="APPLICATION" +>Tor</SPAN +>. If so, please + temporary disable the other proxy to see if the symptoms change. + </P ></LI ><LI ><P -CLASS="LITERALLAYOUT" -> Submit feature requests only through our Sourceforge feature request forum:<br> - <br> - <A -HREF="http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse" -TARGET="_top" ->http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse</A ->.<br> - </P +> Whether you are using a personal firewall product. If so, does + <SPAN +CLASS="APPLICATION" +>Privoxy</SPAN +> work without it? + </P ></LI ><LI ><P -CLASS="LITERALLAYOUT" -> Submit missed ads and banners, and incorrectly blocked images, popups, etc:<br> - <br> - <A -HREF="http://p.p/" +> 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). To get a meaningful logfile, please make sure that the + <A +HREF="../user-manual/config.html#LOGFILE" TARGET="_top" ->http://p.p/</A ->, and select <A -HREF="javascript:w=Math.floor(screen.width/2);h=Math.floor(screen.height*0.9);void(window.open('http://www.privoxy.org/actions','Feedback','screenx='+w+',width='+w+',height='+h+',scrollbars=yes,toolbar=no,location=no,directories=no,status=no,menubar=no,copyhistory=no').focus());" +>logfile directive</A +> + is being used and the following <A +HREF="../user-manual/config.html#DEBUG" TARGET="_top" -><SPAN -CLASS="QUOTE" ->"actions file feedback system"</SPAN -></A -><br> - </P +>debug options</A +> are enabled + (all of them): + </P +><P +CLASS="LITERALLAYOUT" +>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,<br> + # and the reason why.<br> +debug 4096 # Startup banner and warnings.<br> +debug 8192 # Non-fatal errors<br> +debug 65536 # Log applying actions</P ><P -> This page can also be reached from many of the internal CGI pages. +> If you are having trouble with a filter, please additionally enable </P -></LI -><LI ><P CLASS="LITERALLAYOUT" -> For any other issues, feel free to use the mailing lists:<br> - <br> - <A -HREF="http://sourceforge.net/mail/?group_id=11118" -TARGET="_top" ->http://sourceforge.net/mail/?group_id=11118</A ->.<br> - </P -><P -> Anyone interested in actively participating in development and related - discussions can also join the appropriate mailing list. Archives are - available too. - </P +>debug 64 # debug regular expression filters</P +><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 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. 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. + 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="https://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT" +TARGET="_top" +>appendix + of the Privoxy User Manual</A +> also has helpful information + on understanding <TT +CLASS="LITERAL" +>actions</TT +>, and <TT +CLASS="LITERAL" +>action</TT +> debugging.</P +></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="SUBMITACTIONS" ->6.1. Submitting Ads and <SPAN -CLASS="QUOTE" ->"Action"</SPAN -> Problems</A +NAME="CONTACT-SUPPORT" +>11.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="REPORTING" +>11.3. Reporting Problems</A ></H2 ><P -> Ads and banners that are not stopped by <SPAN +><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 -> - can be submitted to the developers by accessing a special page and filling - out the brief, required form. Conversely, you can also report pages, images, - etc. that <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 -> is blocking, but should not. - The form itself does require Internet access.</P +>, 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" +>11.3.1. Reporting Ads or Other Configuration Problems</A +></H3 ><P -> To do this, point your browser to <SPAN +> 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="https://sourceforge.net/tracker/?group_id=11118&atid=460288" +TARGET="_top" +> 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" +>11.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" +>11.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="MAILING-LISTS" +>11.5. Mailing Lists</A +></H2 +><P +>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 -> - at <A -HREF="http://p.p/" +>-related mailing lists, +including list archives, at: +<A +HREF="https://lists.privoxy.org/mailman/listinfo" TARGET="_top" ->http://p.p/</A ->, and then select - <A -HREF="javascript:w=Math.floor(screen.width/2);h=Math.floor(screen.height*0.9);void(window.open('http://www.privoxy.org/actions','Feedback','screenx='+w+',width='+w+',height='+h+',scrollbars=yes,toolbar=no,location=no,directories=no,status=no,menubar=no,copyhistory=no').focus());" +>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" ->Actions file feedback system</A ->, - near the bottom of the page. Paste in the URL that is the cause of the - unwanted behavior, and follow the prompts. The developers will - try to incorporate your submission into future versions.</P +>https://sourceforge.net/mail/?group_id=11118</A +>.</P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="SF-TRACKERS" +>11.6. SourceForge support trackers</A +></H2 ><P -> New <TT -CLASS="FILENAME" ->default.actions</TT -> files will occasionally be made - available based on your feedback. These - will be announced on the +> The <A -HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce" +HREF="https://sourceforge.net/tracker/?group_id=11118&atid=211118" TARGET="_top" ->ijbswa-announce</A +>SourceForge support trackers</A > - list.</P + 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 @@ -241,6 +519,7 @@ CLASS="NAVFOOTER" ><HR ALIGN="LEFT" WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" @@ -251,7 +530,8 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="configuration.html" +HREF="templates.html" +ACCESSKEY="P" >Prev</A ></TD ><TD @@ -260,6 +540,7 @@ ALIGN="center" VALIGN="top" ><A HREF="index.html" +ACCESSKEY="H" >Home</A ></TD ><TD @@ -268,6 +549,7 @@ ALIGN="right" VALIGN="top" ><A HREF="copyright.html" +ACCESSKEY="N" >Next</A ></TD ></TR @@ -276,10 +558,7 @@ HREF="copyright.html" WIDTH="33%" ALIGN="left" VALIGN="top" -><SPAN -CLASS="APPLICATION" ->Privoxy</SPAN -> Configuration</TD +>Privoxy's Template Files</TD ><TD WIDTH="34%" ALIGN="center" @@ -289,7 +568,7 @@ VALIGN="top" WIDTH="33%" ALIGN="right" VALIGN="top" ->Copyright and History</TD +>Privoxy Copyright, License and History</TD ></TR ></TABLE ></DIV