X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Ffaq%2Fconfiguration.html;h=3f1c67a0b5941056539a8c774d687685a8f5c1f5;hp=20d8bb9d04e8bf54db54015bfdde0be29191aa04;hb=6de6bda5b29cbb5a8aef6863c1b5ca999ab4887b;hpb=94a4fa45e28600ad0e1e0455bda3ee4fd0303ffe;ds=sidebyside diff --git a/doc/webserver/faq/configuration.html b/doc/webserver/faq/configuration.html index 20d8bb9d..3f1c67a0 100644 --- a/doc/webserver/faq/configuration.html +++ b/doc/webserver/faq/configuration.html @@ -1,219 +1,166 @@ - + -
-- Privoxy Frequently Asked Questions - | -||
---|---|---|
- Prev - | -- | -- Next - | -
Privoxy utilizes the concept of + " actions" that are used to manipulate and control web + page data. Actions files are where these actions + that Privoxy could take while + processing a certain request, are configured. Typically, you would + define a set of default actions that apply globally to all URLs, then + add exceptions to these defaults where needed. There is a wide array of + actions available that give the user a high degree of control and + flexibility on how to process each and every web page.
+Actions can be defined on a URL + pattern basis, i.e. for single URLs, whole web sites, groups or + parts thereof etc. Actions can also be grouped together and then + applied to requests matching one or more patterns. There are many + possible actions that might apply to any given site. As an example, if + you are blocking cookies as one of your default actions, but need to + accept cookies from a given site, you would need to define an exception + for this site in one of your actions files, preferably in user.action.
+For a comprehensive discussion of the actions concept, please refer + to the actions + file chapter in the User Manual. It includes a list of all + actions and an actions + file tutorial to get you started.
+Actions files are just text files in a special syntax and can be + edited with a text editor. But probably the easiest way is to access + Privoxy's user interface with your web + browser at http://config.privoxy.org/ (Shortcut: http://p.p/) and then select "View & change the current configuration" from the + menu. Note that this feature must be explicitly enabled in the main + config file (see enable-edit-actions).
+Please have a look at the the actions chapter in the User Manual for a + detailed explanation.
- Privoxy utilizes the concept of - " actions" that are used to manipulate and control - web page data. Actions files are where these actions that Privoxy - could take while processing a certain request, are configured. - Typically, you would define a set of default actions that apply - globally to all URLs, then add exceptions to these defaults where - needed. There is a wide array of actions available that give the - user a high degree of control and flexibility on how to process - each and every web page. -
-- Actions can be defined on a URL - pattern basis, i.e. for single URLs, whole web sites, groups or - parts thereof etc. Actions can also be grouped together and then - applied to requests matching one or more patterns. There are many - possible actions that might apply to any given site. As an example, - if you are blocking cookies as one of your default actions, but need to - accept cookies from a given site, you would need to define an - exception for this site in one of your actions files, preferably in - user.action. -
-- For a comprehensive discussion of the actions concept, please refer - to the actions file chapter in the User Manual. It - includes a list of all actions and an actions file tutorial to get you started. -
-- Actions files are just text files in a special syntax and can be - edited with a text editor. But probably the easiest way is to - access Privoxy's user interface - with your web browser at http://config.privoxy.org/ (Shortcut: http://p.p/) and then select "View & change the current - configuration" from the menu. Note that this feature - must be explicitly enabled in the main config file (see enable-edit-actions). -
-- Please have a look at the the actions - chapter in the User Manual for a detailed explanation. -
-- Based on your feedback and the continuing development, updates of - default.action will be made available - from time to time on the files section of our project - page. -
-- If you wish to receive an email notification whenever we release - updates of Privoxy or the actions - file, subscribe to our announce mailing list, - privoxy-announce@lists.privoxy.org. -
-- The syntax and purpose of configuration files has remained roughly - the same throughout the 3.x series, but backwards compatibility is - not guaranteed. Also each release contains updated, "improved" versions and it is therefore strongly - recommended to install the newer configuration files and merge back - your modifications. -
-- "Complicated" is in the eye of the - beholder. -
-- Privoxy is currently mainly written by and for people who are - already familiar with the underlying concepts like regular - expressions, HTTP and HTML, or are willing to become familiar with - them to be able to get the most out of a powerful and flexible tool - such as Privoxy. -
-- While everybody is expected to be able to get a Privoxy default - installation up and running, fine-tuning requires a certain amount - of background information and Privoxy's documentation mainly - concentrates on the Privoxy-specific parts while only providing - references to the rest. -
-- If you or anyone you know has the skills, time and energy to reduce - the barrier of entry, please get - involved. -
-- The default configuration shouldn't impact the usability of any of - these services. It may, however, make all cookies temporary, so that your browser will forget your - login credentials in between browser sessions. If you would like - not to have to log in manually each time you access those websites, - simply turn off all cookie handling for them in the user.action file. An example for yahoo might look - like: -
--
-
--# Allow all cookies for Yahoo login: + |