From 3438a9978a79dbb702e70e2e8a80d727f0ddd6e1 Mon Sep 17 00:00:00 2001 From: hal9 Date: Sun, 4 Nov 2007 21:18:32 +0000 Subject: [PATCH] Sync generated html with sgml source. --- doc/webserver/user-manual/actions-file.html | 553 +++++++------------ doc/webserver/user-manual/appendix.html | 102 +--- doc/webserver/user-manual/config.html | 298 +++++++--- doc/webserver/user-manual/configuration.html | 44 +- doc/webserver/user-manual/contact.html | 108 ++-- doc/webserver/user-manual/copyright.html | 45 +- doc/webserver/user-manual/filter-file.html | 18 +- doc/webserver/user-manual/index.html | 41 +- doc/webserver/user-manual/installation.html | 60 +- doc/webserver/user-manual/introduction.html | 34 +- doc/webserver/user-manual/quickstart.html | 14 +- doc/webserver/user-manual/seealso.html | 8 +- doc/webserver/user-manual/startup.html | 74 ++- doc/webserver/user-manual/templates.html | 8 +- doc/webserver/user-manual/whatsnew.html | 12 +- 15 files changed, 711 insertions(+), 708 deletions(-) diff --git a/doc/webserver/user-manual/actions-file.html b/doc/webserver/user-manual/actions-file.html index 72b9a064..f9fd3383 100644 --- a/doc/webserver/user-manual/actions-file.html +++ b/doc/webserver/user-manual/actions-file.html @@ -1,11 +1,11 @@ + Actions Files8. Actions Files8. Actions Files

The actions files are used to define what

http://config.privoxy.org/show-status. The over-riding principle when applying actions, is that the last action that - matches a given URL, wins. The broadest, most general rules go first + matches a given URL wins. The broadest, most general rules go first (defined in default.actiondefault.action, - with the advantage that is a separate file, which makes preserving your + with the advantage that it is a separate file, which makes preserving your personal settings across Privoxy

Actions can be used to block anything you want, including ads, banners, or - just some obnoxious URL that you would rather not see. Cookies can be accepted + just some obnoxious URL whose content you would rather not see. Cookies can be accepted or rejected, or accepted only during the current browser session (i.e. not - written to disk), content can be modified, JavaScripts tamed, user-tracking + written to disk), content can be modified, some JavaScripts tamed, user-tracking fooled, and much more. See below for a complete list @@ -686,9 +528,9 @@ CLASS="SECT2" >

8.1. Finding the Right Mix

8.1. Finding the Right Mix

Note that some

We have tried to provide you with reasonable rules to start from in the distribution actions files. But there is no general rule of thumb on these @@ -721,9 +563,9 @@ CLASS="SECT2" >

8.2. How to Edit

8.2. How to Edit

The easiest way to edit the actions files is with a browser by using our browser-based editor, which can be reached from 8.3. How Actions are Applied to Requests8.3. How Actions are Applied to Requests

Actions files are divided into sections. There are special sections, like the 8.4. Patterns8.4. Patterns

As mentioned,

Generally, a URL pattern has the form +> Generally, an URL pattern has the form <domain>/<path>

www.example.com/index.htmlwww.example.com/index.html$

matches all the documents on www.example.com + whose name starts with /index.html. +

www.example.com/index.html$

/index.html/index.html$

matches nothing, since it would be interpreted as a domain name and +> matches nothing, since it would be interpreted as a domain name and there is no top-level domain called .html

8.4.1. The Domain Pattern

8.4.1. The Domain Pattern

The matching of the domain part offers some flexible options: if the domain starts or ends with a dot, it becomes unanchored at that end. @@ -1252,9 +1111,9 @@ CLASS="SECT3" >

8.4.2. The Path Pattern

8.4.2. The Path Pattern

.example.com/.*/index.html.example.com/.*/index.html$

.example.com/(.*/)?index\.html.example.com/(.*/)?index\.html$

8.4.3. The Tag Pattern8.4.3. The Tag Pattern

Tag patterns are used to change the applying actions based on the request's tags. Tags can be created with either the client-header-tagger or the server-header-tagger action.

can tell them apart from URL patterns. Everything after the colon including white space, is interpreted as a regular expression with - path patterns syntax, except that tag patterns aren't left-anchored + path pattern syntax, except that tag patterns aren't left-anchored automatically (Privoxy doesn't silently add a "^""foo" somewhere.

somewhere. + "TAG: foo" wouldn't work as it requires white space.

Sections can contain URL and tag patterns at the same time, but tag patterns are checked after the URL patterns and thus @@ -1563,8 +1426,8 @@ CLASS="SECT2" CLASS="SECT2" >8.5. Actions8.5. Actions

All actions are disabled by default, until they are explicitly enabled somewhere in an actions file. Actions are turned on if preceded with a @@ -1726,7 +1589,7 @@ CLASS="REPLACEABLE" > Example: +hide-user-agent{ Mozilla 1.0 }+hide-user-agent{Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.4) Gecko/20070602 Firefox/2.0.0.4}

Privoxy would just be a - normal, non-blocking, non-anonymizing proxy. You must specifically enable the + normal, non-blocking, non-filtering proxy. You must specifically enable the privacy and blocking features you need (although the provided default actions files will give a good starting point).

Later defined actions always over-ride earlier ones. So exceptions - to any rules you make, should come in the latter part of the file (or +> Later defined action sections always over-ride earlier ones of the same type. + So exceptions to any rules you make, should come in the latter part of the file (or in a file that is processed later when using multiple actions files such as 8.5.1. add-header8.5.1. add-header

8.5.2. block8.5.2. block

8.5.3. client-header-filter8.5.3. client-header-filter

8.5.4. client-header-tagger8.5.4. client-header-tagger

8.5.5. content-type-overwrite8.5.5. content-type-overwrite

8.5.6. crunch-client-header8.5.6. crunch-client-header

8.5.7. crunch-if-none-match8.5.7. crunch-if-none-match

It is also useful to make sure the header isn't used as a cookie - replacement. + replacement (unlikely but possible).

Blocking the "If-Modified-Since:" header - isn't blocked as well. + isn't blocked or missing as well.

It is recommended to use this action together with @@ -2702,8 +2565,9 @@ WIDTH="90%" >

FeatureCautiousMediumAdvanced
Ad-blocking Aggressivenessmediumhighhigh
Ad-filtering by sizenoyesyes
Ad-filtering by linknonoyes
Pop-up killingblocks onlyblocks onlyblocks only
Privacy Featureslowmediummedium/high
Cookie handlingnonesession-onlykill
Referer forgingnoyesyes
GIF de-animationnoyesyes
Fast redirectsnonoyes
HTML tamingnonoyes
JavaScript tamingnonoyes
Web-bug killingnoyesyes
Image tag reorderingnonoyes
# Let the browser revalidate cached documents without being tracked across sessions
-{ +hide-if-modified-since{-60} \
+># Let the browser revalidate cached documents but don't
+# allow the server to use the revalidation headers for user tracking.
+{+hide-if-modified-since{-60} \
  +overwrite-last-modified{randomize} \
  +crunch-if-none-match}
 /
8.5.8. crunch-incoming-cookies8.5.8. crunch-incoming-cookies

Typical use:

Prevent the web server from setting any cookies on your system +> Prevent the web server from setting HTTP cookies on your system

incoming cookies. For +> HTTP cookies. For outgoing cookies, use +> HTTP cookies, use both to disable cookies completely. +> to disable HTTP cookies completely.

It makes 8.5.9. crunch-server-header8.5.9. crunch-server-header

8.5.10. crunch-outgoing-cookies8.5.10. crunch-outgoing-cookies

Typical use:

Prevent the web server from reading any cookies from your system +> Prevent the web server from reading any HTTP cookies from your system

outgoing cookies. For +> HTTP cookies. For incoming cookies, use +> HTTP cookies, use both to disable cookies completely. +> to disable HTTP cookies completely.

It makes 8.5.11. deanimate-gifs8.5.11. deanimate-gifs

8.5.12. downgrade-http-version8.5.12. downgrade-http-version

didn't support important HTTP/1.1 features well. It is left here for the unlikely case that you experience HTTP/1.1 related problems with some server - out there. Not all (optional) HTTP/1.1 features are supported yet, so there - is a chance you might need this action. + out there. Not all HTTP/1.1 features and requirements are supported yet, + so there is a chance you might need this action.

8.5.13. fast-redirects8.5.13. fast-redirects

 { +fast-redirects{simple-check} }
-   .example.com 
+   one.example.com 
 
  { +fast-redirects{check-decoded-url} }
    another.example.com/testing
8.5.14. filter8.5.14. filter

+filter{ie-exploits}         # Disable some known Internet Explorer bug exploits
+filter{ie-exploits} # Disable a known Internet Explorer bug exploits
8.5.15. force-text-mode8.5.15. force-text-mode

8.5.16. forward-override8.5.16. forward-override

Effect:

Overrules the forward directives in the configuration files. +> Overrules the forward directives in the configuration file.

"forward-socks4a 127.0.0.1:9050 ." to use the socks4a proxy listening at 127.0.0.1 port 9050. - Replace to use the socks4a proxy listening at + 127.0.0.1 port 9050. Replace "forward-socks4a" with "forward-socks4" to use a socks4 connection (with local DNS - resolution) instead. +> + to use a socks4 connection (with local DNS resolution) instead.

  • with "forward-socks4" to use a socks4 connection (with local DNS - resolution) instead. +> to use a socks4 connection + (with local DNS resolution) instead.

    • 8.5.17. handle-as-empty-document8.5.17. handle-as-empty-document

    8.5.18. handle-as-image8.5.18. handle-as-image

    8.5.19. hide-accept-language8.5.19. hide-accept-language

    8.5.20. hide-content-disposition8.5.20. hide-content-disposition

    This action will probably be removed in the future, + use server-header filters instead. +

    Example usage:
    8.5.21. hide-if-modified-since8.5.21. hide-if-modified-since

    8.5.22. hide-forwarded-for-headers8.5.22. hide-forwarded-for-headers

    Typical use:

    Improve privacy by hiding the true source of the request

    Improve privacy by not embedding the source of the request in the HTTP headers.

    Effect:
    Notes:

    It is fairly safe to leave this on. -

    This action is scheduled for improvement: It should be able to generate forged - "X-Forwarded-for:" headers using random IP addresses from a specified network, - to make successive requests from the same client look like requests from a pool of different - users sharing the same proxy. +> It is safe to leave this on.

    8.5.23. hide-from-header8.5.23. hide-from-header

    8.5.24. hide-referrer8.5.24. hide-referrer8.5.25. hide-user-agent8.5.25. hide-user-agent

    This action is scheduled for improvement. +> More information on known user-agent strings can be found at + http://www.user-agents.org/ + and + http://en.wikipedia.org/wiki/User_agent.

    8.5.26. inspect-jpegs8.5.26. inspect-jpegs

    Note that the described exploit is only one of many, + using this action does not mean that you no longer + have to patch the client.

    8.5.27. kill-popups

    8.5.28. limit-connect8.5.28. limit-connect

    8.5.29. prevent-compression8.5.29. prevent-compression

    8.5.30. overwrite-last-modified8.5.30. overwrite-last-modified

    8.5.31. redirect8.5.31. redirect

    8.5.32. send-vanilla-wafer8.5.32. send-vanilla-wafer

    8.5.33. send-wafer8.5.33. send-wafer

    8.5.34. server-header-filter8.5.34. server-header-filter

    8.5.35. server-header-tagger8.5.35. server-header-tagger

    8.5.36. session-cookies-only8.5.36. session-cookies-only

    8.5.37. set-image-blocker8.5.37. set-image-blocker

    8.5.38. treat-forbidden-connects-like-blocks8.5.38. treat-forbidden-connects-like-blocks

    8.5.39. Summary

    8.5.39. Summary

    Note that many of these actions have the potential to cause a page to misbehave, possibly even not to display at all. There are many ways @@ -7296,8 +7171,8 @@ CLASS="SECT2" CLASS="SECT2" >8.6. Aliases8.6. Aliases

    Custom 8.7. Actions Files Tutorial8.7. Actions Files Tutorial

    The above chapters have shown

    8.7.1. default.action

    8.7.1. default.action

    Every config file should start with a short comment stating its purpose:

    8.7.2. user.action

    8.7.2. user.action

    So far we are painting with a broad brush by setting general policies, which would be a reasonable starting point for many people. Now, diff --git a/doc/webserver/user-manual/appendix.html b/doc/webserver/user-manual/appendix.html index f7124451..10155019 100644 --- a/doc/webserver/user-manual/appendix.html +++ b/doc/webserver/user-manual/appendix.html @@ -1,11 +1,11 @@ + Appendix14. Appendix14. Appendix

    14.1. Regular Expressions

    14.1. Regular Expressions

    14.2. Privoxy's Internal Pages

    14.2. Privoxy's Internal Pages

    Since

    Short cuts. Turn off, then on:

    14.2.1. Bookmarklets14.2.1. Bookmarklets

    Below are some 14.3. Chain of Events14.3. Chain of Events

    Let's take a quick look at how some of 14.4. Troubleshooting: Anatomy of an Action14.4. Troubleshooting: Anatomy of an Action

    The way 

     Matches for http://google.com:
+> Matches for http://www.google.com:
 
  In file: default.action [ Edit ]
 
- {-add-header
- -block
- -client-header-filter{hide-tor-exit-notation}
- -content-type-overwrite
- -crunch-client-header
- -crunch-if-none-match
- -crunch-incoming-cookies
- -crunch-outgoing-cookies
- -crunch-server-header
- +deanimate-gifs {last}
- -downgrade-http-version
+ {+deanimate-gifs {last}
  +fast-redirects {check-decoded-url}
- -filter {js-events}
- -filter {content-cookies}
- -filter {all-popups}
- -filter {banners-by-link}
- -filter {tiny-textforms}
- -filter {frameset-borders}
- -filter {demoronizer}
- -filter {shockwave-flash}
- -filter {quicktime-kioskmode}
- -filter {fun}
- -filter {crude-parental}
- -filter {site-specifics}
- -filter {js-annoyances}
- -filter {html-annoyances}
  +filter {refresh-tags}
- -filter {unsolicited-popups}
  +filter {img-reorder}
  +filter {banners-by-size}
  +filter {webbugs}
  +filter {jumping-windows}
  +filter {ie-exploits}
- -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-forwarded-for-headers
  +hide-from-header {block}
- -hide-if-modified-since
  +hide-referrer {forge}
- -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
  +set-image-blocker {pattern}
- -treat-forbidden-connects-like-blocks }
 /
  
  { -session-cookies-only }
@@ -1688,7 +1640,7 @@ CLASS="SCREEN"
  -crunch-server-header
  +deanimate-gifs {last}
  -downgrade-http-version
- +fast-redirects {check-decoded-url}
+ -fast-redirects
  -filter {js-events}
  -filter {content-cookies}
  -filter {all-popups}
@@ -1729,7 +1681,7 @@ CLASS="SCREEN"
  -kill-popups
  -limit-connect
  -overwrite-last-modified
- +prevent-compression
+ -prevent-compression
  -redirect
  -send-vanilla-wafer
  -send-wafer
diff --git a/doc/webserver/user-manual/config.html b/doc/webserver/user-manual/config.html
index 05f183a0..6214cb89 100644
--- a/doc/webserver/user-manual/config.html
+++ b/doc/webserver/user-manual/config.html
@@ -1,11 +1,11 @@
+
 The Main Configuration File7. The Main Configuration File7. The Main Configuration File
     Again, the main configuration file is named 7.1. Local Set-up Documentation7.1. Local Set-up Documentation
        If you intend to operate 7.1.1. user-manual7.1.1. user-manual
    7.1.2. trust-info-url7.1.2. trust-info-url
    Default value:

    Two example URL are provided

    Two example URLs are provided

    Effect if unset:
    7.1.3. admin-address7.1.3. admin-address

    7.1.4. proxy-info-url7.1.4. proxy-info-url

    7.2. Configuration and Log File Locations7.2. Configuration and Log File Locations

    7.2.1. confdir7.2.1. confdir

    7.2.2. templdir7.2.2. templdir

    7.2.3. logdir7.2.3. logdir

    7.2.4. actionsfile7.2.4. actionsfile7.2.5. filterfile7.2.5. filterfile7.2.6. logfile7.2.6. logfile

    Default value:

    logfile (Unix) Unset (commented out). When activated: logfile (Unix) Privoxy (e.g., it's not blocking an ad you - think it should block) but in most cases you probably will never look at it. + think it should block) but in most cases you probably will never look at + it. For this reason, it is disabled by default. For troubleshooting + purposes, you will have to explicitly enable it.

    Your logfile will grow indefinitely, and you will probably want to @@ -1088,11 +1096,11 @@ CLASS="APPLICATION" (see "man cron"). For Red Hat, a ). For Red Hat based Linux distributions, a + logrotate - script has been included. +> script has been included.

    On SuSE Linux systems, you can place a line like 7.2.7. jarfile7.2.7. jarfile

    Default value:

    Unset (commented out). When activated: jarfile (Unix) Unset (commented out). When activated: jarfile (Unix) 7.2.8. trustfile7.2.8. trustfile

    7.3. Debugging7.3. Debugging

    These options are mainly useful when tracing a problem. Note that you might also want to invoke @@ -1357,8 +1371,8 @@ CLASS="SECT3" CLASS="SECT3" >7.3.1. debug7.3.1. debug

    7.3.2. single-threaded7.3.2. single-threaded

    7.4. Access Control and Security7.4. Access Control and Security

    This section of the config file controls the security-relevant aspects of 7.4.1. listen-address7.4.1. listen-address

    7.4.2. toggle7.4.2. toggle

    7.4.3. enable-remote-toggle7.4.3. enable-remote-toggle

    Default value:

    1

    0

    Effect if unset:

    For the time being, access to the toggle feature can Access to the toggle feature can not recommended - for multi-user environments with untrusted users. + for multi-user environments with untrusted users. Because of + the obvious security implications, this feature is off by default. + Note that malicious client side code (e.g JavaScript) is also potentially + capable of changing Privoxy's intended + behavior.

    Note that you must have compiled 7.4.4. enable-remote-http-toggle7.4.4. enable-remote-http-toggle

    Default value:

    1

    0

    Effect if unset:

    If you are using This feature is disabled by default. If you are using + Privoxy in a - multi-user environment or with untrustworthy clients and want to - enforce filtering, you will have to disable this option, - otherwise you can ignore it. +> in a environment with trusted clients, + you may enable this feature at your discretion. Note that malicious client + side code (e.g JavaScript) is also potentially capable of changing + Privoxy's intended behavior.

    7.4.5. enable-edit-actions7.4.5. enable-edit-actions

    Default value:

    1

    0

    Effect if unset:
    Notes:

    For the time being, access to the editor can Access to the editor can listen-address above) can - modify its configuration for all users. So this option is not recommended for multi-user environments with untrusted users. +> for multi-user environments with untrusted users + and is therefore disabled by default. Note that malicious client side code + (e.g JavaScript) is also potentially capable of changing + Privoxy's intended behavior.

    Note that you must have compiled 7.4.6. enforce-blocks7.4.6. enforce-blocks

    7.4.7. ACLs: permit-access and deny-access7.4.7. ACLs: permit-access and deny-access7.4.8. buffer-limit7.4.8. buffer-limit

    7.5. Forwarding7.5. Forwarding

    This feature allows routing of HTTP requests through a chain of multiple proxies.

    7.5.1. forward7.5.1. forward

    7.5.2. forward-socks4 and forward-socks4a7.5.2. forward-socks4 and forward-socks4a7.5.3. Advanced Forwarding Examples7.5.3. Advanced Forwarding Examples

    If you have links to multiple ISPs that provide various special content only to their subscribers, you can configure multiple 7.5.4. forwarded-connect-retries7.5.4. forwarded-connect-retries

    7.5.5. accept-intercepted-requests7.5.5. accept-intercepted-requests

    7.5.6. allow-cgi-request-crunching

    Specifies:

    Whether requests to Privoxy's CGI pages can be blocked or redirected. +

    Type of value:

    0 or 1 +

    Default value:

    0

    Effect if unset:

    Privoxy ignores block and redirect actions for its CGI pages. +

    Notes:

    By default Privoxy ignores block or redirect actions + for its CGI pages. Intercepting these requests can be useful in multi-user + setups to implement fine-grained access control, but it can also render the complete + web interface useless and make debugging problems painful if done without care. +

    Don't enable this option unless you're sure that you really need it. +

    Examples:

    allow-cgi-request-crunching 1 +

    7.5.6. split-large-forms

    7.5.7. split-large-forms

    7.6. Windows GUI Options7.6. Windows GUI Options

    Privoxy Configuration6. Privoxy Configuration6. Privoxy Configuration

    All

    6.1. Controlling Privoxy with Your Web Browser

    6.1. Controlling Privoxy with Your Web Browser

        Privoxy Menu

    6.2. Configuration Files Overview6.2. Configuration Files Overview

    For Unix, *BSD and Linux, all configuration files are located in Privoxy executable.

    executable. The name + and number of configuration files has changed from previous versions, and is + subject to change as development progresses.

    The installed defaults provide a reasonable starting point, though some settings may be aggressive by some standards. For the time being, the @@ -379,15 +381,9 @@ CLASS="FILENAME" >

    The syntax of all configuration files has remained the same throughout the - 3.x series. There have been enhancements, but no changes that would preclude - the use of any configuration file from one version to the next. (There is - one exception: +fast-redirects which - has enhanced syntax and will require updating any local configs from earlier - versions.)

    The syntax of the configuration and filter files may change between different + Privoxy versions, unfortunately some enhancements cost backwards compatibility. +

    All files use the old listening address.

    While under development, the configuration content is subject to change. + The below documentation may not be accurate by the time you read this. + Also, what constitutes a "default" setting, may change, so + please check all your configuration files on important issues.

    <META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK REL="HOME" TITLE="Privoxy 3.0.7 User Manual" HREF="index.html"><LINK @@ -77,9 +77,9 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="CONTACT" -></A >11. Contacting the Developers, Bug Reporting and Feature -Requests</H1 +Requests</A +></H1 ><P > We value your feedback. In fact, we rely on it to improve <SPAN @@ -94,8 +94,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="CONTACT-SUPPORT" -></A ->11.1. Get Support</H2 +>11.1. Get Support</A +></H2 ><P > For casual users, our <A @@ -116,6 +116,17 @@ TARGET="_top" >users mailing list</A >, where the developers also hang around.</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" @@ -123,8 +134,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="REPORTING" -></A ->11.2. Reporting Problems</H2 +>11.2. Reporting Problems</A +></H2 ><P ><SPAN CLASS="QUOTE" @@ -168,8 +179,8 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="CONTACT-ADS" -></A ->11.2.1. Reporting Ads or Other Configuration Problems</H3 +>11.2.1. Reporting Ads or Other Configuration Problems</A +></H3 ><P > 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 @@ -210,17 +221,10 @@ CLASS="SECT3" CLASS="SECT3" ><A NAME="CONTACT-BUGS" -></A ->11.2.2. Reporting Bugs</H3 +>11.2.2. Reporting Bugs</A +></H3 ><P -> Please report all bugs <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->only</I -></SPAN -> through our - bug tracker: +> Please report all bugs through our bug tracker: <A HREF="http://sourceforge.net/tracker/?group_id=11118&atid=111118" TARGET="_top" @@ -242,12 +246,12 @@ TARGET="_top" >. If already submitted, please feel free to add any info to the original report that might help to solve the issue.</P ><P -> - Please try to verify that it is a <SPAN +> Please try to verify that it is a <SPAN CLASS="APPLICATION" >Privoxy</SPAN > bug, - and not a browser or site bug first. If unsure, + and not a browser or site bug 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" @@ -256,11 +260,14 @@ TARGET="_top" > <SPAN CLASS="APPLICATION" >Privoxy</SPAN ->, 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.</P +>, and see if the problem persists.</P +><P +> 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.</P ><P -> If not using the latest version, the bug may have been found +> 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 <A HREF="http://www.privoxy.org/user-manual/installation.html" @@ -268,7 +275,7 @@ TARGET="_top" >upgrade to the latest version</A > (or even the latest CVS snapshot) and verify - your bug.</P + that your bug still exists.</P ><P >Please be sure to provide the following information:</P ><P @@ -280,7 +287,7 @@ TARGET="_top" > The exact <SPAN CLASS="APPLICATION" >Privoxy</SPAN -> version of the proxy software +> version you are using (if you got the source from CVS, please also provide the source code revisions as shown in <A HREF="http://config.privoxy.org/show-version" @@ -303,7 +310,8 @@ CLASS="APPLICATION" sending the output of <SPAN CLASS="QUOTE" >"uname -a"</SPAN -> should do. +> should do, + in case of GNU/Linux, please also name the distribution. </P ></LI ><LI @@ -333,11 +341,11 @@ CLASS="LITERAL" CLASS="APPLICATION" >Privoxy</SPAN > is one supplied - by the developers of <SPAN + by the <SPAN CLASS="APPLICATION" >Privoxy</SPAN -> via SourceForge, - or somewhere else. +> developers via SourceForge, + or if you got your copy somewhere else. </P ></LI ><LI @@ -349,8 +357,8 @@ CLASS="APPLICATION" another proxy such as <SPAN CLASS="APPLICATION" >Tor</SPAN ->. If so, please try - disabling the other proxy. +>. If so, please + temporary disable the other proxy to see if the symptoms change. </P ></LI ><LI @@ -369,21 +377,19 @@ CLASS="APPLICATION" action taken). </P ></LI -><LI -><P -> <SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->Please provide your SF login, or email address</I -></SPAN ->, in case we - need to contact you. - </P -></LI ></UL ></P ><P +> 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.</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.</P +><P > The <A HREF="http://www.privoxy.org/user-manual/appendix.html#ACTIONSANAT" TARGET="_top" @@ -405,8 +411,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="CONTACT-FEATURE" -></A ->11.3. Request New Features</H2 +>11.3. Request New Features</A +></H2 ><P > You are welcome to submit ideas on new features or other proposals for improvement through our feature request tracker at @@ -422,8 +428,8 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="CONTACT-OTHER" -></A ->11.4. Other</H2 +>11.4. Other</A +></H2 ><P >For any other issues, feel free to use the mailing lists. Technically interested users and people who wish to contribute to the project are also welcome on the developers list! diff --git a/doc/webserver/user-manual/copyright.html b/doc/webserver/user-manual/copyright.html index 988219f4..6403fbac 100644 --- a/doc/webserver/user-manual/copyright.html +++ b/doc/webserver/user-manual/copyright.html @@ -1,11 +1,11 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd"> <HTML ><HEAD ><TITLE >Privoxy Copyright, License and History12. Privoxy Copyright, License and History12. Privoxy Copyright, License and History

    Copyright © 2001 - 2006 by Privoxy Developers Copyright © 2001 - 2007 by Privoxy Developers

    Some source code is based on code Copyright © 1997 by Anonymous Coders @@ -99,9 +99,9 @@ CLASS="SECT2" >

    12.1. License

    12.1. License

    12.2. History12.2. History

    A long time ago, there was the 12.3. Authors12.3. Authors

    Current Privoxy Team:

     Ken Arromdee
     Devin Bayer
     Reiner Buehl
    + Gergely Bor
     Andrew J. Caines
     Clifford Caoile
     Frédéric Crozat
    @@ -303,25 +304,35 @@ CLASS="LITERALLAYOUT"  Mattes Dolak 
     Peter E
     Florian Effenberger
    + Markus Elfring
     Dean Gaudet
    + Stephen Gildea
    + Daniel Griscom
    + Felix Gröbert
     Aaron Hamid
     Darel Henman
     Magnus Holmgren
    + Peter Hyman
     Derek Jennings
    + Petr Kadlec
     David Laight
     Don Libes  
     Paul Lieverse
    + Toby Lyward
    + Wil Mahan
     Jindrich Makovicka 
     David Mediavilla 
     Raphael Moll
     Adam Piggott
    - Oliver Stoeneberg
    - Martin Thomas
     Roberto Ragusa
     Félix Rauch
     Maynard Riley
    + Chung-chieh Shan
     Spinor S
     Bart Schelstraete
    + Oliver Stoeneberg
    + Peter Thoenen
    + Martin Thomas
     Bobby G. Vinyard
     Jörg Weinmann 
     Darren Wiebe
    @@ -334,8 +345,8 @@ CLASS="LITERALLAYOUT" CLASS="LITERALLAYOUT" > Junkbusters Corp.
     Anonymous Coders
    - Ulrich Drepper
    - Philip Hazel

    + Philip Hazel (PCRE)

    Filter Files9. Filter Files9. Filter Files

    On-the-fly text substitutions need to be defined in a

    9.1. Filter File Tutorial

    9.1. Filter File Tutorial

    Now, let's complete our 9.2. The Pre-defined Filters9.2. The Pre-defined Filters

    The distribution Privoxy 3.0.7 User ManualPrivoxy 3.0.7 User ManualPrivoxy 3.0.7 User Manual


    $Id: user-manual.sgml,v 2.32 2007/06/07 12:36:22 fabiankeil Exp $

    $Id: user-manual.sgml,v 2.38 2007/09/22 16:01:42 fabiankeil Exp $

    The Privoxy User Manual

    6.1. Controlling Privoxy with Your Web Browser
    7.5.6. allow-cgi-request-crunching
    7.5.7. split-large-forms
    8.1. Finding the Right Mix
    8.2. How to Edit
    8.4.1. The Domain Pattern
    8.4.2. The Path Pattern
    8.5.39. Summary
    8.7.1. default.action
    8.7.2. user.action
    9.1. Filter File Tutorial
    12.1. License
    14.2. Privoxy's Internal Pages
    Installation2. Installation2. Installation

    2.1. Binary Packages2.1. Binary Packages

    How to install the binary packages depends on your operating system:

    2.1.1. Red Hat and Fedora RPMs2.1.1. Red Hat and Fedora RPMs

    RPMs can be installed with 2.1.2. Debian2.1.2. Debian

    DEBs can be installed with 2.1.3. Windows2.1.3. Windows

    Just double-click the installer, which will guide you through the installation process. You will find the configuration files @@ -306,8 +306,8 @@ CLASS="SECT3" CLASS="SECT3" >2.1.4. Solaris, NetBSD, HP-UX2.1.4. Solaris, NetBSD, HP-UX

    Create a new directory, 2.1.5. OS/22.1.5. OS/2

    First, make sure that no previous installations of 2.1.6. Mac OSX2.1.6. Mac OSX

    Unzip the downloaded file (you can either double-click on the file from the finder, or from the desktop if you downloaded it there). @@ -424,8 +424,8 @@ CLASS="SECT3" CLASS="SECT3" >2.1.7. AmigaOS2.1.7. AmigaOS

    Copy and then unpack the 2.1.8. FreeBSD2.1.8. FreeBSD

    Privoxy is part of FreeBSD's Ports Collection, you can build and install it with 2.1.9. Gentoo2.1.9. Gentoo

    Gentoo source packages (Ebuilds) for 2.2. Building from Source2.2. Building from Source

    The most convenient way to obtain the 

     tar xzvf privoxy-3.0.7-src* [.tgz or .tar.gz]
- cd privoxy-3.0.7
    tar xzvf privoxy-3.0.7-beta-src* [.tgz or .tar.gz] + cd privoxy-3.0.7-beta2.3. Keeping your Installation Up-to-Date2.3. Keeping your Installation Up-to-Date

    As user feedback comes in and development continues, we will make updated versions of both the main Introduction1. Introduction1. Introduction

    This documentation is included with the current stable version of +> This documentation is included with the current UNRELEASED version of Privoxy, v.3.0.7.

    , v.3.0.7, + and is mostly complete at this point. The most up to date reference for the + time being is still the comments in the source files and in the individual + configuration files. Development of a new version is currently nearing + completion, and includes significant changes and enhancements over + earlier versions. .

    Since this is a UNRELEASED version, not all new features are well tested. This + documentation may be slightly out of sync as a result (especially with + CVS sources). And there may be bugs, though hopefully + not many!

    1.1. Features

    1.1. Features

    In addition to the core features of ad blocking and @@ -104,7 +120,7 @@ TARGET="_top" CLASS="APPLICATION" >Privoxy provides many supplemental - features, + features, some of them currently under development, that give the end-user more control, more privacy and more freedom:

    Quickstart to Using Privoxy4. Quickstart to Using Privoxy4. Quickstart to Using Privoxy

    4.1. Quickstart to Ad Blocking4.1. Quickstart to Ad Blocking

    Ad blocking is but one of

    See Also13. See Also13. See Also

    Other references and sites of interest to Starting Privoxy5. Starting Privoxy5. Starting Privoxy

    Before launching

    5.1. Red Hat and Fedora5.1. Red Hat and Fedora

    A default Red Hat installation may not start 5.2. Debian5.2. Debian

    We use a script. Note that Debian typically starts 5.3. Windows5.3. Windows

    Click on the 5.4. Solaris, NetBSD, FreeBSD, HP-UX and others5.4. Solaris, NetBSD, FreeBSD, HP-UX and others

    Example Unix startup command:

    5.5. OS/25.5. OS/2

    During installation, 5.6. Mac OSX5.6. Mac OSX

    During installation, 5.7. AmigaOS5.7. AmigaOS

    Start 5.8. Gentoo5.8. Gentoo

    A script is again used. It will use the file 5.9. Command Line Options5.9. Command Line Options

    --pidfile FILE -

    On startup, write the process ID to --user USER[.GROUP] -

    After (optionally) writing the PID file, assume the user ID of @@ -742,7 +740,6 @@ CLASS="EMPHASIS" >--chroot -

    Before changing to the user ID given in the

  • --pre-chroot-nslookup hostname +

    Specifies a hostname to look up before doing a chroot. On some systems, initializing the + resolver library involves reading config files from /etc and/or loading additional shared + libraries from /lib. On these systems, doing a hostname lookup before the chroot reduces + the number of files that must be copied into the chroot tree. +

    For fastest startup speed, a good value is a hostname that is not in /etc/hosts but that + your local name server (listed in /etc/resolv.conf) can resolve without recursion + (that is, without having to ask any other name servers). The hostname need not exist, + but if it doesn't, an error message (which can be ignored) will be output. +

  • Privoxy's Template Files10. Privoxy's Template Files10. Privoxy's Template Files

    All What's New in this Release3. What's New in this Release3. What's New in this Release

    There are many improvements and new features since 3.1. Note to Upgraders3.1. Note to Upgraders

    A quick list of things to be aware of before upgrading from earlier versions of