#
# File : $Source: /cvsroot/ijbswa/current/default.action,v $
#
-# $Id: default.action,v 1.10 2002/04/02 06:22:16 oes Exp $
+# $Id: default.action,v 1.11 2002/04/02 08:51:51 oes Exp $
#
# Purpose : Default actions file, see
# http://www.privoxy.org/faq/questions.html#CONFIGFILES
# regular expressions wouldn't fit here, but (FIXME) someone should paste
# a concise intro to the regex language here.
#
-# If Junkbuster was compiled with pcre support (default), Perl compatible
+# If Privoxy was compiled with pcre support (default), Perl compatible
# regular expressions are used. See the pcre/docs/ direcory or man perlre
# (also available on http://www.perldoc.com/perl5.6/pod/perlre.html) for
# details.
# +downgrade
# Downgrade HTTP/1.1 client requests to HTTP/1.0 and downgrade the
# responses as well. Use this action for servers that use HTTP/1.1
-# protocol features that Junkbuster currently can't handle yet.
+# protocol features that Privoxy currently can't handle yet.
#
# +fast-redirects
# Many sites, like yahoo.com, don't just link to other sites.
# its connections to the cliant and to the remote proxy.
# This can be a big security hole, since CONNECT-enabled proxies can
# be abused as TCP relays very easily.
-# By default, i.e. in the absence of a +limit-connect action, Junkbuster
+# By default, i.e. in the absence of a +limit-connect action, Privoxy
# will only allow CONNECT requests to port 443, which is the standard port
# for https.
# If you want to allow CONNECT for more ports than that, or want to forbid
#
# File : $Source: /cvsroot/ijbswa/current/default.filter,v $
#
-# $Id: basic.action,v 1.3 2002/03/26 22:29:54 swa Exp $
+# $Id: default.filter,v 1.5 2002/03/27 15:30:26 swa Exp $
#
# Purpose : Rules to process the content of web pages
#
# * Submit bugs only thru our bug forum:
# http://sourceforge.net/tracker/?group_id=11118&atid=111118
# Make sure that the bug has not already been submitted. Please try
-# to verify that it is a Junkbuster bug, and not a browser or site
+# to verify that it is a Privoxy 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,
#
# Revisions :
# $Log: default.filter,v $
+# Revision 1.5 2002/03/27 15:30:26 swa
+# have a consistent appearance
+#
# Revision 1.4 2002/03/26 22:29:54 swa
# we have a new homepage!
#
-# This is the Internet Junkbuster web site.
+# This is the Privoxy web site.
#
-# If the robot is connecting through a JunkBuster, then the
+# If the robot is connecting through Privoxy, then the
# control interface is at /config. It isn't very useful
# to index it, and you're likely to break stuff. So go away!
#
-# Even if you're not connected through a JunkBuster, the
-# one "JunkBuster's not working" page there is not very
+# Even if you're not connected through Privoxy, the
+# one "Privoxy is not working" page there is not very
# interesting.
User-agent: *
projects / privoxy.git / commitdiff