The actions files are used to define what actions Privoxy takes for which URLs, and thus determine how ad images, cookies and various other aspects of HTTP content and transactions are handled, and on which sites (or even parts thereof). There are three such files included with Privoxy with differing purposes:
default.action - is the primary action file that sets the initial values for all actions. It is intended to provide a base level of functionality for Privoxy's array of features. So it is a set of broad rules that should work reasonably well for users everywhere. This is the file that the developers are keeping updated, and making available to users.
user.action - is intended to be for local site preferences and exceptions. As an example, if your ISP or your bank has specific requirements, and need special handling, this kind of thing should go here. This file will not be upgraded.
standard.action - is used by the web based editor, to set various pre-defined sets of rules for the default actions section in default.action. These have increasing levels of aggressiveness and have no influence on your browsing unless you select them explicitly in the editor. It is not recommend to edit this file.
The default profiles, and their associated actions, as pre-defined in standard.action are:
Table 1. Default Configurations
| Feature | Cautious | Medium | Adventuresome |
|---|---|---|---|
| Ad-blocking by URL | yes | yes | yes |
| Ad-filtering by size | yes | yes | yes |
| GIF de-animation | no | yes | yes |
| Referer forging | no | yes | yes |
| Cookie handling | none | session-only | kill |
| Pop-up killing | unsolicited | unsolicited | all |
| Fast redirects | no | no | yes |
| HTML taming | yes | yes | yes |
| JavaScript taming | yes | yes | yes |
| Web-bug killing | yes | yes | yes |
| Fun text replacements | no | no | yes |
| Image tag reordering | no | no | yes |
| Ad-filtering by link | no | no | yes |
| Demoronizer | no | no | yes |
The list of actions files to be used are defined in the main configuration file, and are processed in the order they are defined (e.g. default.action is typically process before user.action). The content of these can all be viewed and edited from http://config.privoxy.org/show-status.
An actions file typically has multiple sections. If you want to use "aliases" in an actions file, you have to place the (optional) alias section at the top of that file. Then comes the default set of rules which will apply universally to all sites and pages (be very careful with using such a universal set in user.action or any other actions file after default.action, because it will override the result from consulting any previous file). And then below that, exceptions to the defined universal policies. You can regard user.action as an appendix to default.action, with the advantage that is a separate file, which makes preserving your personal settings across Privoxy upgrades easier.
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 or rejected, or accepted only during the current browser session (i.e. not written to disk), content can be modified, JavaScripts tamed, user-tracking fooled, and much more. See below for a complete list of actions.
Note that some actions, like cookie suppression or script disabling, may render some sites unusable that rely on these techniques to work properly. Finding the right mix of actions is not always easy and certainly a matter of personal taste. In general, it can be said that the more "aggressive" your default settings (in the top section of the actions file) are, the more exceptions for "trusted" sites you will have to make later. If, for example, you want to crunch all cookies per default, you'll have to make exceptions from that rule for sites that you regularly use and that require cookies for actually useful puposes, like maybe your bank, favorite shop, or newspaper.
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 things. There just are too many variables, and sites are constantly changing. Sooner or later you will want to change the rules (and read this chapter again :).
The easiest way to edit the actions files is with a browser by using our browser-based editor, which can be reached from http://config.privoxy.org/show-status. The editor allows both fine-grained control over every single feature on a per-URL basis, and easy choosing from wholesale sets of defaults like "Cautious", "Medium" or "Adventuresome". Warning: the "Adventuresome" setting is not only more aggressive, but includes settings that are fun and subversive, and which some may find of dubious merit!
If you prefer plain text editing to GUIs, you can of course also directly edit the the actions files. Look at default.action which is richly commented.
Actions files are divided into sections. There are special sections, like the "alias" sections which will be discussed later. For now let's concentrate on regular sections: They have a heading line (often split up to multiple lines for readability) which consist of a list of actions, separated by whitespace and enclosed in curly braces. Below that, there is a list of URL patterns, each on a separate line.
To determine which actions apply to a request, the URL of the request is compared to all patterns in each action file file. Every time it matches, the list of applicable actions for the URL is incrementally updated, using the heading of the section in which er aspP content and transactions are handled, and on which sites (or even parts thereof). There are three such files included with Privoxy with differing purposes:
default.action - is the primary action file that sets the initial values for all actions. It is intended to provide a base level of functionality for Privoxy's array of features. So it is a set of broad rules that should work reasonably well for users everywhere. This is the file that the developers are keeping updated, and making available to users.
user.action - is intended to be for local site preferences and exceptions. As an example, if your ISP or your bank has specific requirements, and need special handling, this kind of thing should go here. This file will not be upgraded.
standard.action - is used by the web based editor, to set various pre-defined sets of rules for the default actions section in default.action. These have increasing levels of aggressiveness and have no influence on your browsing unless you select them explicitly in the editor. It is not recommend to edit this file.
The default profiles, and their associated actions, as pre-defined in standard.action are:
Table 1. Default Configurations
| Feature | Cautious | Medium | Adventuresome |
|---|---|---|---|
| Ad-blocking by URL | yes | yes | yes |
| Ad-filtering by size | yes | yes | yes |
| GIF de-animation | no | yes | yes |
| Referer forging | no | yes | yes |
| Cookie handling | none | session-only | kill |
| Pop-up killing | unsolicited | unsolicited | all |
| Fast redirects | no | no | yes |
| HTML taming | yes | yes | yes |
| JavaScript taming | yes | yes | yes |
| Web-bug killing | yes | yes | yes |
| Fun text replacements | no | no | yes |
| Image tag reordering | no | no | yes |
| Ad-filtering by link | no | no | yes |
| Demoronizer | no | no | yes |
The list of actions files to be used are defined in the main configuration file, and are processed in the order they are defined (e.g. default.action is typically process before user.action). The content of these can all be viewed and edited from http://config.privoxy.org/show-status.
An actions file typically has multiple sections. If you want to use "aliases" in an actions file, you have to place the (optional) alias section at the top of that file. Then comes the default set of rules which will apply universally to all sites and pages (be very careful with using such a universal set in user.action or any other actions file after default.action, because it will override the result from consulting any previous file). And then below that, exceptions to the defined universal policies. You can regard user.action as an appendix to default.action, with the advantage that is a separate file, which makes preserving your personal settings across Privoxy upgrades easier.
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 or rejected, or accepted only during the current browser session (i.e. not written to disk), content can be modified, JavaScripts tamed, user-tracking fooled, and much more. See below for a complete list of actions.
Note that some actions, like cookie suppression or script disabling, may render some sites unusable that rely on these techniques to work properly. Finding the right mix of actions is not always easy and certainly a matter of personal taste. In general, it can be said that the more "aggressive" your default settings (in the top section of the actions file) are, the more exceptions for "trusted" sites you will have to make later. If, for example, you want to crunch all cookies per default, you'll have to make exceptions from that rule for sites that you regularly use and that require cookies for actually useful puposes, like maybe your bank, favorite shop, or newspaper.
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 things. There just are too many variables, and sites are constantly changing. Sooner or later you will want to change the rules (and read this chapter again :).
The easiest way to edit the actions files is with a browser by using our browser-based editor, which can be reached from http://config.privoxy.org/show-status. The editor allows both fine-grained control over every single feature on a per-URL basis, and easy choosing from wholesale sets of defaults like "Cautious", "Medium" or "Adventuresome". Warning: the "Adventuresome" setting is not only more aggressive, but includes settings that are fun and subversive, and which some may find of dubious merit!
If you prefer plain text editing to GUIs, you can of course also directly edit the the actions files. Look at default.action which is richly commented.
Actions files are divided into sections. There are special sections, like the "alias" sections which will be discussed later. For now let's concentrate on regular sections: They have a heading line (often split up to multiple lines for readability) which consist of a list of actions, separated by whitespace and enclosed in curly braces. Below that, there is a list of URL patterns, each on a separate line.
To determine which actions apply to a request, the URL of the request is compared to all patterns in each action file file. Every time it matches, the list of applicable actions for the URL is incrementally updated, using the heading of the section in which er aspP content and transactions are handled, and on which sites (or even parts thereof). There are three such files included with Privoxy with differing purposes:
default.action - is the primary action file that sets the initial values for all actions. It is intended to provide a base level of functionality for Privoxy's array of features. So it is a set of broad rules that should work reasonably well for users everywhere. This is the file that the developers are keeping updated, and making available to users.
user.action - is intended to be for local site preferences and exceptions. As an example, if your ISP or your bank has specific requirements, and need special handling, this kind of thing should go here. This file will not be upgraded.
standard.action - is used by the web based editor, to set various pre-defined sets of rules for the default actions section in default.action. These have increasing levels of aggressiveness and have no influence on your browsing unless you select them explicitly in the editor. It is not recommend to edit this file.
The default profiles, and their associated actions, as pre-defined in standard.action are:
Table 1. Default Configurations
| Feature | Cautious | Medium | Adventuresome |
|---|---|---|---|
| Ad-blocking by URL | yes | yes | yes |
| Ad-filtering by size | yes | yes | yes |
| GIF de-animation | no | yes | yes |
| Referer forging | no | yes | yes |
| Cookie handling | none | session-only | kill |
| Pop-up killing | unsolicited | unsolicited | all |
| Fast redirects | no | no | yes |
| HTML taming | yes | yes | yes |
| JavaScript taming | yes | yes | yes |
| Web-bug killing | yes | yes | yes |
| Fun text replacements | no | no | yes |
| Image tag reordering | no | no | yes |
| Ad-filtering by link | no | no | yes |
| Demoronizer | no | no | yes |
The list of actions files to be used are defined in the main configuration file, and are processed in the order they are defined (e.g. default.action is typically process before user.action). The content of these can all be viewed and edited from http://config.privoxy.org/show-status.
An actions file typically has multiple sections. If you want to use "aliases" in an actions file, you have to place the (optional) alias section at the top of that file. Then comes the default set of rules which will apply universally to all sites and pages (be very careful with using such a universal set in user.action or any other actions file after default.action, because it will override the result from consulting any previous file). And then below that, exceptions to the defined universal policies. You can regard user.action as an appendix to default.action, with the advantage that is a separate file, which makes preserving your personal settings across Privoxy upgrades easier.
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 or rejected, or accepted only during the current browser session (i.e. not written to disk), content can be modified, JavaScripts tamed, user-tracking fooled, and much more. See below for a complete list of actions.
Note that some actions, like cookie suppression or script disabling, may render some sites unusable that rely on these techniques to work properly. Finding the right mix of actions is not always easy and certainly a matter of personal taste. In general, it can be said that the more "aggressive" your default settings (in the top section of the actions file) are, the more exceptions for "trusted" sites you will have to make later. If, for example, you want to crunch all cookies per default, you'll have to make exceptions from that rule for sites that you regularly use and that require cookies for actually useful puposes, like maybe your bank, favorite shop, or newspaper.
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 things. There just are too many variables, and sites are constantly changing. Sooner or later you will want to change the rules (and read this chapter again :).
The easiest way to edit the actions files is with a browser by using our browser-based editor, which can be reached from http://config.privoxy.org/show-status. The editor allows both fine-grained control over every single feature on a per-URL basis, and easy choosing from wholesale sets of defaults like "Cautious", "Medium" or "Adventuresome". Warning: the "Adventuresome" setting is not only more aggressive, but includes settings that are fun and subversive, and which some may find of dubious merit!
If you prefer plain text editing to GUIs, you can of course also directly edit the the actions files. Look at default.action which is richly commented.
Actions files are divided into sections. There are special sections, like the "alias" sections which will be discussed later. For now let's concentrate on regular sections: They have a heading line (often split up to multiple lines for readability) which consist of a list of actions, separated by whitespace and enclosed in curly braces. Below that, there is a list of URL patterns, each on a separate line.
To determine which actions apply to a request, the URL of the request is compared to all patterns in each action file file. Every time it matches, the list of applicable actions for the URL is incrementally updated, using the heading of the section in which er aspP content and transactions are handled, and on which sites (or even parts thereof). There are three such files included with Privoxy with differing purposes:
default.action - is the primary action file that sets the initial values for all actions. It is intended to provide a base level of functionality for Privoxy's array of features. So it is a set of broad rules that should work reasonably well for users everywhere. This is the file that the developers are keeping updated, and making available to users.
user.action - is intended to be for local site preferences and exceptions. As an example, if your ISP or your bank has specific requirements, and need special handling, this kind of thing should go here. This file will not be upgraded.
standard.action - is used by the web based editor, to set various pre-defined sets of rules for the default actions section in default.action. These have increasing levels of aggressiveness and have no influence on your browsing unless you select them explicitly in the editor. It is not recommend to edit this file.
The default profiles, and their associated actions, as pre-defined in standard.action are:
Table 1. Default Configurations
| Feature | Cautious | Medium | Adventuresome |
|---|---|---|---|
| Ad-blocking by URL | yes | yes | yes |
| Ad-filtering by size | yes | yes | yes |
| GIF de-animation | no | yes | yes |
| Referer forging | no | yes | yes |
| Cookie handling | none | session-only | kill |
| Pop-up killing | unsolicited | unsolicited | all |
| Fast redirects | no | no | yes |
| HTML taming | yes | yes | yes |
| JavaScript taming | yes | yes | yes |
| Web-bug killing | yes | yes | yes |
| Fun text replacements | no | no | yes |
| Image tag reordering | no | no | yes |
| Ad-filtering by link | no | no | yes |
| Demoronizer | no | no | yes |
The list of actions files to be used are defined in the main configuration file, and are processed in the order they are defined (e.g. default.action is typically process before user.action). The content of these can all be viewed and edited from http://config.privoxy.org/show-status.
An actions file typically has multiple sections. If you want to use "aliases" in an actions file, you have to place the (optional) alias section at the top of that file. Then comes the default set of rules which will apply universally to all sites and pages (be very careful with using such a universal set in user.action or any other actions file after default.action, because it will override the result from consulting any previous file). And then below that, exceptions to the defined universal policies. You can regard user.action as an appendix to default.action, with the advantage that is a separate file, which makes preserving your personal settings across Privoxy upgrades easier.
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 or rejected, or accepted only during the current browser session (i.e. not written to disk), content can be modified, JavaScripts tamed, user-tracking fooled, and much more. See below for a complete list of actions.
Note that some actions, like cookie suppression or script disabling, may render some sites unusable that rely on these techniques to work properly. Finding the right mix of actions is not always easy and certainly a matter of personal taste. In general, it can be said that the more "aggressive" your default settings (in the top section of the actions file) are, the more exceptions for "trusted" sites you will have to make later. If, for example, you want to crunch all cookies per default, you'll have to make exceptions from that rule for sites that you regularly use and that require cookies for actually useful puposes, like maybe your bank, favorite shop, or newspaper.
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 things. There just are too many variables, and sites are constantly changing. Sooner or later you will want to change the rules (and read this chapter again :).
The easiest way to edit the actions files is with a browser by using our browser-based editor, which can be reached from http://config.privoxy.org/show-status. The editor allows both fine-grained control over every single feature on a per-URL basis, and easy choosing from wholesale sets of defaults like "Cautious", "Medium" or "Adventuresome". Warning: the "Adventuresome" setting is not only more aggressive, but includes settings that are fun and subversive, and which some may find of dubious merit!
If you prefer plain text editing to GUIs, you can of course also directly edit the the actions files. Look at default.action which is richly commented.
Actions files are divided into sections. There are special sections, like the "alias" sections which will be discussed later. For now let's concentrate on regular sections: They have a heading line (often split up to multiple lines for readability) which consist of a list of actions, separated by whitespace and enclosed in curly braces. Below that, there is a list of URL patterns, each on a separate line.
To determine which actions apply to a request, the URL of the request is compared to all patterns in each action file file. Every time it matches, the list of applicable actions for the URL is incrementally updated, using the heading of the section in which er aspP content and transactions are handled, and on which sites (or even parts thereof). There are three such files included with Privoxy with differing purposes:
default.action - is the primary action file that sets the initial values for all actions. It is intended to provide a base level of functionality for Privoxy's array of features. So it is a set of broad rules that should work reasonably well for users everywhere. This is the file that the developers are keeping updated, and making available to users.
user.action - is intended to be for local site preferences and exceptions. As an example, if your ISP or your bank has specific requirements, and need special handling, this kind of thing should go here. This file will not be upgraded.
standard.action - is used by the web based editor, to set various pre-defined sets of rules for the default actions section in default.action. These have increasing levels of aggressiveness and have no influence on your browsing unless you select them explicitly in the editor. It is not recommend to edit this file.
The default profiles, and their associated actions, as pre-defined in standard.action are:
Table 1. Default Configurations
| Feature | Cautious | Medium | Adventuresome |
|---|---|---|---|
| Ad-blocking by URL | yes | yes | yes |
| Ad-filtering by size | yes | yes | yes |
| GIF de-animation | no | yes | yes |
| Referer forging | no | yes | yes |
| Cookie handling | none | session-only | kill |
| Pop-up killing | unsolicited | unsolicited | all |
| Fast redirects | no | no | yes |
| HTML taming | yes | yes | yes |
| JavaScript taming | yes | yes | yes |
| Web-bug killing | yes | yes | yes |
| Fun text replacements | no | no | yes |
| Image tag reordering | no | no | yes |
| Ad-filtering by link | no | no | yes |
| Demoronizer | no | no | yes |
The list of actions files to be used are defined in the main configuration file, and are processed in the order they are defined (e.g. default.action is typically process before user.action). The content of these can all be viewed and edited from http://config.privoxy.org/show-status.
An actions file typically has multiple sections. If you want to use "aliases" in an actions file, you have to place the (optional) alias section at the top of that file. Then comes the default set of rules which will apply universally to all sites and pages (be very careful with using such a universal set in user.action or any other actions file after default.action, because it will override the result from consulting any previous file). And then below that, exceptions to the defined universal policies. You can regard user.action as an appendix to default.action, with the advantage that is a separate file, which makes preserving your personal settings across Privoxy upgrades easier.
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 or rejected, or accepted only during the current browser session (i.e. not written to disk), content can be modified, JavaScripts tamed, user-tracking fooled, and much more. See below for a complete list of actions.
Note that some actions, like cookie suppression or script disabling, may render some sites unusable that rely on these techniques to work properly. Finding the right mix of actions is not always easy and certainly a matter of personal taste. In general, it can be said that the more "aggressive" your default settings (in the top section of the actions file) are, the more exceptions for "trusted" sites you will have to make later. If, for example, you want to crunch all cookies per default, you'll have to make exceptions from that rule for sites that you regularly use and that require cookies for actually useful puposes, like maybe your bank, favorite shop, or newspaper.
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 things. There just are too many variables, and sites are constantly changing. Sooner or later you will want to change the rules (and read this chapter again :).
The easiest way to edit the actions files is with a browser by using our browser-based editor, which can be reached from http://config.privoxy.org/show-status. The editor allows both fine-grained control over every single feature on a per-URL basis, and easy choosing from wholesale sets of defaults like "Cautious", "Medium" or "Adventuresome". Warning: the "Adventuresome" setting is not only more aggressive, but includes settings that are fun and subversive, and which some may find of dubious merit!
If you prefer plain text editing to GUIs, you can of course also directly edit the the actions files. Look at default.action which is richly commented.
Actions files are divided into sections. There are special sections, like the "alias" sections which will be discussed later. For now let's concentrate on regular sections: They have a heading line (often split up to multiple lines for readability) which consist of a list of actions, separated by whitespace and enclosed in curly braces. Below that, there is a list of URL patterns, each on a separate line.
To determine which actions apply to a request, the URL of the request is compared to all patterns in each action file file. Every time it matches, the list of applicable actions for the URL is incrementally updated, using the heading of the section in which er aspP content and transactions are handled, and on which sites (or even parts thereof). There are three such files included with Privoxy with differing purposes:
default.action - is the primary action file that sets the initial values for all actions. It is intended to provide a base level of functionality for Privoxy's array of features. So it is a set of broad rules that should work reasonably well for users everywhere. This is the file that the developers are keeping updated, and making available to users.
user.action - is intended to be for local site preferences and exceptions. As an example, if your ISP or your bank has specific requirements, and need special handling, this kind of thing should go here. This file will not be upgraded.
standard.action - is used by the web based editor, to set various pre-defined sets of rules for the default actions section in default.action. These have increasing levels of aggressiveness and have no influence on your browsing unless you select them explicitly in the editor. It is not recommend to edit this file.
The default profiles, and their associated actions, as pre-defined in standard.action are:
Table 1. Default Configurations
| Feature | Cautious | Medium | Adventuresome |
|---|---|---|---|
| Ad-blocking by URL | yes | yes | yes |
| Ad-filtering by size | yes | yes | yes |
| GIF de-animation | no | yes | yes |
| Referer forging | no | yes | yes |
| Cookie handling | none | session-only | kill |
| Pop-up killing | unsolicited | unsolicited | all |
| Fast redirects | no | no | yes |
| HTML taming | yes | yes | yes |
| JavaScript taming | yes | yes | yes |
| Web-bug killing | yes | yes | yes |
| Fun text replacements | no | no | yes |
| Image tag reordering | no | no | yes |
| Ad-filtering by link | no | no | yes |
| Demoronizer | no | no | yes |
The list of actions files to be used are defined in the main configuration file, and are processed in the order they are defined (e.g. default.action is typically process before user.action). The content of these can all be viewed and edited from http://config.privoxy.org/show-status.
An actions file typically has multiple sections. If you want to use "aliases" in an actions file, you have to place the (optional) alias section at the top of that file. Then comes the default set of rules which will apply universally to all sites and pages (be very careful with using such a universal set in user.action or any other actions file after default.action, because it will override the result from consulting any previous file). And then below that, exceptions to the defined universal policies. You can regard user.action as an appendix to default.action, with the advantage that is a separate file, which makes preserving your personal settings across Privoxy upgrades easier.
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 or rejected, or accepted only during the current browser session (i.e. not written to disk), content can be modified, JavaScripts tamed, user-tracking fooled, and much more. See below for a complete list of actions.
Note that some actions, like cookie suppression or script disabling, may render some sites unusable that rely on these techniques to work properly. Finding the right mix of actions is not always easy and certainly a matter of personal taste. In general, it can be said that the more "aggressive" your default settings (in the top section of the actions file) are, the more exceptions for "trusted" sites you will have to make later. If, for example, you want to crunch all cookies per default, you'll have to make exceptions from that rule for sites that you regularly use and that require cookies for actually useful puposes, like maybe your bank, favorite shop, or newspaper.
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 things. There just are too many variables, and sites are constantly changing. Sooner or later you will want to change the rules (and read this chapter again :).
The easiest way to edit the actions files is with a browser by using our browser-based editor, which can be reached from http://config.privoxy.org/show-status. The editor allows both fine-grained control over every single feature on a per-URL basis, and easy choosing from wholesale sets of defaults like "Cautious", "Medium" or "Adventuresome". Warning: the "Adventuresome" setting is not only more aggressive, but includes settings that are fun and subversive, and which some may find of dubious merit!
If you prefer plain text editing to GUIs, you can of course also directly edit the the actions files. Look at default.action which is richly commented.
Actions files are divided into sections. There are special sections, like the "alias" sections which will be discussed later. For now let's concentrate on regular sections: They have a heading line (often split up to multiple lines for readability) which consist of a list of actions, separated by whitespace and enclosed in curly braces. Below that, there is a list of URL patterns, each on a separate line.
To determine which actions apply to a request, the URL of the request is compared to all patterns in each action file file. Every time it matches, the list of applicable actions for the URL is incrementally updated, using the heading of the section in which er aspP content and transactions are handled, and on which sites (or even parts thereof). There are three such files included with Privoxy with differing purposes:
default.action - is the primary action file that sets the initial values for all actions. It is intended to provide a base level of functionality for Privoxy's array of features. So it is a set of broad rules that should work reasonably well for users everywhere. This is the file that the developers are keeping updated, and making available to users.
user.action - is intended to be for local site preferences and exceptions. As an example, if your ISP or your bank has specific requirements, and need special handling, this kind of thing should go here. This file will not be upgraded.
standard.action - is used by the web based editor, to set various pre-defined sets of rules for the default actions section in default.action. These have increasing levels of aggressiveness and have no influence on your browsing unless you select them explicitly in the editor. It is not recommend to edit this file.
The default profiles, and their associated actions, as pre-defined in standard.action are:
Table 1. Default Configurations
| Feature | Cautious | Medium | Adventuresome |
|---|---|---|---|
| Ad-blocking by URL | yes | yes | yes |
| Ad-filtering by size | yes | yes | yes |
| GIF de-animation | no | yes | yes |
| Referer forging | no | yes | yes |
| Cookie handling | none | session-only | kill |
| Pop-up killing | unsolicited | unsolicited | all |
| Fast redirects | no | no | yes |
| HTML taming | yes | yes | yes |
| JavaScript taming | yes | yes | yes |
| Web-bug killing | yes | yes | yes |
| Fun text replacements | no | no | yes |
| Image tag reordering | no | no | yes |
| Ad-filtering by link | no | no | yes |
| Demoronizer | no | no | yes |
The list of actions files to be used are defined in the main configuration file, and are processed in the order they are defined (e.g. default.action is typically process before user.action). The content of these can all be viewed and edited from http://config.privoxy.org/show-status.
An actions file typically has multiple sections. If you want to use "aliases" in an actions file, you have to place the (optional) alias section at the top of that file. Then comes the default set of rules which will apply universally to all sites and pages (be very careful with using such a universal set in user.action or any other actions file after default.action, because it will override the result from consulting any previous file). And then below that, exceptions to the defined universal policies. You can regard user.action as an appendix to default.action, with the advantage that is a separate file, which makes preserving your personal settings across Privoxy upgrades easier.
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 or rejected, or accepted only during the current browser session (i.e. not written to disk), content can be modified, JavaScripts tamed, user-tracking fooled, and much more. See below for a complete list of actions.
Note that some actions, like cookie suppression or script disabling, may render some sites unusable that rely on these techniques to work properly. Finding the right mix of actions is not always easy and certainly a matter of personal taste. In general, it can be said that the more "aggressive" your default settings (in the top section of the actions file) are, the more exceptions for "trusted" sites you will have to make later. If, for example, you want to crunch all cookies per default, you'll have to make exceptions from that rule for sites that you regularly use and that require cookies for actually useful puposes, like maybe your bank, favorite shop, or newspaper.
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 things. There just are too many variables, and sites are constantly changing. Sooner or later you will want to change the rules (and read this chapter again :).
The easiest way to edit the actions files is with a browser by using our browser-based editor, which can be reached from http://config.privoxy.org/show-status. The editor allows both fine-grained control over every single feature on a per-URL basis, and easy choosing from wholesale sets of defaults like "Cautious", "Medium" or "Adventuresome". Warning: the "Adventuresome" setting is not only more aggressive, but includes settings that are fun and subversive, and which some may find of dubious merit!
If you prefer plain text editing to GUIs, you can of course also directly edit the the actions files. Look at default.action which is richly commented.
Actions files are divided into sections. There are special sections, like the "alias" sections which will be discussed later. For now let's concentrate on regular sections: They have a heading line (often split up to multiple lines for readability) which consist of a list of actions, separated by whitespace and enclosed in curly braces. Below that, there is a list of URL patterns, each on a separate line.
To determine which actions apply to a request, the URL of the request is compared to all patterns in each action file file. Every time it matches, the list of applicable actions for the URL is incrementally updated, using the heading of the section in which er aspP content and transactions are handled, and on which sites (or even parts thereof). There are three such files included with Privoxy with differing purposes:
default.action - is the primary action file that sets the initial values for all actions. It is intended to provide a base level of functionality for Privoxy's array of features. So it is a set of broad rules that should work reasonably well for users everywhere. This is the file that the developers are keeping updated, and making available to users.
user.action - is intended to be for local site preferences and exceptions. As an example, if your ISP or your bank has specific requirements, and need special handling, this kind of thing should go here. This file will not be upgraded.
standard.action - is used by the web based editor, to set various pre-defined sets of rules for the default actions section in default.action. These have increasing levels of aggressiveness and have no influence on your browsing unless you select them explicitly in the editor. It is not recommend to edit this file.
The default profiles, and their associated actions, as pre-defined in standard.action are:
Table 1. Default Configurations
| Feature | Cautious | Medium | Adventuresome |
|---|---|---|---|
| Ad-blocking by URL | yes | yes | yes |
| Ad-filtering by size | yes | yes | yes |
| GIF de-animation | no | yes | yes |
| Referer forging | no | yes | yes |
| Cookie handling | none | session-only | kill |
| Pop-up killing | unsolicited | unsolicited | all |
| Fast redirects | no | no | yes |
| HTML taming | yes | yes | yes |
| JavaScript taming | yes | yes | yes |
| Web-bug killing | yes | yes | yes |
| Fun text replacements | no | no | yes |
| Image tag reordering | no | no | yes |
| Ad-filtering by link | no | no | yes |
| Demoronizer | no | no | yes |
The list of actions files to be used are defined in the main configuration file, and are processed in the order they are defined (e.g. default.action is typically process before user.action). The content of these can all be viewed and edited from http://config.privoxy.org/show-status.
An actions file typically has multiple sections. If you want to use "aliases" in an actions file, you have to place the (optional) alias section at the top of that file. Then comes the default set of rules which will apply universally to all sites and pages (be very careful with using such a universal set in user.action or any other actions file after default.action, because it will override the result from consulting any previous file). And then below that, exceptions to the defined universal policies. You can regard user.action as an appendix to default.action, with the advantage that is a separate file, which makes preserving your personal settings across Privoxy upgrades easier.
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 or rejected, or accepted only during the current browser session (i.e. not written to disk), content can be modified, JavaScripts tamed, user-tracking fooled, and much more. See below for a complete list of actions.
Note that some actions, like cookie suppression or script disabling, may render some sites unusable that rely on these techniques to work properly. Finding the right mix of actions is not always easy and certainly a matter of personal taste. In general, it can be said that the more "aggressive" your default settings (in the top section of the actions file) are, the more exceptions for "trusted" sites you will have to make later. If, for example, you want to crunch all cookies per default, you'll have to make exceptions from that rule for sites that you regularly use and that require cookies for actually useful puposes, like maybe your bank, favorite shop, or newspaper.
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 things. There just are too many variables, and sites are constantly changing. Sooner or later you will want to change the rules (and read this chapter again :).
The easiest way to edit the actions files is with a browser by using our browser-based editor, which can be reached from http://config.privoxy.org/show-status. The editor allows both fine-grained control over every single feature on a per-URL basis, and easy choosing from wholesale sets of defaults like "Cautious", "Medium" or "Adventuresome". Warning: the "Adventuresome" setting is not only more aggressive, but includes settings that are fun and subversive, and which some may find of dubious merit!
If you prefer plain text editing to GUIs, you can of course also directly edit the the actions files. Look at default.action which is richly commented.
Actions files are divided into sections. There are special sections, like the "alias" sections which will be discussed later. For now let's concentrate on regular sections: They have a heading line (often split up to multiple lines for readability) which consist of a list of actions, separated by whitespace and enclosed in curly braces. Below that, there is a list of URL patterns, each on a separate line.
To determine which actions apply to a request, the URL of the request is compared to all patterns in each action file file. Every time it matches, the list of applicable actions for the URL is incrementally updated, using the heading of the section in which er aspP content and transactions are handled, and on which sites (or even parts thereof). There are three such files included with Privoxy with differing purposes:
default.action - is the primary action file that sets the initial values for all actions. It is intended to provide a base level of functionality for Privoxy's array of features. So it is a set of broad rules that should work reasonably well for users everywhere. This is the file that the developers are keeping updated, and making available to users.
user.action - is intended to be for local site preferences and exceptions. As an example, if your ISP or your bank has specific requirements, and need special handling, this kind of thing should go here. This file will not be upgraded.
standard.action - is used by the web based editor, to set various pre-defined sets of rules for the default actions section in default.action. These have increasing levels of aggressiveness and have no influence on your browsing unless you select them explicitly in the editor. It is not recommend to edit this file.
The default profiles, and their associated actions, as pre-defined in standard.action are:
Table 1. Default Configurations
| Feature | Cautious | Medium | Adventuresome |
|---|---|---|---|
| Ad-blocking by URL | yes | yes | yes |
| Ad-filtering by size | yes | yes | yes |
| GIF de-animation | no | yes | yes |
| Referer forging | no | yes | yes |
| Cookie handling | none | session-only | kill |
| Pop-up killing | unsolicited | unsolicited | all |
| Fast redirects | no | no | yes |
| HTML taming | yes | yes | yes |
| JavaScript taming | yes | yes | yes |
| Web-bug killing | yes | yes | yes |
| Fun text replacements | no | no | yes |
| Image tag reordering | no | no | yes |
| Ad-filtering by link | no | no | yes |
| Demoronizer | no | no | yes |
The list of actions files to be used are defined in the main configuration file, and are processed in the order they are defined (e.g. default.action is typically process before user.action). The content of these can all be viewed and edited from http://config.privoxy.org/show-status.
An actions file typically has multiple sections. If you want to use "aliases" in an actions file, you have to place the (optional) alias section at the top of that file. Then comes the default set of rules which will apply universally to all sites and pages (be very careful with using such a universal set in user.action or any other actions file after default.action, because it will override the result from consulting any previous file). And then below that, exceptions to the defined universal policies. You can regard user.action as an appendix to default.action, with the advantage that is a separate file, which makes preserving your personal settings across Privoxy upgrades easier.
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 or rejected, or accepted only during the current browser session (i.e. not written to disk), content can be modified, JavaScripts tamed, user-tracking fooled, and much more. See below for a complete list of actions.
Note that some actions, like cookie suppression or script disabling, may render some sites unusable that rely on these techniques to work properly. Finding the right mix of actions is not always easy and certainly a matter of personal taste. In general, it can be said that the more "aggressive" your default settings (in the top section of the actions file) are, the more exceptions for "trusted" sites you will have to make later. If, for example, you want to crunch all cookies per default, you'll have to make exceptions from that rule for sites that you regularly use and that require cookies for actually useful puposes, like maybe your bank, favorite shop, or newspaper.
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 things. There just are too many variables, and sites are constantly changing. Sooner or later you will want to change the rules (and read this chapter again :).
The easiest way to edit the actions files is with a browser by using our browser-based editor, which can be reached from http://config.privoxy.org/show-status. The editor allows both fine-grained control over every single feature on a per-URL basis, and easy choosing from wholesale sets of defaults like "Cautious", "Medium" or "Adventuresome". Warning: the "Adventuresome" setting is not only more aggressive, but includes settings that are fun and subversive, and which some may find of dubious merit!
If you prefer plain text editing to GUIs, you can of course also directly edit the the actions files. Look at default.action which is richly commented.
Actions files are divided into sections. There are special sections, like the "alias" sections which will be discussed later. For now let's concentrate on regular sections: They have a heading line (often split up to multiple lines for readability) which consist of a list of actions, separated by whitespace and enclosed in curly braces. Below that, there is a list of URL patterns, each on a separate line.
To determine which actions apply to a request, the URL of the request is compared to all patterns in each action file file. Every time it matches, the list of applicable actions for the URL is incrementally updated, using the heading of the section in which er aspP content and transactions are handled, and on which sites (or even parts thereof). There are three such files included with Privoxy with differing purposes:
default.action - is the primary action file that sets the initial values for all actions. It is intended to provide a base level of functionality for Privoxy's array of features. So it is a set of broad rules that should work reasonably well for users everywhere. This is the file that the developers are keeping updated, and making available to users.
user.action - is intended to be for local site preferences and exceptions. As an example, if your ISP or your bank has specific requirements, and need special handling, this kind of thing should go here. This file will not be upgraded.
standard.action - is used by the web based editor, to set various pre-defined sets of rules for the default actions section in default.action. These have increasing levels of aggressiveness and have no influence on your browsing unless you select them explicitly in the editor. It is not recommend to edit this file.
The default profiles, and their associated actions, as pre-defined in standard.action are:
Table 1. Default Configurations
| Feature | Cautious | Medium | Adventuresome |
|---|---|---|---|
| Ad-blocking by URL | yes | yes | yes |
| Ad-filtering by size | yes | yes | yes |
| GIF de-animation | no | yes | yes |
| Referer forging | no | yes | yes |
| Cookie handling | none | session-only | kill |
| Pop-up killing | unsolicited | unsolicited | all |
| Fast redirects | no | no | yes |
| HTML taming | yes | yes | yes |
| JavaScript taming | yes | yes | yes |
| Web-bug killing | yes | yes | yes |
| Fun text replacements | no | no | yes |
| Image tag reordering | no | no | yes |
| Ad-filtering by link | no | no | yes |
| Demoronizer | no | no | yes |
The list of actions files to be used are defined in the main configuration file, and are processed in the order they are defined (e.g. default.action is typically process before user.action). The content of these can all be viewed and edited from http://config.privoxy.org/show-status.
An actions file typically has multiple sections. If you want to use "aliases" in an actions file, you have to place the (optional) alias section at the top of that file. Then comes the default set of rules which will apply universally to all sites and pages (be very careful with using such a universal set in user.action or any other actions file after default.action, because it will override the result from consulting any previous file). And then below that, exceptions to the defined universal policies. You can regard user.action as an appendix to default.action, with the advantage that is a separate file, which makes preserving your personal settings across Privoxy upgrades easier.
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 or rejected, or accepted only during the current browser session (i.e. not written to disk), content can be modified, JavaScripts tamed, user-tracking fooled, and much more. See below for a complete list of actions.
Note that some actions, like cookie suppression or script disabling, may render some sites unusable that rely on these techniques to work properly. Finding the right mix of actions is not always easy and certainly a matter of personal taste. In general, it can be said that the more "aggressive" your default settings (in the top section of the actions file) are, the more exceptions for "trusted" sites you will have to make later. If, for example, you want to crunch all cookies per default, you'll have to make exceptions from that rule for sites that you regularly use and that require cookies for actually useful puposes, like maybe your bank, favorite shop, or newspaper.
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 things. There just are too many variables, and sites are constantly changing. Sooner or later you will want to change the rules (and read this chapter again :).
The easiest way to edit the actions files is with a browser by using our browser-based editor, which can be reached from http://config.privoxy.org/show-status. The editor allows both fine-grained control over every single feature on a per-URL basis, and easy choosing from wholesale sets of defaults like "Cautious", "Medium" or "Adventuresome". Warning: the "Adventuresome" setting is not only more aggressive, but includes settings that are fun and subversive, and which some may find of dubious merit!
If you prefer plain text editing to GUIs, you can of course also directly edit the the actions files. Look at default.action which is richly commented.
Actions files are divided into sections. There are special sections, like the "alias" sections which will be discussed later. For now let's concentrate on regular sections: They have a heading line (often split up to multiple lines for readability) which consist of a list of actions, separated by whitespace and enclosed in curly braces. Below that, there is a list of URL patterns, each on a separate line.
To determine which actions apply to a request, the URL of the request is compared to all patterns in each action file file. Every time it matches, the list of applicable actions for the URL is incrementally updated, using the heading of the section in which er aspP content and transactions are handled, and on which sites (or even parts thereof). There are three such files included with Privoxy with differing purposes:
default.action - is the primary action file that sets the initial values for all actions. It is intended to provide a base level of functionality for Privoxy's array of features. So it is a set of broad rules that should work reasonably well for users everywhere. This is the file that the developers are keeping updated, and making available to users.
user.action - is intended to be for local site preferences and exceptions. As an example, if your ISP or your bank has specific requirements, and need special handling, this kind of thing should go here. This file will not be upgraded.
standard.action - is used by the web based editor, to set various pre-defined sets of rules for the default actions section in default.action. These have increasing levels of aggressiveness and have no influence on your browsing unless you select them explicitly in the editor. It is not recommend to edit this file.
The default profiles, and their associated actions, as pre-defined in standard.action are:
Table 1. Default Configurations
| Feature | Cautious | Medium | Adventuresome |
|---|---|---|---|
| Ad-blocking by URL | yes | yes | yes |
| Ad-filtering by size | yes | yes | yes |
| GIF de-animation | no | yes | yes |
| Referer forging | no | yes | yes |
| Cookie handling | none | session-only | kill |
| Pop-up killing | unsolicited | unsolicited | all |
| Fast redirects | no | no | yes |
| HTML taming | yes | yes | yes |
| JavaScript taming | yes | yes | yes |
| Web-bug killing | yes | yes | yes |
| Fun text replacements | no | no | yes |
| Image tag reordering | no | no | yes |
| Ad-filtering by link | no | no | yes |
| Demoronizer | no | no | yes |
The list of actions files to be used are defined in the main configuration file, and are processed in the order they are defined (e.g. default.action is typically process before user.action). The content of these can all be viewed and edited from http://config.privoxy.org/show-status.
An actions file typically has multiple sections. If you want to use "aliases" in an actions file, you have to place the (optional) alias section at the top of that file. Then comes the default set of rules which will apply universally to all sites and pages (be very careful with using such a universal set in user.action or any other actions file after default.action, because it will override the result from consulting any previous file). And then below that, exceptions to the defined universal policies. You can regard user.action as an appendix to default.action, with the advantage that is a separate file, which makes preserving your personal settings across Privoxy upgrades easier.
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 or rejected, or accepted only during the current browser session (i.e. not written to disk), content can be modified, JavaScripts tamed, user-tracking fooled, and much more. See below for a complete list of actions.
Note that some actions, like cookie suppression or script disabling, may render some sites unusable that rely on these techniques to work properly. Finding the right mix of actions is not always easy and certainly a matter of personal taste. In general, it can be said that the more "aggressive" your default settings (in the top section of the actions file) are, the more exceptions for "trusted" sites you will have to make later. If, for example, you want to crunch all cookies per default, you'll have to make exceptions from that rule for sites that you regularly use and that require cookies for actually useful puposes, like maybe your bank, favorite shop, or newspaper.
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 things. There just are too many variables, and sites are constantly changing. Sooner or later you will want to change the rules (and read this chapter again :).
The easiest way to edit the actions files is with a browser by using our browser-based editor, which can be reached from http://config.privoxy.org/show-status. The editor allows both fine-grained control over every single feature on a per-URL basis, and easy choosing from wholesale sets of defaults like "Cautious", "Medium" or "Adventuresome". Warning: the "Adventuresome" setting is not only more aggressive, but includes settings that are fun and subversive, and which some may find of dubious merit!
If you prefer plain text editing to GUIs, you can of course also directly edit the the actions files. Look at default.action which is richly commented.
Actions files are divided into sections. There are special sections, like the "alias" sections which will be discussed later. For now let's concentrate on regular sections: They have a heading line (often split up to multiple lines for readability) which consist of a list of actions, separated by whitespace and enclosed in curly braces. Below that, there is a list of URL patterns, each on a separate line.
To determine which actions apply to a request, the URL of the request is compared to all patterns in each action file file. Every time it matches, the list of applicable actions for the URL is incrementally updated, using the heading of the section in which er aspP content and transactions are handled, and on which sites (or even parts thereof). There are three such files included with Privoxy with differing purposes:
default.action - is the primary action file that sets the initial values for all actions. It is intended to provide a base level of functionality for Privoxy's array of features. So it is a set of broad rules that should work reasonably well for users everywhere. This is the file that the developers are keeping updated, and making available to users.
user.action - is intended to be for local site preferences and exceptions. As an example, if your ISP or your bank has specific requirements, and need special handling, this kind of thing should go here. This file will not be upgraded.
standard.action - is used by the web based editor, to set various pre-defined sets of rules for the default actions section in default.action. These have increasing levels of aggressiveness and have no influence on your browsing unless you select them explicitly in the editor. It is not recommend to edit this file.
The default profiles, and their associated actions, as pre-defined in standard.action are:
Table 1. Default Configurations
| Feature | Cautious | Medium | Adventuresome |
|---|---|---|---|
| Ad-blocking by URL | yes | yes | yes |
| Ad-filtering by size | yes | yes | yes |
| GIF de-animation | no | yes | yes |
| Referer forging | no | yes | yes |
| Cookie handling | none | session-only | kill |
| Pop-up killing | unsolicited | unsolicited | all |
| Fast redirects | no | no | yes |
| HTML taming | yes | yes | yes |
| JavaScript taming | yes | yes | yes |
| Web-bug killing | yes | yes | yes |
| Fun text replacements | no | no | yes |
| Image tag reordering | no | no | yes |
| Ad-filtering by link | no | no | yes |
| Demoronizer | no | no | yes |
The list of actions files to be used are defined in the main configuration file, and are processed in the order they are defined (e.g. default.action is typically process before user.action). The content of these can all be viewed and edited from http://config.privoxy.org/show-status.
An actions file typically has multiple sections. If you want to use "aliases" in an actions file, you have to place the (optional) alias section at the top of that file. Then comes the default set of rules which will apply universally to all sites and pages (be very careful with using such a universal set in user.action or any other actions file after default.action, because it will override the result from consulting any previous file). And then below that, exceptions to the defined universal policies. You can regard user.action as an appendix to default.action, with the advantage that is a separate file, which makes preserving your personal settings across Privoxy upgrades easier.
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 or rejected, or accepted only during the current browser session (i.e. not written to disk), content can be modified, JavaScripts tamed, user-tracking fooled, and much more. See below for a complete list of actions.
Note that some actions, like cookie suppression or script disabling, may render some sites unusable that rely on these techniques to work properly. Finding the right mix of actions is not always easy and certainly a matter of personal taste. In general, it can be said that the more "aggressive" your default settings (in the top section of the actions file) are, the more exceptions for "trusted" sites you will have to make later. If, for example, you want to crunch all cookies per default, you'll have to make exceptions from that rule for sites that you regularly use and that require cookies for actually useful puposes, like maybe your bank, favorite shop, or newspaper.
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 things. There just are too many variables, and sites are constantly changing. Sooner or later you will want to change the rules (and read this chapter again :).
The easiest way to edit the actions files is with a browser by using our browser-based editor, which can be reached from http://config.privoxy.org/show-status. The editor allows both fine-grained control over every single feature on a per-URL basis, and easy choosing from wholesale sets of defaults like "Cautious", "Medium" or "Adventuresome". Warning: the "Adventuresome" setting is not only more aggressive, but includes settings that are fun and subversive, and which some may find of dubious merit!
If you prefer plain text editing to GUIs, you can of course also directly edit the the actions files. Look at default.action which is richly commented.
Actions files are divided into sections. There are special sections, like the "alias" sections which will be discussed later. For now let's concentrate on regular sections: They have a heading line (often split up to multiple lines for readability) which consist of a list of actions, separated by whitespace and enclosed in curly braces. Below that, there is a list of URL patterns, each on a separate line.
To determine which actions apply to a request, the URL of the request is compared to all patterns in each action file file. Every time it matches, the list of applicable actions for the URL is incrementally updated, using the heading of the section in which er aspP content and transactions are handled, and on which sites (or even parts thereof). There are three such files included with Privoxy with differing purposes:
default.action - is the primary action file that sets the initial values for all actions. It is intended to provide a base level of functionality for Privoxy's array of features. So it is a set of broad rules that should work reasonably well for users everywhere. This is the file that the developers are keeping updated, and making available to users.
user.action - is intended to be for local site preferences and exceptions. As an example, if your ISP or your bank has specific requirements, and need special handling, this kind of thing should go here. This file will not be upgraded.
standard.action - is used by the web based editor, to set various pre-defined sets of rules for the default actions section in default.action. These have increasing levels of aggressiveness and have no influence on your browsing unless you select them explicitly in the editor. It is not recommend to edit this file.
The default profiles, and their associated actions, as pre-defined in standard.action are: