X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Ffaq%2Fconfiguration.html;h=daf8ae1f5b9983a191e1b3fe4a0dded3e8973413;hp=2c19d28e70e7028df09150415da31b14fdbe5e68;hb=7cffc51606453083eb5ac1ddeb726d0569991e5f;hpb=6d810395712f0337682205c4ea304009c86c128f diff --git a/doc/webserver/faq/configuration.html b/doc/webserver/faq/configuration.html index 2c19d28e..daf8ae1f 100644 --- a/doc/webserver/faq/configuration.html +++ b/doc/webserver/faq/configuration.html @@ -1,215 +1,194 @@ - + + -
- -- 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.
+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, + ijbswa-announce@lists.sourceforge.net.
+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.
- 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, - ijbswa-announce@lists.sourceforge.net. -
-- 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. Those that are familiar with some of the underlying - concepts, such as regular expression syntax, take to it like a fish - takes to water. Also, software that tries hard to be "user friendly", often lacks sophistication and - flexibility. There is always that trade-off there between power vs. - easy-of-use. Furthermore, anyone is welcome to contribute ideas and - implementations to enhance Privoxy. -
-- 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: -
--
-
-+ + |