doc/webserver/user-manual/contact.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01
   2 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
   3 <html>
   4   <head>
   5     <meta name="generator" content="HTML Tidy, see www.w3.org">
   6     <title>
   7       Contacting the Developers, Bug Reporting and Feature Requests
   8     </title>
   9     <meta name="GENERATOR" content=
  10     "Modular DocBook HTML Stylesheet Version 1.79">
  11     <link rel="HOME" title="Privoxy 3.0.18 User Manual" href="index.html">
  12     <link rel="PREVIOUS" title="Privoxy's Template Files" href=
  13     "templates.html">
  14     <link rel="NEXT" title="Privoxy Copyright, License and History" href=
  15     "copyright.html">
  16     <link rel="STYLESHEET" type="text/css" href="../p_doc.css">
  17     <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
  18     <link rel="STYLESHEET" type="text/css" href="p_doc.css">
  19 <style type="text/css">
  20  body {
  21   background-color: #EEEEEE;
  22   color: #000000;
  23  }
  24  :link { color: #0000FF }
  25  :visited { color: #840084 }
  26  :active { color: #0000FF }
  27  hr.c1 {text-align: left}
  28 </style>
  29   </head>
  30   <body class="SECT1">
  31     <div class="NAVHEADER">
  32       <table summary="Header navigation table" width="100%" border="0"
  33       cellpadding="0" cellspacing="0">
  34         <tr>
  35           <th colspan="3" align="center">
  36             Privoxy 3.0.18 User Manual
  37           </th>
  38         </tr>
  39         <tr>
  40           <td width="10%" align="left" valign="bottom">
  41             <a href="templates.html" accesskey="P">Prev</a>
  42           </td>
  43           <td width="80%" align="center" valign="bottom">
  44           </td>
  45           <td width="10%" align="right" valign="bottom">
  46             <a href="copyright.html" accesskey="N">Next</a>
  47           </td>
  48         </tr>
  49       </table>
  50       <hr width="100%" class="c1">
  51     </div>
  52     <div class="SECT1">
  53       <h1 class="SECT1">
  54         <a name="CONTACT">11. Contacting the Developers, Bug Reporting and
  55         Feature Requests</a>
  56       </h1>
  57       <p>
  58         We value your feedback. In fact, we rely on it to improve <span
  59         class="APPLICATION">Privoxy</span> and its configuration. However,
  60         please note the following hints, so we can provide you with the best
  61         support:
  62       </p>
  63       <div class="SECT2">
  64         <h2 class="SECT2">
  65           <a name="CONTACT-SUPPORT">11.1. Get Support</a>
  66         </h2>
  67         <p>
  68           For casual users, our <a href=
  69           "http://sourceforge.net/tracker/?group_id=11118&amp;atid=211118"
  70           target="_top">support forum at SourceForge</a> is probably best
  71           suited: <a href=
  72           "http://sourceforge.net/tracker/?group_id=11118&amp;atid=211118"
  73           target=
  74           "_top">http://sourceforge.net/tracker/?group_id=11118&amp;atid=211118</a>
  75         </p>
  76         <p>
  77           All users are of course welcome to discuss their issues on the <a
  78           href="http://lists.sourceforge.net/lists/listinfo/ijbswa-users"
  79           target="_top">users mailing list</a>, where the developers also
  80           hang around.
  81         </p>
  82         <p>
  83           Please don't sent private support requests to individual Privoxy
  84           developers, either use the mailing lists or the support trackers.
  85         </p>
  86         <p>
  87           If you have to contact a Privoxy developer directly for other
  88           reasons, please send a real mail and do not bother with
  89           SourceForge's messaging system. Answers to SourceForge messages are
  90           usually bounced by SourceForge's mail server in which case the
  91           developer wasted time writing a response you don't get. From your
  92           point of view it will look like your message has been completely
  93           ignored, so this is frustrating for all parties involved.
  94         </p>
  95         <p>
  96           Note that the Privoxy mailing lists are moderated. Posts from
  97           unsubscribed addresses have to be accepted manually by a moderator.
  98           This may cause a delay of several days and if you use a subject
  99           that doesn't clearly mention Privoxy or one of its features, your
 100           message may be accidentally discarded as spam.
 101         </p>
 102         <p>
 103           If you aren't subscribed, you should therefore spend a few seconds
 104           to come up with a proper subject. Additionally you should make it
 105           clear that you want to get CC'd. Otherwise some responses will be
 106           directed to the mailing list only, and you won't see them.
 107         </p>
 108       </div>
 109       <div class="SECT2">
 110         <h2 class="SECT2">
 111           <a name="REPORTING">11.2. Reporting Problems</a>
 112         </h2>
 113         <p>
 114           <span class="QUOTE">"Problems"</span> for our purposes, come in two
 115           forms:
 116         </p>
 117         <ul>
 118           <li>
 119             <p>
 120               Configuration issues, such as ads that slip through, or sites
 121               that don't function properly due to one <span class=
 122               "APPLICATION">Privoxy</span> <span class=
 123               "QUOTE">"action"</span> or another being turned <span class=
 124               "QUOTE">"on"</span>.
 125             </p>
 126           </li>
 127           <li>
 128             <p>
 129               <span class="QUOTE">"Bugs"</span> in the programming code that
 130               makes up <span class="APPLICATION">Privoxy</span>, such as that
 131               might cause a crash.
 132             </p>
 133           </li>
 134         </ul>
 135         <div class="SECT3">
 136           <h3 class="SECT3">
 137             <a name="CONTACT-ADS">11.2.1. Reporting Ads or Other
 138             Configuration Problems</a>
 139           </h3>
 140           <p>
 141             Please send feedback on ads that slipped through, innocent images
 142             that were blocked, sites that don't work properly, and other
 143             configuration related problem of <tt class=
 144             "FILENAME">default.action</tt> file, to <a href=
 145             "http://sourceforge.net/tracker/?group_id=11118&amp;atid=460288"
 146             target=
 147             "_top">http://sourceforge.net/tracker/?group_id=11118&amp;atid=460288</a>,
 148             the Actions File Tracker.
 149           </p>
 150           <p>
 151             New, improved <tt class="FILENAME">default.action</tt> files may
 152             occasionally be made available based on your feedback. These will
 153             be announced on the <a href=
 154             "http://lists.sourceforge.net/lists/listinfo/ijbswa-announce"
 155             target="_top">ijbswa-announce</a> list and available from our the
 156             <a href=
 157             "http://sourceforge.net/project/showfiles.php?group_id=11118"
 158             target="_top">files section</a> of our <a href=
 159             "http://sf.net/projects/ijbswa/" target="_top">project page</a>.
 160           </p>
 161         </div>
 162         <div class="SECT3">
 163           <h3 class="SECT3">
 164             <a name="CONTACT-BUGS">11.2.2. Reporting Bugs</a>
 165           </h3>
 166           <p>
 167             Please report all bugs through our bug tracker: <a href=
 168             "http://sourceforge.net/tracker/?group_id=11118&amp;atid=111118"
 169             target=
 170             "_top">http://sourceforge.net/tracker/?group_id=11118&amp;atid=111118</a>.
 171           </p>
 172           <p>
 173             Before doing so, please make sure that the bug has <span class=
 174             "emphasis"><i class="EMPHASIS">not already been
 175             submitted</i></span> and observe the additional hints at the top
 176             of the <a href=
 177             "http://sourceforge.net/tracker/?func=add&amp;group_id=11118&amp;atid=111118"
 178              target="_top">submit form</a>. If already submitted, please feel
 179             free to add any info to the original report that might help to
 180             solve the issue.
 181           </p>
 182           <p>
 183             Please try to verify that it is a <span class=
 184             "APPLICATION">Privoxy</span> bug, and not a browser or site bug
 185             or documented behaviour that just happens to be different than
 186             what you expected. If unsure, try <a href=
 187             "http://config.privoxy.org/toggle?set=disable" target=
 188             "_top">toggling off</a> <span class="APPLICATION">Privoxy</span>,
 189             and see if the problem persists.
 190           </p>
 191           <p>
 192             If you are using your own custom configuration, please try the
 193             stock configs to see if the problem is configuration related. If
 194             you're having problems with a feature that is disabled by
 195             default, please ask around on the mailing list if others can
 196             reproduce the problem.
 197           </p>
 198           <p>
 199             If you aren't using the latest Privoxy version, the bug may have
 200             been found and fixed in the meantime. We would appreciate if you
 201             could take the time to <a href=
 202             "http://www.privoxy.org/user-manual/installation.html" target=
 203             "_top">upgrade to the latest version</a> (or even the latest CVS
 204             snapshot) and verify that your bug still exists.
 205           </p>
 206           <p>
 207             Please be sure to provide the following information:
 208           </p>
 209           <p>
 210           </p>
 211           <ul>
 212             <li>
 213               <p>
 214                 The exact <span class="APPLICATION">Privoxy</span> version
 215                 you are using (if you got the source from CVS, please also
 216                 provide the source code revisions as shown in <a href=
 217                 "http://config.privoxy.org/show-version" target=
 218                 "_top">http://config.privoxy.org/show-version</a>).
 219               </p>
 220             </li>
 221             <li>
 222               <p>
 223                 The operating system and versions you run <span class=
 224                 "APPLICATION">Privoxy</span> on, (e.g. <span class=
 225                 "APPLICATION">Windows XP SP2</span>), if you are using a Unix
 226                 flavor, sending the output of <span class="QUOTE">"uname
 227                 -a"</span> should do, in case of GNU/Linux, please also name
 228                 the distribution.
 229               </p>
 230             </li>
 231             <li>
 232               <p>
 233                 The name, platform, and version of the <span class=
 234                 "APPLICATION">browser</span> you were using (e.g. <span
 235                 class="APPLICATION">Internet Explorer v5.5</span> for Mac).
 236               </p>
 237             </li>
 238             <li>
 239               <p>
 240                 The URL where the problem occurred, or some way for us to
 241                 duplicate the problem (e.g. <tt class=
 242                 "LITERAL">http://somesite.example.com/?somethingelse=123</tt>).
 243               </p>
 244             </li>
 245             <li>
 246               <p>
 247                 Whether your version of <span class=
 248                 "APPLICATION">Privoxy</span> is one supplied by the <span
 249                 class="APPLICATION">Privoxy</span> developers via
 250                 SourceForge, or if you got your copy somewhere else.
 251               </p>
 252             </li>
 253             <li>
 254               <p>
 255                 Whether you are using <span class=
 256                 "APPLICATION">Privoxy</span> in tandem with another proxy
 257                 such as <span class="APPLICATION">Tor</span>. If so, please
 258                 temporary disable the other proxy to see if the symptoms
 259                 change.
 260               </p>
 261             </li>
 262             <li>
 263               <p>
 264                 Whether you are using a personal firewall product. If so,
 265                 does <span class="APPLICATION">Privoxy</span> work without
 266                 it?
 267               </p>
 268             </li>
 269             <li>
 270               <p>
 271                 Any other pertinent information to help identify the problem
 272                 such as config or log file excerpts (yes, you should have log
 273                 file entries for each action taken). To get a meaningful
 274                 logfile, please make sure that the <a href=
 275                 "../user-manual/config.html#LOGFILE" target="_top">logfile
 276                 directive</a> is being used and the following <a href=
 277                 "../user-manual/config.html#DEBUG" target="_top">debug
 278                 options</a> are enabled:
 279               </p>
 280               <p class="LITERALLAYOUT">
 281                 debug&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1&nbsp;#&nbsp;Log&nbsp;the&nbsp;destination&nbsp;for&nbsp;each&nbsp;request&nbsp;Privoxy&nbsp;let&nbsp;through.&nbsp;See&nbsp;also&nbsp;debug&nbsp;1024.<br>
 282
 283                  debug&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2&nbsp;#&nbsp;show&nbsp;each&nbsp;connection&nbsp;status<br>
 284
 285                  debug&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4&nbsp;#&nbsp;show&nbsp;I/O&nbsp;status<br>
 286
 287                  debug&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;8&nbsp;#&nbsp;show&nbsp;header&nbsp;parsing<br>
 288
 289                  debug&nbsp;&nbsp;&nbsp;128&nbsp;#&nbsp;debug&nbsp;redirects<br>
 290
 291                  debug&nbsp;&nbsp;&nbsp;256&nbsp;#&nbsp;debug&nbsp;GIF&nbsp;de-animation<br>
 292
 293                  debug&nbsp;&nbsp;&nbsp;512&nbsp;#&nbsp;Common&nbsp;Log&nbsp;Format<br>
 294
 295                  debug&nbsp;&nbsp;1024&nbsp;#&nbsp;Log&nbsp;the&nbsp;destination&nbsp;for&nbsp;requests&nbsp;Privoxy&nbsp;didn't&nbsp;let&nbsp;through,&nbsp;and&nbsp;the&nbsp;reason&nbsp;why.<br>
 296
 297                  debug&nbsp;&nbsp;4096&nbsp;#&nbsp;Startup&nbsp;banner&nbsp;and&nbsp;warnings.<br>
 298
 299                  debug&nbsp;&nbsp;8192&nbsp;#&nbsp;Non-fatal&nbsp;errors
 300               </p>
 301               If you are having trouble with a filter, please additionally
 302               enable
 303               <p class="LITERALLAYOUT">
 304                 debug&nbsp;&nbsp;&nbsp;&nbsp;64&nbsp;#&nbsp;debug&nbsp;regular&nbsp;expression&nbsp;filters
 305               </p>
 306               If you are using Privoxy 3.0.17 or later and suspect that it
 307               interprets the request or the response incorrectly, please
 308               enable
 309               <p class="LITERALLAYOUT">
 310                 debug&nbsp;32768&nbsp;#&nbsp;log&nbsp;all&nbsp;data&nbsp;read&nbsp;from&nbsp;the&nbsp;network
 311               </p>
 312               Note that Privoxy log files may contain sensitive information
 313               so please don't submit any logfiles you didn't read first. You
 314               can mask sensitive information as long as it's clear that you
 315               removed something.<br>
 316             </li>
 317           </ul>
 318
 319           <p>
 320             You don't have to tell us your actual name when filing a problem
 321             report, but if you don't, please use a nickname so we can
 322             differentiate between your messages and the ones entered by other
 323             "anonymous" users that may respond to your request if they have
 324             the same problem or already found a solution. Note that due to
 325             spam the trackers may not always allow to post without being
 326             logged into SourceForge. If that's the case, you are still free
 327             to create a login that isn't directly linked to your name,
 328             though.
 329           </p>
 330           <p>
 331             Please also check the status of your request a few days after
 332             submitting it, as we may request additional information. If you
 333             use a SF id, you should automatically get a mail when someone
 334             responds to your request. Please don't bother to add an email
 335             address when using the tracker. If you prefer to communicate
 336             through email, just use one of the mailing lists directly.
 337           </p>
 338           <p>
 339             The <a href=
 340             "http://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT"
 341             target="_top">appendix of the Privoxy User Manual</a> also has
 342             helpful information on understanding <tt class=
 343             "LITERAL">actions</tt>, and <tt class="LITERAL">action</tt>
 344             debugging.
 345           </p>
 346         </div>
 347       </div>
 348       <div class="SECT2">
 349         <h2 class="SECT2">
 350           <a name="CONTACT-FEATURE">11.3. Request New Features</a>
 351         </h2>
 352         <p>
 353           You are welcome to submit ideas on new features or other proposals
 354           for improvement through our feature request tracker at <a href=
 355           "http://sourceforge.net/tracker/?atid=361118&amp;group_id=11118"
 356           target=
 357           "_top">http://sourceforge.net/tracker/?atid=361118&amp;group_id=11118</a>.
 358         </p>
 359       </div>
 360       <div class="SECT2">
 361         <h2 class="SECT2">
 362           <a name="MAILING-LISTS">11.4. Mailing Lists</a>
 363         </h2>
 364         <p>
 365           If you prefer to communicate through email, instead of using a web
 366           interface, feel free to use one of the mailing lists. To discuss
 367           issues that haven't been completely diagnosed yet, please use the
 368           Privoxy users list. Technically interested users and people who
 369           wish to contribute to the project are always welcome on the
 370           developers list. You can find an overview of all <span class=
 371           "APPLICATION">Privoxy</span>-related mailing lists, including list
 372           archives, at: <a href="http://sourceforge.net/mail/?group_id=11118"
 373           target="_top">http://sourceforge.net/mail/?group_id=11118</a>.
 374         </p>
 375       </div>
 376     </div>
 377     <div class="NAVFOOTER">
 378       <hr width="100%" class="c1">
 379       <table summary="Footer navigation table" width="100%" border="0"
 380       cellpadding="0" cellspacing="0">
 381         <tr>
 382           <td width="33%" align="left" valign="top">
 383             <a href="templates.html" accesskey="P">Prev</a>
 384           </td>
 385           <td width="34%" align="center" valign="top">
 386             <a href="index.html" accesskey="H">Home</a>
 387           </td>
 388           <td width="33%" align="right" valign="top">
 389             <a href="copyright.html" accesskey="N">Next</a>
 390           </td>
 391         </tr>
 392         <tr>
 393           <td width="33%" align="left" valign="top">
 394             Privoxy's Template Files
 395           </td>
 396           <td width="34%" align="center" valign="top">
 397             &nbsp;
 398           </td>
 399           <td width="33%" align="right" valign="top">
 400             Privoxy Copyright, License and History
 401           </td>
 402         </tr>
 403       </table>
 404     </div>
 405   </body>
 406 </html>
 407