X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fuser-manual.sgml;h=ccf8c6230cdbf9eb833a324926d0ddc6da79ed42;hp=dd1bebf9353fc6e472d9f516eef69d35a5e40acf;hb=dc1f592446fbced35169930697f4aa2b2ba21585;hpb=4c292377c13c2648634249198c8aebdca5200b8c diff --git a/doc/source/user-manual.sgml b/doc/source/user-manual.sgml index dd1bebf9..ccf8c623 100644 --- a/doc/source/user-manual.sgml +++ b/doc/source/user-manual.sgml @@ -11,11 +11,11 @@ - - + + - - + + @@ -34,7 +34,7 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: user-manual.sgml,v 2.143 2011/11/20 17:16:36 fabiankeil Exp $ + $Id: user-manual.sgml,v 2.153 2012/11/09 10:49:59 fabiankeil Exp $ Copyright (C) 2001-2011 Privoxy Developers http://www.privoxy.org/ See LICENSE. @@ -60,7 +60,7 @@ -$Id: user-manual.sgml,v 2.143 2011/11/20 17:16:36 fabiankeil Exp $ +$Id: user-manual.sgml,v 2.153 2012/11/09 10:49:59 fabiankeil Exp $ Mac OS X - Unzip the downloaded file (you can either double-click on the zip file - icon from the Finder, or from the desktop if you downloaded it there). - Then, double-click on the package installer icon and follow the - installation process. + Installation instructions for the OS X platform depend upon whether + you downloaded a ready-built installation package (.pkg or .mpkg) or have + downloaded the source code. + +Installation from ready-built package - The privoxy service will automatically start after a successful - installation (in addition to every time your computer starts up). To - prevent the privoxy service from automatically starting when your - computer starts up, remove or rename the folder named - /Library/StartupItems/Privoxy. + The downloaded file will either be a .pkg (for OS X 10.5 upwards) or a bzipped + .mpkg file (for OS X 10.4). The former can be double-clicked as is and the + installation will start; double-clicking the latter will unzip the .mpkg file + which can then be double-clicked to commence the installation. + + + The privoxy service will automatically start after a successful installation + (and thereafter every time your computer starts up) however you will need to + configure your web browser(s) to use it. To do so, configure them to use a + proxy for HTTP and HTTPS at the address 127.0.0.1:8118. + + + To prevent the privoxy service from automatically starting when your computer + starts up, remove or rename the file /Library/LaunchDaemons/org.ijbswa.privoxy.plist + (on OS X 10.5 and higher) or the folder named + /Library/StartupItems/Privoxy (on OS X 10.4 'Tiger'). + + + To manually start or stop the privoxy service, use the scripts startPrivoxy.sh + and stopPrivoxy.sh supplied in /Applications/Privoxy. They must be run from an + administrator account, using sudo. + + + To uninstall, run /Applications/Privoxy/uninstall.command as sudo from an + administrator account. + + +Installation from source + + To build and install the Privoxy source code on OS X you will need to obtain + the macsetup module from the Privoxy Sourceforge CVS repository (refer to + Sourceforge help for details of how to set up a CVS client to have read-only + access to the repository). This module contains scripts that leverage the usual + open-source tools (available as part of Apple's free of charge Xcode + distribution or via the usual open-source software package managers for OS X + (MacPorts, Homebrew, Fink etc.) to build and then install the privoxy binary + and associated files. The macsetup module's README file contains complete + instructions for its use. + + + The privoxy service will automatically start after a successful installation + (and thereafter every time your computer starts up) however you will need to + configure your web browser(s) to use it. To do so, configure them to use a + proxy for HTTP and HTTPS at the address 127.0.0.1:8118. + + + To prevent the privoxy service from automatically starting when your computer + starts up, remove or rename the file /Library/LaunchDaemons/org.ijbswa.privoxy.plist + (on OS X 10.5 and higher) or the folder named + /Library/StartupItems/Privoxy (on OS X 10.4 'Tiger'). To manually start or stop the privoxy service, use the Privoxy Utility - for Mac OS X. This application controls the privoxy service (e.g. - starting and stopping the service as well as uninstalling the software). + for Mac OS X (also part of the macsetup module). This application can start + and stop the privoxy service and display its log and configuration files. + + + To uninstall, run the macsetup module's uninstall.sh as sudo from an + administrator account. @@ -437,13 +487,73 @@ How to install the binary packages depends on your operating system: What's New in this Release - Privoxy 3.0.18 is a stable release. - The changes since 3.0.17 stable are: + Privoxy 3.0.19 is a stable release. + The changes since 3.0.18 stable are: + + Bug fixes: + + + + Prevent a segmentation fault when de-chunking buffered content. + It could be triggered by malicious web servers if Privoxy was + configured to filter the content and running on a platform + where SIZE_T_MAX isn't larger than UINT_MAX, which probably + includes most 32-bit systems. On those platforms, all Privoxy + versions before 3.0.19 appear to be affected. + To be on the safe side, this bug should be presumed to allow + code execution as proving that it doesn't seems unrealistic. + + + + + Do not expect a response from the SOCKS4/4A server until it + got something to respond to. This regression was introduced + in 3.0.18 and prevented the SOCKS4/4A negotiation from working. + Reported by qqqqqw in #3459781. + + + + + + + + General improvements: + + + + Fix an off-by-one in an error message about connect failures. + + + + + Use a GNUMakefile variable for the webserver root directory and + update the path. Sourceforge changed it which broke various + web-related targets. + + + + + Update the CODE_STATUS description. + + + + + + + + + + The following changes were made between 3.0.17 and 3.0.18: + + + + + Bug fixes: @@ -2328,6 +2438,27 @@ must find a better place for this paragraph + + + --config-test + + + Exit after loading the configuration files before binding to + the listen address. The exit code signals whether or not the + configuration files have been successfully loaded. + + + If the exit code is 1, at least one of the configuration files + is invalid, if it is 0, all the configuration files have been + successfully loaded (but may still contain errors that can + currently only be detected at run time). + + + This option doesn't affect the log setting, combination with + --no-daemon is recommended if a configured + log file shouldn't be used. + + --version @@ -3839,7 +3970,7 @@ for details. and use their output as input. - If the request URL gets changed, &my-app; will detect that and use the new + If the request URI gets changed, &my-app; will detect that and use the new one. This can be used to rewrite the request destination behind the client's back, for example to specify a Tor exit relay for certain requests. @@ -3861,7 +3992,7 @@ for details. {+client-header-filter{hide-tor-exit-notation}} / - + @@ -3955,6 +4086,22 @@ TAG:^User-Agent: fetch libfetch/ TAG:^User-Agent: Ubuntu APT-HTTP/ TAG:^User-Agent: MPlayer/ + + + +# Tag all requests with the Range header set +{+client-header-tagger{range-requests}} +/ + +# Disable filtering for the tagged requests. +# +# With filtering enabled Privoxy would remove the Range headers +# to be able to filter the whole response. The downside is that +# it prevents clients from resuming downloads or skipping over +# parts of multimedia files. +{-filter -deanimate-gifs} +TAG:^RANGE-REQUEST$ + @@ -5929,6 +6076,94 @@ new action + + + +limit-cookie-lifetime + + + + Typical use: + + Limit the lifetime of HTTP cookies to a couple of minutes or hours. + + + + + Effect: + + + Overwrites the expires field in Set-Cookie server headers if it's above the specified limit. + + + + + + Type: + + + Parameterized. + + + + + Parameter: + + + The lifetime limit in minutes, or 0. + + + + + + Notes: + + + This action reduces the lifetime of HTTP cookies coming from the + server to the specified number of minutes, starting from the time + the cookie passes Privoxy. + + + Cookies with a lifetime below the limit are not modified. + The lifetime of session cookies is set to the specified limit. + + + The effect of this action depends on the server. + + + In case of servers which refresh their cookies with each response + (or at least frequently), the lifetime limit set by this action + is updated as well. + Thus, a session associated with the cookie continues to work with + this action enabled, as long as a new request is made before the + last limit set is reached. + + + However, some servers send their cookies once, with a lifetime of several + years (the year 2037 is a popular choice), and do not refresh them + until a certain event in the future, for example the user logging out. + In this case this action may limit the absolute lifetime of the session, + even if requests are made frequently. + + + If the parameter is 0, this action behaves like + session-cookies-only. + + + + + + Example usages: + + + +limit-cookie-lifetime{60} + + + + + + + prevent-compression @@ -6185,6 +6420,10 @@ new action either provided as parameter, or derived by applying a single pcrs command to the original URL. + + The syntax for pcrs commands is documented in the + filter file section. + This action will be ignored if you use it together with block. @@ -7805,7 +8044,7 @@ pre-defined filters for your convenience: - refresh tags + refresh-tags Disable any refresh tags if the interval is greater than nine seconds (so @@ -9380,6 +9619,40 @@ In file: user.action [ View ] [ Edit ]