From: hal9 Date: Thu, 15 Nov 2007 03:02:37 +0000 (+0000) Subject: Rebuilt for 3.0.7 beta release. X-Git-Tag: v_3_0_7~51 X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=commitdiff_plain;h=af54618c059fd116d88387645cf6c689c658a56e Rebuilt for 3.0.7 beta release. --- diff --git a/AUTHORS b/AUTHORS index d1b1f656..c275a569 100644 --- a/AUTHORS +++ b/AUTHORS @@ -8,6 +8,7 @@ Current Privoxy Team: Hal Burgiss Roland Rosenfeld + Jörg Strohmayer Former Privoxy Team Members: @@ -20,7 +21,7 @@ Former Privoxy Team Members: Karsten Hopp Alexander Lazic Daniel Leite - G bor Lipt k + Gábor Lipták Adam Lock Guy Laroche Mark Martinec @@ -29,7 +30,6 @@ Former Privoxy Team Members: Haroon Rafique Georg Sauthoff Thomas Steudten - Joerg Strohmayer Rodney Stromlund Sviatoslav Sviridov Sarantis Paskalis @@ -45,23 +45,26 @@ alphabetical order): Reiner Buehl Andrew J. Caines Clifford Caoile - Fr d ric Crozat + Frédéric Crozat Michael T. Davis Mattes Dolak - Peter E + Peter E. Florian Effenberger Markus Elfring Dean Gaudet Stephen Gildea Daniel Griscom - Felix Gr bert + Felix Gröbert Aaron Hamid Darel Henman Magnus Holmgren + Ralf Horstmann + Stefan Huehner Peter Hyman Derek Jennings Petr Kadlec David Laight + Bert van Leeuwen Don Libes Paul Lieverse Toby Lyward @@ -69,29 +72,38 @@ alphabetical order): Jindrich Makovicka David Mediavilla Raphael Moll + Amuro Namie Adam Piggott + Dan Price + Lee R. Roberto Ragusa - F lix Rauch + Félix Rauch Maynard Riley Chung-chieh Shan - Spinor S + Spinor S. Bart Schelstraete Oliver Stoeneberg Peter Thoenen Martin Thomas - Bobby G. Vinyard - J rg Weinmann + Song Weijia + Jörg Weinmann Darren Wiebe + Bobby G. Vinyard Anduin Withers Oliver Yeoh Jamie Zawinski -Privoxy is based in part on code originally developed by: +Privoxy is based in part on code originally developed by Junkbusters Corp. and +Anonymous Coders. + +Privoxy heavily relies on Philip Hazel's PCRE. + +The code to filter compressed content makes use of zlib which is written by +Jean-loup Gailly and Mark Adler. - Junkbusters Corp. - Anonymous Coders - Ulrich Drepper (strptime fallback) - Philip Hazel (PCRE) +On systems that lack snprintf(), Privoxy is using a version written by Mark +Martinec. On systems that lack strptime(), Privoxy is using the one from the +GNU C Library written by Ulrich Drepper. If we've missed you off this list, please let us know! diff --git a/INSTALL b/INSTALL index 7a1f1a3d..a6c4c107 100644 --- a/INSTALL +++ b/INSTALL @@ -4,7 +4,7 @@ * * Purpose : INSTALL file to help with installing from source. * - * Copyright : Written by and Copyright (C) 2001-2006 the SourceForge + * Copyright : Written by and Copyright (C) 2001-2007 the SourceForge * Privoxy team. http://www.privoxy.org/ * * Based on the Internet Junkbuster originally written @@ -33,24 +33,26 @@ *********************************************************************/ -------------------------------------------------------------------------------- +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ To build Privoxy from source, autoconf, GNU make (gmake), and, of course, a C compiler like gcc are required. When building from a source tarball, first unpack the source: - tar xzvf privoxy-3.0.6-src* [.tgz or .tar.gz] - cd privoxy-3.0.6 + tar xzvf privoxy-3.0.7-beta-src* [.tgz or .tar.gz] + cd privoxy-3.0.7-beta + For retrieving the current CVS sources, you'll need a CVS client installed. Note that sources from CVS are typically development quality, and may not be stable, or well tested. To download CVS source, check the Sourceforge documentation, which might give commands like: - cvs -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa login - cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co current - cd current + cvs -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa login + cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co current + cd current + This will create a directory named current/, which will contain the source tree. @@ -61,33 +63,37 @@ with the wanted branch name (Example: v_3_0_branch for the 3.0 cvs tree). It is also strongly recommended to not run Privoxy as root. You should configure/install/run Privoxy as an unprivileged user, preferably by creating a "privoxy" user and group just for this purpose. See your local documentation -for the correct command line to do add new users and groups (something like +for the correct command line to do add new users and groups (something like adduser, but the command syntax may vary from platform to platform). /etc/passwd might then look like: - privoxy:*:7777:7777:privoxy proxy:/no/home:/no/shell + privoxy:*:7777:7777:privoxy proxy:/no/home:/no/shell + And then /etc/group, like: - privoxy:*:7777: + privoxy:*:7777: + Some binary packages may do this for you. Then, to build from either unpacked tarball or CVS source: - autoheader - autoconf - ./configure # (--help to see options) - make # (the make from GNU, sometimes called gmake) - su # Possibly required - make -n install # (to see where all the files will go) - make -s install # (to really install, -s to silence output) + autoheader + autoconf + ./configure # (--help to see options) + make # (the make from GNU, sometimes called gmake) + su # Possibly required + make -n install # (to see where all the files will go) + make -s install # (to really install, -s to silence output) + Using GNU make, you can have the first four steps automatically done for you by just typing: - make + make + in the freshly downloaded or unpacked source directory. @@ -95,9 +101,11 @@ To build an executable with security enhanced features so that users cannot easily bypass the proxy (e.g. "Go There Anyway"), or alter their own configurations, configure like this: - ./configure --disable-toggle --disable-editor --disable-force + ./configure --disable-toggle --disable-editor --disable-force -Then build as above. + +Then build as above. In Privoxy 3.0.7 and later, all of these options can also +be disabled through the configuration file. WARNING: If installing as root, the install will fail unless a non-root user or group is specified, or a privoxy user and group already exist on the system. If @@ -114,7 +122,8 @@ be run as this same user to insure write access to configuration and log files! Alternately, you can specify user and group on the make command line, but be sure both already exist: - make -s install USER=privoxy GROUP=privoxy + make -s install USER=privoxy GROUP=privoxy + The default installation path for make install is /usr/local. This may of course be customized with the various ./configure path options. If you are diff --git a/README b/README index 6b1d5d83..6987f7b5 100644 --- a/README +++ b/README @@ -1,10 +1,10 @@ /********************************************************************* * - * File : $Source: /cvsroot/ijbswa/current/README,v $ + * File : $Source: /cvsroot/ijbswa/current/doc/source/readme.sgml,v $ * * Purpose : README file to give a short intro. * - * Copyright : Written by and Copyright (C) 2001 - 2007 the SourceForge + * Copyright : Written by and Copyright (C) 2001-2007 the SourceForge * Privoxy team. http://www.privoxy.org/ * * Based on the Internet Junkbuster originally written @@ -32,39 +32,32 @@ * *********************************************************************/ -2007-11-03: The next stable release of Privoxy is being readied. The -developers consider the current sources to be stable, and are doing last minute -house keeping and fine tuning. There are many new features and enhancements, -many of which may not be fully documented at this point. Please refer to the -ChangeLog for what's new. 3.0.7 stable release is expected by the end of -November. +This README is included with the development version of Privoxy 3.0.7. See +http://www.privoxy.org/ for more information. The current code maturity level +is "beta", but seems stable to us :). -And PLEASE report any problems or comments! +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ -------------------------------------------------------------------------------- - -Privoxy is a web proxy with advanced filtering capabilities for protecting -privacy, modifying web page data, managing cookies, controlling access, and -removing ads, banners, pop-ups and other obnoxious Internet junk. Privoxy has a -very flexible configuration and can be customized to suit individual needs and -tastes. Privoxy has application for both stand-alone systems and multi-user -networks. +Privoxy is a non-caching web proxy with advanced filtering capabilities for +enhancing privacy, modifying web page data, managing HTTP cookies, controlling +access, and removing ads, banners, pop-ups and other obnoxious Internet junk. +Privoxy has a flexible configuration and can be customized to suit individual +needs and tastes. Privoxy has application for both stand-alone systems and +multi-user networks. Privoxy is based on Internet Junkbuster (tm). -------------------------------------------------------------------------------- +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1. IMPORTANT CHANGES -NEWS! November 2006, Privoxy 3.0.6 is released. This is a significant upgrade -with many new and enhanced features, and many bugs fixed. It is also the first -stable release in quite some time. There are fifteen new actions available, and -several actions have enhanced capabilities. Multiple filter files are now -supported as well. There are many improvements and refinements. See the "What's -New" section and the "Upgrader's Notes" in the User Manual for details and -specifics. Preliminary work on 3.0.7 is already underway. +November 2007, Privoxy 3.0.7 beta is released. This is a significant upgrade +with many new and enhanced features, and many bugs fixed. See the "ChangeLog", +and the "What's New" section and the "Upgrader's Notes" in the User Manual for +details and specifics. There are changes related to configuration, so anyone +upgrading and keeping their old configuration should read ahead first. -NEWS! September 2006, Privoxy 3.0.5 BETA is released. This is a significant +NEWS! November 2006, Privoxy 3.0.6 stable is released. This is a significant upgrade with many new and enhanced features, and many bugs fixed. There was and will not be an official 3.0.4 release. This release cycle was @@ -72,24 +65,19 @@ used to gather our thoughts, play with some new ideas and refine some old ones. It will remain a development cycle with no actual release. 3.0.5 is the fruit of these efforts. -NEWS! January 2004, Privoxy 3.0.3 is released. This is the another maintenance -release of Privoxy which fixes more bugs, further refines the configuration and -works around some known third-party problems. See the ChangeLog for complete -details. Upgrading from 3.0.2 is recommended. - -------------------------------------------------------------------------------- +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2. INSTALL See the INSTALL file in this directory, for installing from raw source, and the User Manual, for all other installation types. -------------------------------------------------------------------------------- +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3. RUN -privoxy [--help] [--version] [--no-daemon] [--pidfile PIDFILE] [--user USER -[.GROUP]] [--chroot] [config_file] +privoxy [——help] [——version] [——no-daemon] [——pidfile PIDFILE] [——user USER +[.GROUP]] [——chroot] [config_file] See the man page or User Manual for an explanation of each option, and other configuration and usage issues. @@ -98,7 +86,11 @@ If no config_file is specified on the command line, Privoxy will look for a file named 'config' in the current directory (except Win32 which will look for 'config.txt'). If no config_file is found, Privoxy will fail to start. -------------------------------------------------------------------------------- +Or for Red Hat and Fedora based distributions: /etc/rc.d/init.d/privoxy start + +Or Debian: /etc/init.d/privoxy start + +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4. CONFIGURATION @@ -113,29 +105,35 @@ Manual has an explanation of all configuration options, and examples: http:// www.privoxy.org/user-manual/. Be sure to set your browser(s) for HTTP/HTTPS Proxy at :, or whatever -you specify in the config file under 'listen-address'. DEFAULT is localhost: -8118. Note that Privoxy ONLY proxies HTTP (and HTTPS) traffic. Do not try it -with FTP or other protocols for the simple reason it does not work. +you specify in the config file under 'listen-address'. DEFAULT is +localhost:8118. Note that Privoxy ONLY proxies HTTP (and HTTPS) traffic. Do not +try it with FTP or other protocols for the simple reason it does not work. The actions list can be configured via the web interface accessed via http:// p.p/, as well other options. -------------------------------------------------------------------------------- +All configuration files are subject to unannounced changes during the +development process. + +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 5. DOCUMENTATION -There should be documentation in the 'doc' subdirectory. In particular, see the -User Manual there, the FAQ, and those interested in Privoxy development, should -look at developer-manual. +There should be documentation in the 'doc' subdirectory, but it may not be +completed at this point. In particular, see the User Manual there, the FAQ, and +those interested in Privoxy development, should look at developer-manual. -The source and configuration files are all well commented. The main -configuration files are: 'config', 'default.action', and 'default.filter'. +The most up to date source of information on the current development version, +may still be either comments in the source code, or the included configuration +files. The source and configuration files are all well commented. The main +configuration files are: 'config', 'default.action', and 'default.filter' in +the top-level source directory. Included documentation may vary according to platform and packager. All documentation is posted on http://www.privoxy.org, in case you don't have it, or can't find it. -------------------------------------------------------------------------------- +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 6. CONTACTING THE DEVELOPERS, BUG REPORTING AND FEATURE REQUESTS @@ -143,29 +141,39 @@ We value your feedback. In fact, we rely on it to improve Privoxy and its configuration. However, please note the following hints, so we can provide you with the best support: -------------------------------------------------------------------------------- +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 6.1. Get Support -For casual users, our support forum at SourceForge is probably best suited: +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 mailing list, where the developers also hang around. -------------------------------------------------------------------------------- +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. + +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. + +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 6.2. Reporting Problems "Problems" for our purposes, come in two forms: - * Configuration issues, such as ads that slip through, or sites that don't + • Configuration issues, such as ads that slip through, or sites that don't function properly due to one Privoxy "action" or another being turned "on". - - * "Bugs" in the programming code that makes up Privoxy, such as that might + + • "Bugs" in the programming code that makes up Privoxy, such as that might cause a crash. - -------------------------------------------------------------------------------- + +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 6.2.1. Reporting Ads or Other Configuration Problems @@ -178,63 +186,74 @@ 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. -------------------------------------------------------------------------------- +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 6.2.2. Reporting Bugs -Please report all bugs only through our bug tracker: http://sourceforge.net/ -tracker/?group_id=11118&atid=111118. +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 and observe the additional hints at the top of the submit form. If already submitted, please feel free to add any info to the original report that might help to solve the issue. -Please try to verify that it is a Privoxy bug, and not a browser or site bug -first. If unsure, try toggling off Privoxy, and see if the problem persists. If -you are using your own custom configuration, please try the stock configs to -see if the problem is configuration related. +Please try to verify that it is a Privoxy bug, and not a browser or site bug or +documented behaviour that just happens to be different than what you expected. +If unsure, try toggling off Privoxy, and see if the problem persists. + +If you are using your own custom configuration, please try the stock configs 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. -If not using the latest version, the bug may have been found and fixed in the -meantime. We would appreciate if you could take the time to upgrade to the -latest version (or even the latest CVS snapshot) and verify your bug. +If you aren't using the latest Privoxy version, the bug may have been found and +fixed in the meantime. We would appreciate if you could take the time to +upgrade to the latest version (or even the latest CVS snapshot) and verify that +your bug still exists. Please be sure to provide the following information: - * The exact Privoxy version of the proxy software (if you got the source from - CVS, please also provide the source code revisions as shown in http:// + • The exact Privoxy version you are using (if you got the source from CVS, + please also provide the source code revisions as shown in http:// config.privoxy.org/show-version). - - * The operating system and versions you run Privoxy on, (e.g. Windows XP + + • 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. - - * The name, platform, and version of the browser you were using (e.g. + should do, in case of GNU/Linux, please also name the distribution. + + • The name, platform, and version of the browser you were using (e.g. Internet Explorer v5.5 for Mac). - - * The URL where the problem occurred, or some way for us to duplicate the + + • The URL where the problem occurred, or some way for us to duplicate the problem (e.g. http://somesite.example.com/?somethingelse=123). - - * Whether your version of Privoxy is one supplied by the developers of - Privoxy via SourceForge, or somewhere else. - - * Whether you are using Privoxy in tandem with another proxy such as Tor. If - so, please try disabling the other proxy. - - * Whether you are using a personal firewall product. If so, does Privoxy work + + • Whether your version of Privoxy is one supplied by the Privoxy developers + via SourceForge, or if you got your copy somewhere else. + + • Whether you are using Privoxy in tandem with another proxy such as Tor. If + so, please temporary disable the other proxy to see if the symptoms change. + + • Whether you are using a personal firewall product. If so, does Privoxy work without it? - - * Any other pertinent information to help identify the problem such as config + + • 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). - - * Please provide your SF login, or email address, in case we need to contact - you. - + +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 may respond to your request if +they have the same problem or already found a solution. + +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. + The appendix of the Privoxy User Manual also has helpful information on understanding actions, and action debugging. -------------------------------------------------------------------------------- +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 6.3. Request New Features @@ -242,7 +261,7 @@ 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. -------------------------------------------------------------------------------- +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 6.4. Other diff --git a/privoxy.1 b/privoxy.1 index 0ce1b326..0d3c5886 100644 --- a/privoxy.1 +++ b/privoxy.1 @@ -3,7 +3,7 @@ .\" .\" Please send any bug reports, improvements, comments, patches, .\" etc. to Steve Cheng . -.TH "PRIVOXY" "1" "12 November 2007" "Privoxy 3.0.7 UNRELEASED" "" +.TH "PRIVOXY" "1" "14 November 2007" "Privoxy 3.0.7 beta" "" .SH NAME privoxy \- Privacy Enhancing Proxy .SH SYNOPSIS @@ -73,8 +73,10 @@ Privoxy is based on Internet Junkbuster (tm). .SH "INSTALLATION AND USAGE" .PP Browsers can either be individually configured to use -\fBPrivoxy\fR as a HTTP proxy, or \fBPrivoxy\fR can -be set to act as an intercepting proxy (see \fIconfig\fR). The default setting is for +\fBPrivoxy\fR as a HTTP proxy (recommended), +or \fBPrivoxy\fR can be combined with a packet +filter to build an intercepting proxy +(see \fIconfig\fR). The default setting is for localhost, on port 8118 (configurable in the main config file). To set the HTTP proxy in Netscape and Mozilla, go through: \fBEdit\fR; \fBPreferences\fR; \fBAdvanced\fR; @@ -150,67 +152,18 @@ configuration might look like: ## otherwise with the '+' operator. { \\ --add-header \\ --block \\ --client-header-filter{hide-tor-exit-notation} \\ --content-type-overwrite \\ --crunch-client-header \\ --crunch-if-none-match \\ --crunch-outgoing-cookies \\ --crunch-incoming-cookies \\ --crunch-server-header \\ --deanimate-gifs \\ --downgrade-http-version \\ --fast-redirects \\ --filter{js-annoyances} \\ --filter{js-events} \\ --filter{html-annoyances} \\ --filter{content-cookies} \\ --filter{refresh-tags} \\ --filter{unsolicited-popups} \\ --filter{all-popups} \\ --filter{img-reorder} \\ --filter{banners-by-size} \\ --filter{banners-by-link} \\ --filter{webbugs} \\ --filter{tiny-textforms} \\ --filter{jumping-windows} \\ --filter{frameset-borders} \\ --filter{demoronizer} \\ --filter{shockwave-flash} \\ --filter{quicktime-kioskmode} \\ --filter{fun} \\ --filter{crude-parental} \\ --filter{ie-exploits} \\ --filter{site-specifics} \\ --filter{google} \\ --filter{yahoo} \\ --filter{msn} \\ --filter{blogspot} \\ --filter{no-ping} \\ --force-text-mode \\ --handle-as-empty-document \\ --handle-as-image \\ --hide-accept-language \\ --hide-content-disposition \\ --hide-if-modified-since \\ ++deanimate-gifs{last} \\ ++filter{refresh-tags} \\ ++filter{img-reorder} \\ ++filter{banners-by-size} \\ ++filter{webbugs} \\ ++filter{jumping-windows} \\ ++filter{ie-exploits} \\ +hide-forwarded-for-headers \\ +hide-from-header{block} \\ --hide-referrer \\ --hide-user-agent \\ --inspect-jpegs \\ --kill-popups \\ --limit-connect \\ --overwrite-last-modified \\ --prevent-compression \\ --redirect \\ --send-vanilla-wafer \\ --send-wafer \\ --server-header-filter{xml-to-html} \\ --server-header-filter{html-to-xml} \\ --session-cookies-only \\ ++hide-referrer{conditional-block} \\ ++session-cookies-only \\ +set-image-blocker{pattern} \\ --treat-forbidden-connects-like-blocks \\ } / # '/' Match *all* URL patterns @@ -268,7 +221,7 @@ narrowly defined exceptions: # Replace example.com's style sheet with one of my choosing { +redirect{http://localhost/css-replacements/example.com.css} } - example.com/stylesheet.css + .example.com/stylesheet.css .fi .PP See the comments in the configuration files themselves, or the @@ -305,7 +258,7 @@ config file changes by \fBSIGHUP\fR -- it will detect them automatically. .SH "NOTES" .PP -This is a UNRELEASED version of \fBPrivoxy\fR. Not +This is a beta version of \fBPrivoxy\fR. Not all features are well tested. .PP Please see the \fIUser Manual\fR on how to contact the @@ -364,6 +317,7 @@ the \fBPrivoxy\fR developer manual. Hal Burgiss Roland Rosenfeld + Jörg Strohmayer .fi .SH "COPYRIGHT AND LICENSE" .SS "COPYRIGHT"