4 >General Information</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.64
10 TITLE="Privoxy Frequently Asked Questions"
11 HREF="index.html"><LINK
13 TITLE="Privoxy Frequently Asked Questions"
14 HREF="index.html"><LINK
17 HREF="installation.html"><LINK
20 HREF="../p_doc.css"></HEAD
39 >Privoxy Frequently Asked Questions</TH
60 HREF="installation.html"
74 >1. General Information</A
82 >1.1. What is this new version of <SPAN
95 > (tm) is a copyrighted product of <A
96 HREF="http://www.junkbusters.com"
98 >Junkbusters Corporation</A
100 Development of this effort stopped some time ago as of version 2.0.2. Stefan
101 Waldherr started the ijbswa project on <A
102 HREF="http://sourceforge.net/projects/ijbswa/"
106 rekindle development. Other developers subsequently joined with Stefan, and
107 have since added many new features, refinements and enhancements. The result
108 of this effort is <SPAN
117 > has evolved from the
120 >Junkbuster 2.0.2</SPAN
121 > code base, and has advanced
122 significantly at this point.
127 HREF="copyright.html"
130 information on the history of <SPAN
149 >? Why a name change at all?</A
160 >Privacy Enhancing Proxy</I
164 > There are potential legal complications from the continued use of the
168 > name, which is a registered trademark of
170 HREF="http://junkbusters.com"
172 >Junkbusters Corporation</A
177 > the rights to the name.
178 (There are, however, no objections from Junkbusters Corporation to the
182 > project itself, and they, in fact, still
183 share our ideals and goals.)</P
185 > The developers also believed that there are so many changes from the original
186 code, that it was time to make a clean break from the past and make
187 a name in their own right, especially now with the pending
188 release of version 3.0.</P
213 > left off. All the old features remain.
217 > still blocks ads and banners,
218 still manages cookies, and still helps protect your privacy. But, these are
219 all enhanced, and many new features have been added, all in the same vein.
222 > The configuration has changed significantly as well. This is something that
223 users will notice right off the bat if you are upgrading from
231 file does not exist any more. This is replaced by <SPAN
238 >. This is where most of
239 the per site configuration is now.
248 >1.4. What are some of the new features?</A
256 > Integrated browser based configuration and control utility at <A
257 HREF="http://config.privoxy.org/"
259 >http://config.privoxy.org/</A
266 tracing of rule and filter effects. Remote toggling.
271 > Blocking of annoying pop-up browser windows.
276 > HTTP/1.1 compliant (but not all optional 1.1 features are supported).
281 > Support for Perl Compatible Regular Expressions in the configuration files, and
282 generally a more sophisticated and flexible configuration syntax over
293 > Web page content filtering (removes banners based on size,
297 >, JavaScript and HTML annoyances, pop-ups, etc.)
302 > Bypass many click-tracking scripts (avoids script redirection).
307 > Multi-threaded (POSIX and native threads).
312 > Auto-detection and re-reading of config file changes.
317 > User-customizable HTML templates (e.g. 404 error page).
322 > Improved cookie management features (e.g. session based cookies).
327 > Improved signal handling, and a true daemon mode (Unix).
332 > Builds from source on most UNIX-like systems. Packages available for: Linux
333 (RedHat, SuSE, or Debian), Windows, Sun Solaris, Mac OSX, OS/2, HP-UX 11,
339 > Every feature now controllable on a per-site or per-location basis, configuration
340 more powerful and versatile over-all.
345 > Many smaller new features added, limitations and bugs removed, and security holes fixed.
357 >1.5. What is a <SPAN
367 > When you connect to a web site with <SPAN
371 you are really connecting to your locally running version of
379 intercepts your requests for the web page, and relays that to the
383 > web site. The web site sends the HTTP data stream
391 > can work its magic before it
392 relays this data back to your web browser.
398 > sits between you and the
399 WWW, it is in a position to intercept and completely manage all web traffic and
400 HTTP content before it gets to your browser.
404 > uses various programming methods to do
405 this, all of which is under your control via the various configuration
409 > There are many kinds of proxies. <SPAN
415 >"filtering proxy"</SPAN
429 an ad, and what is not?</A
435 > processes all the raw content of every
436 web page. So it reads everything on each page. It then compares this to the
437 rules as set up in the configuration files, and looks for any matches to
444 >"regular expressions"</SPAN
445 >. (If you are not familiar with regular
446 expressions, it is explained briefly in <A
447 HREF="../user-manual/appendix.html"
451 expressions facilitate matching of one text string against another, using
452 wildcards to build complex patterns. So <SPAN
456 will typically look for URLs and other content that match certain key words
457 and expressions as defined in the configuration files. For instance a URL
461 >, has a high probability of containing
462 ad banners, and thus would be a prime candidate to have a matching rule.</P
467 > will look for these kinds of obvious
468 looking culprits. And also, will use lists of known organizations that
469 specialize in ads. Again, using complex patterns to match as many potential
470 combinations as possible since there tend to be many, many variations used by
471 advertisers, and new ones are being introduced all the time.</P
483 This does not sound very scientific.</A
486 > Actually, it's a black art ;-) And yes, it is always possible to have a broad rule
487 accidentally block something by mistake. There is a good chance you may run
488 into such a situation at some point. It is tricky writing rules to cover
489 every conceivable possibility, and not occasionally get false positives.</P
491 > But this should not be a big concern since the
495 > configuration is very flexible, and
496 includes tools to help identify these types of situations so they can be
497 addressed as needed, allowing you to customize your installation.
499 HREF="trouble.html#AEN661"
500 >See the Troubleshooting section below</A
509 >1.8. My browser does the same things as
520 > Modern browsers do indeed have <I
524 functionality as <SPAN
528 adequate for you. But <SPAN
532 versatile and powerful, and can do a number of things that browsers just can't.
535 > In addition, a proxy is good choice if you use multiple browsers, or
536 have a LAN with multiple computers. This way all the configuration
537 is in one place, and you don't have to maintain a similar configuration
538 for possibly many browsers.
548 >1.9. Is there is a license or fee? What about a
549 warranty? Registration?</A
555 > is licensed under the GNU General Public
556 License (GPL). It is free to use, copy, modify or distribute as you wish
557 under the terms of this license. Please see the Copyright section for more
558 information on the license and copyright.
562 > There is no warranty of any kind, expressed, implied or otherwise. That is
563 something that would cost real money ;-) There is no registration either.
581 >1.10. I would like to help you, what do I do?</A
588 NAME="JOINTEAM-MONEY"
589 >1.10.1. Money Money Money</A
592 > We, of course, welcome donations and use the money for domain registering,
593 regular world-wide get-togethers (hahaha). Anyway, we'll soon describe the
594 process how to donate money to the team.</P
602 >1.10.2. You want to work with us?</A
605 > Well, helping the team is always a good idea. We welcome new developers,
606 RPM gurus or documentation makers. Simply get an account on sourceforge.net
607 and mail your id to the developer mailing list. Then read the
608 section Quickstart in the <A
609 HREF="../developer-manual/quickstart.html"
611 > Developer's Manual</A
614 > Once we have added you to the team, you'll have write access to the CVS
615 repository, and together we'll find a suitable task for you.</P
650 HREF="installation.html"
659 >Privoxy Frequently Asked Questions</TD